Skills hig-components-search
πŸ“¦

hig-components-search

Content revision r2 Safe βš™οΈ External commands🌐 Network access

Design Apple Navigation Components with HIG Guidance

Choosing the wrong navigation control creates confusing search and browsing experiences. This skill applies Apple HIG guidance to search fields, page controls, and path controls.

Supports: Claude Codex Code(CC)
πŸ“Š 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "hig-components-search" from https://skillstore.io/skills/sickn33-hig-components-search.md and its manifest at https://skillstore.io/api/skills/sickn33-hig-components-search/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "hig-components-search". Choose navigation for a five-screen iPhone onboarding flow.

Expected outcome:

Use a centered page control near the bottom. Keep the sequence flat, show five indicators, and support direct page movement through swiping.

Using "hig-components-search". Design search for a large macOS document library.

Expected outcome:

  • Place the search field at the trailing side of the toolbar.
  • Start with a broad scope, then offer scopes or tokens for document attributes.
  • Show relevant results quickly and keep clearing behavior consistent.

Using "hig-components-search". Show the selected folder hierarchy in a Mac application.

Expected outcome:

Use a standard path control in the window body. Display meaningful ancestors and let people select a segment to navigate.

Security Audit

Safe
v5 β€’ 7/23/2026 Open versioned report

All ten static findings are false positives caused by ordinary design prose, Markdown formatting, or attribution links. No command execution, system reconnaissance, unauthorized network behavior, prompt injection, or malicious intent was found.

4
Files scanned
423
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

βš™οΈ External commands (1)
🌐 Network access (1)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History β†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-hig-components-search/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-hig-components-search/security.svg)](https://skillstore.io/skills/sickn33-hig-components-search?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-hig-components-search?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-hig-components-search/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-hig-components-search.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA Β· BibTeX Β· CFF)

APA citation

sickn33. (2026). hig-components-search security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-hig-components-search/audits/5

BibTeX citation

@techreport{sickn33-sickn33-hig-components-search-2026, author = {sickn33}, title = {hig-components-search security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-hig-components-search/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "hig-components-search security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-hig-components-search/audits/5" identifiers: - type: other value: "skillstore:sickn33-hig-components-search:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
45
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Plan Mobile Search

Choose search placement, focus behavior, scopes, and suggestions for an iOS or iPadOS content experience.

Review Paginated Onboarding

Check whether page controls fit a flat onboarding sequence and define indicator behavior.

Design File Navigation

Select a standard or pop-up path control for a macOS file workflow.

Try These Prompts

Choose a Component
Recommend a search field, page control, or path control for [workflow] on [platform]. Explain why it fits.
Specify Search Behavior
Design search for [content type] on [platform]. Cover placement, focus, suggestions, scopes, results, empty states, and clearing behavior.
Review Page Controls
Review this [page sequence] for Apple HIG alignment. Assess page count, indicator design, placement, tapping, scrubbing, animation, and platform constraints.
Create a Cross-Platform Specification
Create a navigation component specification for [product]. Compare iOS, iPadOS, macOS, tvOS, visionOS, and watchOS where relevant. Identify unsupported controls and alternatives.

Best Practices

  • Provide the target platform, content type, dataset size, and importance of search.
  • Describe whether navigation is flat, hierarchical, or focused on discovery.
  • Validate recommendations against current Apple documentation and real device behavior.

Avoid

  • Do not use page controls for hierarchical or nonsequential navigation.
  • Do not request implementation code when only a design recommendation is needed.
  • Do not apply macOS path-control guidance to unsupported Apple platforms.

Frequently Asked Questions

Which components does this skill cover?
It covers search fields, page controls, and macOS path controls.
Can it recommend search placement?
Yes. It compares tab bar, toolbar, inline, sidebar, and platform-specific placements.
Does it generate SwiftUI or UIKit code?
No. It produces component recommendations and behavior specifications, not implementation code.
Can I use page controls on macOS?
The included Apple guidance states that page controls are not supported in macOS.
When should I use a path control?
Use one in a macOS window body to show and navigate a selected file or folder hierarchy.
Does it replace accessibility testing?
No. Validate the proposed interface with accessibility checks, target devices, and product-specific testing.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

7 downloads Β· 118 views

File structure

πŸ“ references/

πŸ“„ page-controls.md

πŸ“„ path-controls.md

πŸ“„ search-fields.md

πŸ“„ SKILL.md