ux-search
Skill21 starsChanged 5 months agoMITView on GitHub
In-app search UX: discoverability, autocomplete, recent searches, filters, sort, no-results states, voice search, and typo tolerance. Use when designing or reviewing a search feature, results page, or any content discovery flow.
In this repository17 other files it gives its agents.
- ux-accessibilitySkill
- ux-ai-automationSkill
- ux-contentSkill
- ux-error-handlingSkill
- ux-formsSkill
- ux-generalSkill
- ux-help-onboardingSkill
- ux-information-architectureSkill
- ux-navigationSkill
- ux-networkSkill
- ux-notificationsSkill
- ux-reviewSkill
- ux-safety-privacySkill
- ux-settingsSkill
- ux-user-accountSkill
- ux-utilitySkill
- ux-visual-designSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Search is often the fastest path to content.
- Distinctive: line 36
Federated search: When the app has multiple content types, group results by type (People, Products, Documents) with clear section headers.
- Distinctive: line 40
Blank state suggestions: When the search bar is empty, show trending or personalized suggestions rather than a blank box.
- Distinctive: line 47
Search scope clarity: If the search applies to a subset of content, say so upfront.
- Distinctive: line 55
When applying this checklist to a screen, flow, or codebase:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Search UX
Search is often the fastest path to content. A poor search experience is one of the most common reasons users churn from content-heavy apps.
Checklist
| Item | Guidance |
| Search discoverability | Search bar is visible on the home screen or one tap away. Never buried in a menu. |
| Recent searches | Last 5 to 10 queries are saved. User can delete individual entries. |
| Search suggestions | Autocomplete appears after 1 to 2 keystrokes. Debounced at ~300ms. |
| Filter and sort | Filter chips appear above results. Active filter count shown in a badge. |
| Empty state message | "No results for X" is paired with a spelling suggestion and related categories. General empty-state standards live in ux-error-handling. |
| Search scope indicator | UI makes it clear what is being searched ("Searching in Orders"). |
| Voice search | Microphone icon in the search bar. Uses platform speech recognition APIs. |
| Typo tolerance | Fuzzy matching handles common spelling mistakes gracefully. |
Patterns
Progressive disclosure: Show the top 3 results inline with a "See all" link rather than sending users to a full results page for every query.
Federated search: When the app has multiple content types, group results by type (People, Products, Documents) with clear section headers. Let users filter to a specific type if needed.
Blank state suggestions: When the search bar is empty, show trending or personalized suggestions rather than a blank box. This reduces the cognitive load of starting a search from scratch.
Zero-result analytics: Track every search that returns no results. These queries are a direct signal of content gaps or labeling mismatches.
Search scope clarity: If the search applies to a subset of content, say so upfront. Users who search in a filtered context and get no results often blame the app, not the active filter.
How to Review
When applying this checklist to a screen, flow, or codebase:
- Go through every checklist item and mark it Pass, Fail, or N/A — never skip items silently.
- Cite specific evidence for each finding: the screen, component, file, or line it applies to.
- Tag each failure with a severity: Blocker (breaks the experience), Major (hurts usability), or Minor (polish).
- End the review with the top 3 recommended fixes, ranked by user impact.
Related Skills
ux-information-architecture— labeling and categorization that make search findableux-error-handling— canonical empty-state standardsux-ai-automation— AI-powered and natural language search
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.