hig-patterns

name	hig-patterns
version	1.0.0
description	> Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about "onboarding flow", "user onboarding", "app launch", "loading state", "drag and drop", "search pattern", "settings design", "notifications", "modality", "multitasking", "feedback pattern", "haptics", "undo redo", "file management", data entry, sharing, collaboration, full screen, audio, video, haptic feedback, ratings, printing, help, or account management in Apple apps. Also use when the user says "how should onboarding work", "my app takes too long to load", "should I use a modal here", "how do I handle errors", "when should I ask for permissions", "how to show progress", or "what's the right way to confirm a delete". Cross-references: hig-foundations for underlying principles, hig-platforms for platform specifics, hig-components-layout for navigation, hig-components-content for data display.
risk	unknown
source	community

Apple HIG: Interaction Patterns

Check for .claude/apple-design-context.md before asking questions. Use existing context and only ask for information not already covered.

Key Principles

1. Minimize modality. Use modality only when it is critical to get attention, a task must be completed or abandoned, or saving changes is essential. Prefer non-modal alternatives.

2. Provide clear feedback. Every action should produce visible, audible, or haptic response. Activity indicators for indeterminate waits, progress bars for determinate, haptics for physical confirmation.

3. Support undo over confirmation dialogs. Destructive actions should be reversible when possible. Undo is almost always better than "Are you sure?"

4. Launch quickly. Display a launch screen that transitions seamlessly into the first screen. No splash screens with logos. Restore previous state.

5. Defer sign-in. Let users explore before requiring account creation. Support Sign in with Apple and passkeys.

6. Keep onboarding brief. Three screens max. Let users skip. Teach through progressive disclosure and contextual hints.

7. Use progressive disclosure. Show essentials first, let users drill into details. Don't overwhelm with every option on one screen.

8. Respect user attention. Consolidate notifications, minimize interruptions, give users control over alerts. Never use notifications for marketing.

Reference Index

Reference	Topic	Key content
charting-data.md	Charting Data	Data visualization patterns, accessible charts, interactive elements
collaboration-and-sharing.md	Collaboration & Sharing	Share sheets, activity views, collaborative editing, SharePlay
drag-and-drop.md	Drag and Drop	Drag sources, drop targets, spring loading, multi-item drag, visual feedback
entering-data.md	Entering Data	Text fields, pickers, steppers, input validation, keyboard types, autofill
feedback.md	Feedback	Alerts, action sheets, haptic patterns, sound feedback, visual indicators
file-management.md	File Management	Document browser, file providers, iCloud integration, document lifecycle
going-full-screen.md	Going Full Screen	Full-screen transitions, immersive content, exiting full screen
launching.md	Launching	Launch screens, state restoration, cold vs warm launch
live-viewing-apps.md	Live Viewing Apps	Live content display, real-time updates, Live Activities, Dynamic Island
loading.md	Loading	Activity indicators, progress views, skeleton screens, lazy loading, placeholders
managing-accounts.md

Pattern Selection Guide

User Goal	Recommended Pattern	Avoid
First app experience	Brief onboarding (max 3 screens) + progressive disclosure	Long tutorials, mandatory sign-up
Waiting for content	Skeleton screens or progress indicators	Blocking spinners with no context
Confirming destructive action	Undo support	Excessive "Are you sure?" dialogs
Collecting user input	Inline validation, smart defaults, autofill	Modal forms for simple inputs
Requesting permissions	Contextual, just-in-time with explanation	Requesting all permissions at launch
Providing feedback	Haptics + visual indicator	Silent actions with no confirmation
Organizing preferences	In-app settings for frequent items	Burying all settings in system Settings app

Output Format

1. Recommended pattern with rationale, citing the relevant reference file.
2. Step-by-step implementation covering each screen or state.
3. Platform variations for targeted platforms.
4. Common pitfalls that violate HIG for this pattern.

Questions to Ask

1. Where in the app does this pattern appear? What comes before and after?
2. Which platforms?
3. Designing from scratch or improving an existing flow?
4. Does this involve sensitive actions? (Destructive operations, payments, permissions)

Related Skills

• hig-foundations -- Accessibility, color, typography, and privacy principles underlying every pattern
• hig-platforms -- Platform-specific pattern implementations
• hig-components-layout -- Structural components (tab bars, sidebars, split views) for navigation patterns
• hig-components-content -- Content display within patterns (charts, collections, search results)

---

Built by Raintree Technology · More developer tools

When to Use

This skill is applicable to execute the workflow or actions described in the overview.