hig-components-search
Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.
Best use case
hig-components-search is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.
Teams using hig-components-search should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hig-components-search/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hig-components-search Compares
| Feature / Agent | hig-components-search | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Apple HIG: Navigation Components Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered. ## Key Principles 1. **Search: discoverable with instant feedback.** Place search fields where users expect them (top of list, toolbar/navigation bar). Show results as the user types. 2. **Page controls: position in a flat page sequence.** For discrete, equally weighted pages (onboarding, photo gallery). Show current page and total count. 3. **Path controls: file hierarchy navigation.** macOS path controls display location within a directory structure and allow jumping to any ancestor. 4. **Search scopes narrow large result sets.** Provide scope buttons so users can filter without complex queries. 5. **Clear empty states for search.** Helpful message suggesting corrections or alternatives, not a blank screen. 6. **Page controls are not for hierarchical navigation.** Flat, linear sequences only. Use navigation controllers, tab bars, or sidebars for hierarchy. 7. **Keep path controls concise.** Show meaningful segments only. Users can click any segment to navigate directly. 8. **Support keyboard for search.** Command-F and system search shortcuts should activate search. ## Reference Index | Reference | Topic | Key content | |---|---|---| | [search-fields.md](references/search-fields.md) | Search fields | Scopes, tokens, instant results, placement | | [page-controls.md](references/page-controls.md) | Page controls | Dot indicators, flat page sequences | | [path-controls.md](references/path-controls.md) | Path controls | Breadcrumbs, ancestor navigation | ## Output Format 1. **Component recommendation** -- search field, page control, or path control, and why. 2. **Behavior specification** -- interaction model (search-as-you-type, swipe for pages, click-to-navigate for paths). 3. **Platform differences** across iOS, iPadOS, macOS, visionOS. ## Questions to Ask 1. What type of content is being searched or navigated? 2. Which platforms? 3. How large is the dataset? 4. Is search the primary interaction? ## Related Skills - **hig-components-menus** -- Toolbars and menu bars hosting search and navigation controls - **hig-components-controls** -- Text fields, pickers, segmented controls in search interfaces - **hig-components-dialogs** -- Popovers and sheets for expanded search or filtering - **hig-patterns** -- Navigation patterns and information architecture - **hig-foundations** -- Typography and layout for navigation components --- *Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)* ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
notion-research-documentation
Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.
figma-code-connect-components
Connects Figma design components to code components using Code Connect mapping tools. Use when user says "code connect", "connect this component to code", "map this component", "link component to code", "create code connect mapping", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.
content-research-writer
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
yousearch-automation
Automate Yousearch tasks via Rube MCP (Composio). Always search tools first for current schemas.
google-search-console-automation
Automate Google Search Console tasks via Rube MCP (Composio): search performance, URL inspection, sitemaps, and indexing status. Always search tools first for current schemas.
composio-search-automation
Automate Composio Search tasks via Rube MCP (Composio). Always search tools first for current schemas.
research-lookup
Look up current research information using parallel-cli search (primary, fast web search), the Parallel Chat API (deep research), or Perplexity sonar-pro-search (academic paper searches). Automatically routes queries to the best backend. Use for finding papers, gathering research data, and verifying scientific information.
research-grants
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
perplexity-search
Perform AI-powered web searches with real-time information using Perplexity models via LiteLLM and OpenRouter. This skill should be used when conducting web searches for current information, finding recent scientific literature, getting grounded answers with source citations, or accessing information beyond the model knowledge cutoff. Provides access to multiple Perplexity models including Sonar Pro, Sonar Pro Search (advanced agentic search), and Sonar Reasoning Pro through a single OpenRouter API key.
market-research-reports
Generate comprehensive market research reports (50+ pages) in the style of top consulting firms (McKinsey, BCG, Gartner). Features professional LaTeX formatting, extensive visual generation with scientific-schematics and generate-image, deep integration with research-lookup for data gathering, and multi-framework strategic analysis including Porter Five Forces, PESTLE, SWOT, TAM/SAM/SOM, and BCG Matrix.
bgpt-paper-search
Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server. Returns 25+ fields per paper including methods, results, sample sizes, quality scores, and conclusions. Use for literature reviews, evidence synthesis, and finding experimental details not available in abstracts alone.
xvary-stock-research
Thesis-driven equity analysis from public SEC EDGAR and market data; /analyze, /score, /compare workflows with bundled Python tools (Claude Code, Cursor, Codex).