designing-search-discovery

Design and audit documentation search systems with federated search and CMD+K patterns.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/musher-dev/bundles --skill designing-search-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: designing-search-discovery
Source: https://github.com/musher-dev/bundles/tree/main/developer-docs-authoring/skills/designing-search-discovery
Command: npx skills add https://github.com/musher-dev/bundles --skill designing-search-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need to design and audit effective search and discovery systems for developer documentation, ensuring users can find information quickly and efficiently.

Core Features & Use Cases

  • Search UX Design: Implements modern patterns like CMD+K for intuitive search.
  • Relevance Tuning: Optimizes result ranking based on various factors.
  • Synonym Management: Ensures users find content regardless of their vocabulary.
  • Zero-Result Recovery: Provides helpful fallbacks when searches yield no results.
  • Analytics Integration: Uses metrics to continuously improve search performance.
  • Use Case: When building a new developer portal, use this Skill to define the search experience, ensuring developers can easily locate API references, guides, and tutorials.

Quick Start

Use the designing-search-discovery skill to audit the current search UX and identify areas for improvement.

Frequently Asked Questions about designing-search-discovery

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

FAQPage Schema
How do I design a search experience for developer documentation?

Design documentation search by implementing modern UX patterns like CMD+K, tuning relevance ranking, and mapping synonyms. This ensures developers find API references and guides efficiently.

What is the best way to handle zero-result searches in docs?

Handle zero-result searches by implementing zero-result recovery fallbacks. Provide helpful suggestions and synonym mapping to guide users to relevant content when initial queries yield no results.

How do I improve search relevance for a developer portal?

Improve search relevance by optimizing result ranking based on user behavior analytics and data-driven insights. Adjust synonym mapping to ensure content findability regardless of user vocabulary.

Can I use CMD+K patterns for scoped search in documentation?

Yes, you can implement CMD+K patterns for scoped search and federated search in documentation. This provides an intuitive search experience for navigating complex developer portals.

Why do I need search analytics feedback loops for my docs?

Search analytics feedback loops are needed to continuously improve search performance and content findability. They use metrics and user behavior analysis to identify and address relevance challenges.

When should I implement federated search for documentation?

Implement federated search when your developer documentation spans multiple sources or scopes. It allows users to query across disparate content repositories simultaneously for better discovery.