agentsclimarketplace

Hig components search

Skill raintree-technology/hig-doctor/skills/hig-components-search

Apple HIG reference and cross-framework UI audit tooling for agents.

Install
npx -y skills add raintree-technology/hig-doctor --skill hig-components-search

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

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

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. Use this skill when the user says "how should search work in my app," "I need a breadcrumb," "how do I paginate content," or asks about search field, search bar, page control, path control, breadcrumb, navigation component, search UX, search suggestions, search scopes, paginated content navigation, or file path hierarchy display. Cross-references: hig-components-menus, hig-components-controls, hig-components-dialogs, hig-patterns.

SKILL.md

3.2 KB, 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

  1. Search: discoverable with instant feedback. Place search fields where users expect them (top of list, toolbar/navigation bar). Show results as the user types.

  2. Page controls: position in a flat page sequence. For discrete, equally weighted pages (onboarding, photo gallery). Show current page and total count.

  3. Path controls: file hierarchy navigation. macOS path controls display location within a directory structure and allow jumping to any ancestor.

  4. Search scopes narrow large result sets. Provide scope buttons so users can filter without complex queries.

  5. Clear empty states for search. Helpful message suggesting corrections or alternatives, not a blank screen.

  6. Page controls are not for hierarchical navigation. Flat, linear sequences only. Use navigation controllers, tab bars, or sidebars for hierarchy.

  7. Keep path controls concise. Show meaningful segments only. Users can click any segment to navigate directly.

  8. Support keyboard for search. Command-F and system search shortcuts should activate search.

Reference Index

ReferenceTopicKey content
search-fields.mdSearch fieldsScopes, tokens, instant results, placement
page-controls.mdPage controlsDot indicators, flat page sequences
path-controls.mdPath controlsBreadcrumbs, ancestor navigation

Output Format

  1. Component recommendation -- search field, page control, or path control, and why.
  2. Behavior specification -- interaction model (search-as-you-type, swipe for pages, click-to-navigate for paths).
  3. Platform differences across iOS, iPadOS, macOS, visionOS.

Questions to Ask

  1. What type of content is being searched or navigated?
  2. Which platforms?
  3. How large is the dataset?
  4. 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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.