メニュー
Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.
AI-powered presentation generation via the 2slides API — create slides from text, match a reference image style, summarize documents into decks, add AI voice narration, and export pages/audio. Use for any "make slides", "create a deck", or "slides from this document" request.
Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violations introduced, violations fixed, and pre-existing count. Use `scan` for a full audit with no diffing.
Use the Hugging Face Hub CLI (`hf`) to download, upload, and manage models, datasets, and Spaces.
Plan, orchestrate, and adversarially verify parallel AI coding agents with a dynamic multi-agent workflow engine.
Manage opencode permissions: review always-allow lists, suggest safe read-only commands, configure permission patterns
Generate AI images, videos, and music/audio from agents using the RunAPI CLI.
| name | hig-components-search |
| description | Apple HIG guidance for navigation-related components including search fields, page controls, and path controls. |
| risk | safe |
| source | community |
| date_added | 2026-02-27 |
Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.
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 | 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 |
Built by Raintree Technology · More developer tools
This skill is applicable to execute the workflow or actions described in the overview.
