Skill · Development
Hig components search
Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.
How to use it
- Start your plan and connect your AI once
- Add the skill to your AI, one time only: press Copy skill and paste it into your AI's instructions: a project in ChatGPT, Claude or Grok, a Gem in Gemini, an agent in Microsoft 365 Copilot, or a rule in Cursor. It stays there for every new chat. In Kimi, paste it at the start of a new chat.
- Ask for the task in your own words, or say it directly:
Use the Hig components search skill to help me with this.SKILL.md4 files in this skill
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](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
- 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.