About hig-components-search
hig-components-search is a skill for applying Apple HIG guidance to search fields, page controls, and path controls. It helps designers and developers choose components and specify behavior across Apple platforms.
Key features
- 01Recommends search, page, or path controls
- 02Guidance on search scopes and live results
- 03Covers empty states and keyboard search
- 04Explains flat versus hierarchical navigation
- 05Specifies platform differences
Use cases
- 01Choosing navigation controls for an Apple app
- 02Designing search-as-you-type behavior
- 03Planning gallery or onboarding page indicators
- 04Designing ancestor navigation for directories
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill hig-components-searchAfter installing, type/hig-components-searchin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/path-controls.mdpage-controls.mdsearch-fields.mdDetails
From the project READMEApple 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
-
Search: discoverable with instant feedback. Choose placement per platform and context, including bottom search/tab affordances on iOS. Show results as the user types when feasible, with debounce/cancellation for remote searches.
-
Page controls: position in a flat page sequence. For discrete, equally weighted pages (onboarding, photo gallery). Show current page and total count.
-
Path controls: file hierarchy navigation. macOS path controls display location within a directory structure and allow jumping to any ancestor.
-
Search scopes narrow large result sets. Consider scope controls when categories are clear; default to a broad scope and avoid unnecessary controls.
-
Clear empty states for search. Helpful message suggesting corrections or alternatives, not a blank screen.
-
Page controls are not for hierarchical navigation. Flat, linear sequences only. Use a navigation stack, sidebar or split view for hierarchy; tab bars also represent peer destinations.
-
Keep path controls concise. Show meaningful segments only. Users can click any segment to navigate directly.
-
Support keyboard for search. Command-F and system search shortcuts should activate search.
Reference Index
| Reference | Topic | Key content |
|---|---|---|
| search-fields.md | Search fields | Scopes, tokens, instant results, placement |
| page-controls.md | Page controls | Dot indicators, flat page sequences |
| path-controls.md | Path controls | Breadcrumbs, ancestor navigation |
Output Format
- Component recommendation -- search field, page control, or path control, and why.
- Behavior specification -- interaction model (search-as-you-type, swipe for pages, click-to-navigate for paths).
- Platform differences across iOS, iPadOS, macOS, visionOS.
Questions to Ask
- What type of content is being searched or navigated?
- Which platforms?
- How large is the dataset?
- 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 · More developer tools
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Example
User request:
Use @hig-components-search for this task: Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.
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.