search-ux

Design search experiences covering query input, results, filtering, and zero-results states.

2.5k|358|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designer-skills --skill search-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-ux
Source: https://github.com/Owl-Listener/designer-skills/tree/main/interaction-design/skills/search-ux
Command: npx skills add https://github.com/Owl-Listener/designer-skills --skill search-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users who search rather than browse often hit friction: vague inputs, poor ranking, dead-end zero-results pages, and missing filters. This Skill gives designers a structured playbook for building search experiences that help users find what they need with minimal effort.

Core Features & Use Cases

  • Search Entry Design: Guidance on placeholder text, input width, autocomplete suggestions, recent searches, and search-as-navigation patterns.
  • Results and Refinement: Layout patterns (list, grid, grouped), result item anatomy, ranking signals, faceted filtering, and visible applied filters.
  • Zero-Results Recovery: Concrete patterns for typo suggestions, related terms, and alternative paths so a failed search never becomes a dead end.
  • Use Case: A designer building search for an e-commerce app uses this Skill to spec the autocomplete behavior, design the zero-results state with category suggestions, and define which search analytics to track after launch.

Quick Start

Ask the AI to design the search experience for your product, covering the input, autocomplete, results layout, filters, and zero-results state.

Frequently Asked Questions about search-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a zero-results search page?

A zero-results page should confirm the searched term, suggest corrections for likely typos, offer related or broader terms, and provide alternatives like browsing categories or contacting support. Never show a blank page, since this state is a key retention moment.

How many autocomplete suggestions should a search input show?

Show 5 to 8 suggestions after the user types 2 to 3 characters. Order them as recent searches first, then trending or popular items, then predicted completions, and highlight the typed portion within each suggestion.

When should search results use a list versus a grid layout?

Use a list for most content types since it supports scanning, and a grid for visual content like products or images where the thumbnail is the primary decision signal. Group results by type when they span heterogeneous content such as files, people, and messages.

What search analytics should I track to improve search UX?

Track top queries to find content gaps, zero-results queries to find what the system cannot serve, refinement rate to measure query reformulation, click position to evaluate ranking quality, and search abandonment to detect relevance problems.

When should I use navigation patterns instead of search design?

Use search design when users retrieve specific items rather than explore structure. For browse-oriented information architecture and menu structure, use a navigation patterns skill instead, though search should still handle navigational queries like settings or profile.