Hig components search

Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/hig-components-search

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 1,987+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

Install

npx -y skills add sickn33/agentic-awesome-skills --skill hig-components-search

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Apple HIG guidance for navigation-related components including search fields, page controls, and path controls.

SKILL.md

3.2 KB, 648 tokens by cl100k_base, as published. Nobody here has run it

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.