hig-components-search

Overview of hig-components-search skill

hig-components-search is an Apple HIG skill for designing search fields, page controls, and path controls in navigation-heavy interfaces. Use the hig-components-search skill when you need a practical answer to “how should search work in my app,” “where should pagination controls go,” or “how do I show hierarchy without confusing users.” It is most useful for UI designers, product teams, and agents that need HIG-aligned guidance for search UX, search scopes, search suggestions, and directory-style navigation.

What this skill is best for

This skill is strongest when the task is about component behavior, placement, and user expectation—not visual styling alone. It helps you decide whether to use a search field, page control, or path control, and how each should behave in a real interface.

Why it is worth installing

The main value of hig-components-search install is decision support: it reduces guesswork around when search should update instantly, when scopes are appropriate, and when page or path controls are the wrong fit. That makes it more useful than a generic prompt because it anchors the output to Apple HIG navigation patterns.

When it is a good fit

Choose hig-components-search for UI Design if your input includes search discovery, filtered results, paginated content, breadcrumbs, file hierarchy, or ancestor navigation. It is a good fit for apps with lists, libraries, catalogs, settings, file browsers, or any interface where users need to find or move through structured content.

How to Use hig-components-search skill

Install and load the skill context

Install hig-components-search in your agent environment, then point the model at the skill context before asking for design guidance. A typical hig-components-search usage flow is to invoke the skill with a short product brief, then let it apply the HIG rules to your specific screen or feature.

Give the skill the right input

The skill works best when you describe: the content type, the user goal, the navigation model, and the constraints. For example, instead of “design search,” ask for “a search field for a large document library with live results, optional category filtering, and no advanced query syntax.” That gives the skill enough context to choose between search fields, scopes, tokens, and empty-state behavior.

Read these files first

Start with skills/hig-components-search/SKILL.md, then open references/search-fields.md, references/page-controls.md, and references/path-controls.md. Those three files are the fastest way to understand the actual guidance behind the hig-components-search guide and avoid overextending a search pattern into pagination or hierarchy use cases.

A prompt pattern that works

Use a prompt that names the interface, the content, and the decision you need. Example: “Apply hig-components-search to a macOS file browser. Recommend the search placement, whether to use scopes, and whether a path control should be standard or pop-up.” This is stronger than a vague request because it forces the skill to answer with component-level guidance, not generic UX advice.

hig-components-search skill FAQ

Is hig-components-search only about search fields?

No. The hig-components-search skill also covers page controls and path controls, so it helps when your problem is navigation structure, not just query input. That matters when teams confuse search, pagination, and hierarchy display.

Do I need this if I can write a normal prompt?

If you already know the HIG rules and only need a quick reminder, maybe not. Install hig-components-search when you want more reliable, installable guidance that stays aligned to Apple’s navigation-component conventions and avoids common misuse, like treating page controls as hierarchical navigation.

Is this suitable for beginner designers?

Yes, if the goal is to make a good first decision quickly. The skill is especially helpful for beginners who are unsure when to use search suggestions, scope controls, or path controls, because it gives a concrete framework instead of leaving them to infer the pattern.

When should I not use it?

Do not use hig-components-search for branding, visual decoration, or general layout systems. It is also a poor fit if your product needs highly custom search logic, enterprise filtering taxonomies, or behavior that intentionally departs from Apple HIG patterns.

How to Improve hig-components-search skill

Provide the decision context up front

The strongest results come from inputs that include platform, content density, and whether the user is searching, browsing, or navigating hierarchy. For example: “iPad app, 20,000 items, live search, optional scope buttons, results list updates as the user types.” That is better than “make search better” because it lets the skill choose the right interaction model.

Be explicit about constraints and misfits

If the interface cannot update instantly, if scopes are limited, or if hierarchy depth is shallow, say so. Those constraints change whether hig-components-search should recommend immediate search, tokens, or a simpler pattern. The more you state upfront, the less the output will rely on assumptions.

Iterate from one concrete screen

After the first pass, ask the skill to refine a specific screen rather than the whole product. A good follow-up is: “Revise this for empty states, default scope, and ancestor navigation on macOS.” That narrows the problem and usually improves the practical value of the recommendation.

Watch for common failure modes

The usual mistakes are overusing search scopes, using page controls for non-flat navigation, and under-specifying empty states or result feedback. If the first answer feels generic, re-run hig-components-search with the exact content model, the number of results, and the user’s next likely action.