* chore: upgrade maintenance scripts to robust PyYAML parsing - Replaces fragile regex frontmatter parsing with PyYAML/yaml library - Ensures multi-line descriptions and complex characters are handled safely - Normalizes quoting and field ordering across all maintenance scripts - Updates validator to strictly enforce description quality * fix: restore and refine truncated skill descriptions - Recovered 223+ truncated descriptions from git history (6.5.0 regression) - Refined long descriptions into concise, complete sentences (<200 chars) - Added missing descriptions for brainstorming and orchestration skills - Manually fixed imagen skill description - Resolved dangling links in competitor-alternatives skill * chore: sync generated registry files and document fixes - Regenerated skills index with normalized forward-slash paths - Updated README and CATALOG to reflect restored descriptions - Documented restoration and script improvements in CHANGELOG.md * fix: restore missing skill and align metadata for full 955 count - Renamed SKILL.MD to SKILL.md in andruia-skill-smith to ensure indexing - Fixed risk level and missing section in andruia-skill-smith - Synchronized all registry files for final 955 skill count * chore(scripts): add cross-platform runners and hermetic test orchestration * fix(scripts): harden utf-8 output and clone target writeability * fix(skills): add missing date metadata for strict validation * chore(index): sync generated metadata dates * fix(catalog): normalize skill paths to prevent CI drift * chore: sync generated registry files * fix: enforce LF line endings for generated registry files
2.9 KiB
name, description, risk, source, date_added
| name | description | risk | source | date_added |
|---|---|---|---|---|
| hig-components-search | Apple HIG guidance for navigation-related components including search fields, page controls, and path controls. | unknown | community | 2026-02-27 |
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.