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
Search: discoverable with instant feedback. Place search fields where users expect them (top of list, toolbar/navigation bar). Show results as the user types.
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. Provide scope buttons so users can filter without complex queries.
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 navigation controllers, tab bars, or sidebars for hierarchy.
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.
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.
Source: sickn33/agentic-awesome-skills → skills/hig-components-search/SKILL.md
Also appears in: sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/hig-components-search/SKILL.md, sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/hig-components-search/SKILL.md
1---2name: hig-components-search3description: Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.4---567# Apple HIG: Navigation Components89Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.1011## Key Principles12131. **Search: discoverable with instant feedback.** Place search fields where users expect them (top of list, toolbar/navigation bar). Show results as the user types.14152. **Page controls: position in a flat page sequence.** For discrete, equally weighted pages (onboarding, photo gallery). Show current page and total count.16173. **Path controls: file hierarchy navigation.** macOS path controls display location within a directory structure and allow jumping to any ancestor.18194. **Search scopes narrow large result sets.** Provide scope buttons so users can filter without complex queries.20215. **Clear empty states for search.** Helpful message suggesting corrections or alternatives, not a blank screen.22236. **Page controls are not for hierarchical navigation.** Flat, linear sequences only. Use navigation controllers, tab bars, or sidebars for hierarchy.24257. **Keep path controls concise.** Show meaningful segments only. Users can click any segment to navigate directly.26278. **Support keyboard for search.** Command-F and system search shortcuts should activate search.2829## Reference Index3031| Reference | Topic | Key content |32|---|---|---|33| [search-fields.md](references/search-fields.md) | Search fields | Scopes, tokens, instant results, placement |34| [page-controls.md](references/page-controls.md) | Page controls | Dot indicators, flat page sequences |35| [path-controls.md](references/path-controls.md) | Path controls | Breadcrumbs, ancestor navigation |3637## Output Format38391. **Component recommendation** -- search field, page control, or path control, and why.402. **Behavior specification** -- interaction model (search-as-you-type, swipe for pages, click-to-navigate for paths).413. **Platform differences** across iOS, iPadOS, macOS, visionOS.4243## Questions to Ask44451. What type of content is being searched or navigated?462. Which platforms?473. How large is the dataset?484. Is search the primary interaction?4950## Related Skills5152- **hig-components-menus** -- Toolbars and menu bars hosting search and navigation controls53- **hig-components-controls** -- Text fields, pickers, segmented controls in search interfaces54- **hig-components-dialogs** -- Popovers and sheets for expanded search or filtering55- **hig-patterns** -- Navigation patterns and information architecture56- **hig-foundations** -- Typography and layout for navigation components5758---5960*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*6162## When to Use63This skill is applicable to execute the workflow or actions described in the overview.6465## Limitations66- Use this skill only when the task clearly matches the scope described above.67- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.68- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.6970---7172**Source:** [`sickn33/agentic-awesome-skills`](https://github.com/sickn33/agentic-awesome-skills) → `skills/hig-components-search/SKILL.md`7374**Also appears in:** `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/hig-components-search/SKILL.md`, `sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/hig-components-search/SKILL.md`
thedixitjain