hig-components-search

Implement Apple HIG-compliant navigation components across iOS, iPadOS, macOS, and watchOS.

3|Updated Jan 14, 2014
One-click install
npx skills add https://github.com/prateek/dotfiles --skill hig-components-search-prateek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hig-components-search
Source: https://github.com/prateek/dotfiles/tree/main/.agents/skills/hig-components-search
Command: npx skills add https://github.com/prateek/dotfiles --skill hig-components-search-prateek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides structured guidance for implementing Apple Human Interface Guidelines for navigation components (search fields, page controls, and path controls) to ensure consistent, discoverable UX.

Core Features & Use Cases

  • Guidance on placement, behavior, and platform nuances for search fields, page controls, and path controls across Apple platforms (iOS, iPadOS, macOS, watchOS).
  • Practical patterns and best practices with cross-references to related components (hig-components-menus, hig-components-controls, hig-components-dialogs, hig-patterns).
  • Example: design a list navigation that includes an inline search with scopes, a breadcrumb path, and a bottom page indicator.

Quick Start

Follow Apple HIG recommendations to craft a navigation UI using search fields, path controls, and page controls in your app prototypes.

Frequently Asked Questions about hig-components-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement Apple HIG search fields with correct placement and behavior?

Apple HIG search fields require strategic placement, accessible behavior, and platform-specific nuances across iOS, iPadOS, macOS, and watchOS. This guidance encodes those Human Interface Guidelines into structured metadata and Markdown sections for consistent, discoverable navigation UX.

What is the best way to design page controls for iOS apps following Apple design guidelines?

Page controls following Apple design guidelines should provide clear bottom indicators for flat navigation. This guidance details platform-specific best practices for page controls, ensuring proper accessibility and behavior alignment across Apple platforms.

When do I need scoped search fields in my app's navigation UI?

Scoped search fields are needed when users must filter list navigation results by specific categories. This guidance provides practical patterns for implementing inline search with scopes, ensuring your app prototypes meet Apple HIG recommendations for discoverable UX.

Does this Apple HIG navigation guidance apply to watchOS applications?

Yes, this Apple HIG navigation guidance applies across watchOS, alongside iOS, iPadOS, and macOS. It encodes platform-specific best practices for search fields, page controls, and path controls, ensuring consistent navigation behavior tailored to each platform.