Apple HIG: Navigation Components
Selective Reading Rule
Start with:
references/usage-routing.mdreferences/quality-checklist.md
Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.
Selective Reading Rule
Start with:
references/senior-master-standard.md
Then load only the references, scripts, assets, or examples needed for the user's actual task.
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.
1---2name: hig-components-search3description: ALWAYS use this when the request matches HIG Components Search: Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.4---56# Apple HIG: Navigation Components78## Selective Reading Rule910Start with:1112- `references/usage-routing.md`13- `references/quality-checklist.md`1415Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.1617## Selective Reading Rule1819Start with:2021- `references/senior-master-standard.md`2223Then load only the references, scripts, assets, or examples needed for the user's actual task.242526Check for `.claude/apple-design-context.md` before asking questions. Use existing context and only ask for information not already covered.2728## Key Principles29301. **Search: discoverable with instant feedback.** Place search fields where users expect them (top of list, toolbar/navigation bar). Show results as the user types.31322. **Page controls: position in a flat page sequence.** For discrete, equally weighted pages (onboarding, photo gallery). Show current page and total count.33343. **Path controls: file hierarchy navigation.** macOS path controls display location within a directory structure and allow jumping to any ancestor.35364. **Search scopes narrow large result sets.** Provide scope buttons so users can filter without complex queries.37385. **Clear empty states for search.** Helpful message suggesting corrections or alternatives, not a blank screen.39406. **Page controls are not for hierarchical navigation.** Flat, linear sequences only. Use navigation controllers, tab bars, or sidebars for hierarchy.41427. **Keep path controls concise.** Show meaningful segments only. Users can click any segment to navigate directly.43448. **Support keyboard for search.** Command-F and system search shortcuts should activate search.4546## Reference Index4748| Reference | Topic | Key content |49|---|---|---|50| [search-fields.md](references/search-fields.md) | Search fields | Scopes, tokens, instant results, placement |51| [page-controls.md](references/page-controls.md) | Page controls | Dot indicators, flat page sequences |52| [path-controls.md](references/path-controls.md) | Path controls | Breadcrumbs, ancestor navigation |5354## Output Format55561. **Component recommendation** -- search field, page control, or path control, and why.572. **Behavior specification** -- interaction model (search-as-you-type, swipe for pages, click-to-navigate for paths).583. **Platform differences** across iOS, iPadOS, macOS, visionOS.5960## Questions to Ask61621. What type of content is being searched or navigated?632. Which platforms?643. How large is the dataset?654. Is search the primary interaction?6667## Related Skills6869- **hig-components-menus** -- Toolbars and menu bars hosting search and navigation controls70- **hig-components-controls** -- Text fields, pickers, segmented controls in search interfaces71- **hig-components-dialogs** -- Popovers and sheets for expanded search or filtering72- **hig-patterns** -- Navigation patterns and information architecture73- **hig-foundations** -- Typography and layout for navigation components7475---7677*Built by [Raintree Technology](https://raintree.technology) · [More developer tools](https://raintree.technology)*7879## When to Use80This skill is applicable to execute the workflow or actions described in the overview.8182## Limitations83- Use this skill only when the task clearly matches the scope described above.84- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.85- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
anhvu1107