Index of every page on this site: llms.txt
All skills
raintree-technology avatar

/hig-components-search

@a0f1e4e
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/raintree-technology/hig-doctor/hig-components-search

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈142 tokens for metadata: the name and description. ≈670 when used: this file. ≈1.7k more on demand in 3 files.

Description uses 7.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈570 characters, or 7.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

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

  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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is safe and consists entirely of markdown documentation references regarding the Apple Human Interface Guidelines (HIG) for navigation components. No active code, scripts, or network interactions are present.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    4 files scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at a0f1e4e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 9 months ago
version
1.0.0

README badge

README badge for raintree-technology/hig-doctor/hig-components-search