Skip to content
cccskills
FreePublished on GitHub

search-ux

Design a search experience covering query input, suggestions, result layouts, filters, and helpful responses when nothing matches. It also identifies search metrics that reveal missing content, weak rankings, and places where users struggle to find information.

OriginalShow the original description

Design search — query input, zero results, refinement, and result presentation. Use when users retrieve rather than browse. For browse structure, use `navigation-patterns`.

Run score Not tested

See how to install

Good for

  • Designing search for a product catalog
  • Improving searches that return no results
  • Organizing filters and result layouts
  • Choosing metrics to evaluate search

Files included (1)

  • SKILL.md4.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Search UX

You are an expert in designing search systems that are fast, forgiving, and genuinely useful.

What You Do

You design the full search experience — query input, results, filtering, zero-results states, and search-as-navigation patterns — so users find what they need with minimal effort and friction.

Search Entry

The Search Input

  • Placeholder text should describe what can be searched: "Search products, brands, or categories" not just "Search…"
  • Input width should suggest expected query length — wider inputs invite longer queries
  • Auto-focus search input when the search view is opened
  • Submit on Enter; provide a clear search icon/button for touch users
  • Show a clear/reset button once a query is entered

Autocomplete and Suggestions

  • Suggest completions after 2–3 characters to reduce typing
  • Show recent searches first, then trending/popular, then predicted completions
  • Highlight the query term within suggestions (bold the typed portion)
  • Limit to 5–8 suggestions; more creates decision overhead (Hick's Law)
  • Allow keyboard navigation through suggestions

Search-as-Navigation

Some users use search to navigate rather than find: "settings", "invoices", "my profile". Design for this:

  • Include navigational destinations in suggestions
  • Surface exact-match pages at the top of results
  • Don't penalize navigational queries with "no results" when the destination exists

Results

Results Layout

  • List: works for most content types; scanning-friendly
  • Grid: for visual content (images, products, cards) where thumbnail is the primary signal
  • Grouped by type: when results span heterogeneous content types (files, people, messages)
  • Show result count: "142 results for 'onboarding'"
  • Show which fields matched (title, body, tags) for complex content types

Result Items

Each result should show:

  • Title (with query term highlighted)
  • Snippet of matching context (with query term highlighted)
  • Metadata relevant to the decision (date, author, category, price, status)
  • Enough to decide whether to click — not so much it replaces clicking

Ranking and Relevance

  • Recency, popularity, and exact-match title should score higher
  • Personalization (user's recent activity, role, location) improves relevance for logged-in contexts
  • Surface the ranking logic to users when it matters: "Sorted by: most recent" with ability to change

Filtering and Refinement

  • Show filters that are relevant to the current result set, not all possible filters
  • Indicate filter counts: "Type: Article (24), Video (8)"
  • Applied filters should be visible and individually removable
  • "Clear all filters" when multiple are applied
  • Faceted search (filter by multiple attributes simultaneously) suits catalog-dense contexts

Zero-Results State

The most critical and most often neglected state:

  • Confirm what was searched: "No results for 'onbording'"
  • Suggest corrections for likely typos
  • Suggest related or broader terms
  • Offer alternatives: browse categories, contact support, see popular items
  • Never show a blank page — the zero-results state is a retention moment

Search Analytics

  • Top queries: what are users searching for? Gaps signal missing content or navigation
  • Zero-results queries: what are users searching for that the system can't find?
  • Refinement rate: how often do users modify their query or apply filters?
  • Click position: which result position is clicked most? Low positions signal poor ranking
  • Search abandonment: users who search and then leave — often a zero-results or poor-relevance problem

Best Practices

  • Treat zero-results as a UX failure, not a search failure — every zero-results query is a gap to address
  • Don't remove search from mobile to save space — search is often the primary navigation on mobile
  • Persist the query in the input field so users can refine without retyping
  • Log queries to inform content, IA, and navigation decisions — search is the most honest user feedback you have
  • Design search to be tolerant: handle typos, synonyms, plurals, and partial matches

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a-b-test-design

FreeSummary

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

affinity-diagram

FreeSummary

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill