ios-hig
Apple Human Interface Guidelines for iOS 26 / Swift 6.2 clinic-architecture apps. Covers navigation, interaction design, accessibility, feedback states, UX patterns, and visual design for SwiftUI implementations that follow App-target coordinators/route shells and Domain/Data boundaries. Use when designing or reviewing HIG-compliant experiences in the clinic modular MVVM-C stack.
Works with
--- name: ios-hig description: Apple Human Interface Guidelines for iOS 26 / Swift 6.2 clinic-architecture apps. Covers navigation, interaction design, accessibility, feedback states, UX patterns, and visual design for SwiftUI implementations that follow App-target coordinators/route shells and Domain/Data boundaries. Use when designing or reviewing HIG-compliant experiences in the clinic modular MVVM-C stack. license: MIT --- # Apple iOS HIG Best Practices Comprehensive guide for Apple Human Interface Guidelines compliance in iOS apps built with SwiftUI. Contains 34 rules across 6 categories covering navigation, interaction design, accessibility, user feedback, UX patterns, and visual design. ## Clinic Architecture Contract (iOS 26 / Swift 6.2) All guidance in this skill assumes the clinic modular MVVM-C architecture: - Feature modules import `Domain` + `DesignSystem` only (never `Data`, never sibling features) - App target is the convergence point and owns `DependencyContainer`, concrete coordinators, and Route Shell wiring - `Domain` stays pure Swift and defines models plus repository, `*Coordinating`, `ErrorRouting`, and `AppError` contracts - `Data` owns SwiftData/network/sync/retry/background I/O and implements Domain protocols - Read/write flow defaults to stale-while-revalidate reads and optimistic queued writes - ViewModels call repository protocols directly (no default use-case/interactor layer) ## When to Apply Reference these guidelines when: - Building navigation hierarchies with tab bars, NavigationStack, or split views - Designing touch interactions, gestures, and haptic feedback - Ensuring accessibility with VoiceOver, Dynamic Type, and color contrast - Implementing loading states, error handling, and empty states - Building onboarding flows, permission requests, and confirmation dialogs - Supporting dark mode, SF Symbols, and standard layout margins - Reviewing apps for HIG compliance ## Rule Categories by Priority | Priority | Category | Impact | Prefix | |----------|----------|--------|--------| | 1 | Navigation | CRITICAL | `nav-` | | 2 | Interaction Design | CRITICAL | `inter-` | | 3 | Accessibility | CRITICAL | `acc-` | | 4 | User Feedback | HIGH | `feed-` | | 5 | UX Patterns | HIGH | `ux-` | | 6 | Visual Design | HIGH | `vis-` | ## Quick Reference ### 1. Navigation (CRITICAL) - [`nav-tab-bar`](references/nav-tab-bar.md) - Design tab bars for top-level navigation - [`nav-navigation-stack`](references/nav-navigation-stack.md) - Use NavigationStack for hierarchical navigation - [`nav-toolbar-placement`](references/nav-toolbar-placement.md) - Place actions in toolbars using standard placements ### 2. Interaction Design (CRITICAL) - [`inter-touch-targets`](references/inter-touch-targets.md) - Maintain 44pt minimum touch targets - [`inter-gesture-patterns`](references/inter-gesture-patterns.md) - Use standard gesture patterns - [`inter-haptic-feedback`](references/inter-haptic-feedback.md) - Add haptic feedback for meaningful events - [`inter-keyboard-handling`](references/inter-keyboard-handling.md) - Handle keyboard appearance gracefully - [`inter-drag-drop`](references/inter-drag-drop.md) - Support drag and drop for content transfer - [`inter-pull-to-refresh`](references/inter-pull-to-refresh.md) - Support pull to refresh for lists - [`inter-swipe-actions`](references/inter-swipe-actions.md) - Add swipe actions for contextual operations - [`inter-list-search`](references/inter-list-search.md) - Use searchable for built-in search ### 3. Accessibility (CRITICAL) - [`acc-labels`](references/acc-labels.md) - Provide meaningful accessibility labels - [`acc-dynamic-type`](references/acc-dynamic-type.md) - Support Dynamic Type for all text - [`acc-color-contrast`](references/acc-color-contrast.md) - Maintain sufficient color contrast - [`acc-reduce-motion`](references/acc-reduce-motion.md) - Respect reduce motion preference - [`acc-color-independent`](references/acc-color-independent.md) - Never rely on color alone - [`acc-focus-management`](references/acc-focus-management.md) - Manage focus for assistive technologies - [`acc-scaled-metric`](references/acc-scaled-metric.md) - Use ScaledMetric for adaptive sizing - [`acc-view-that-fits`](references/acc-view-that-fits.md) - Use ViewThatFits for adaptive layouts ### 4. User Feedback (HIGH) - [`feed-loading-states`](references/feed-loading-states.md) - Show appropriate loading indicators - [`feed-error-states`](references/feed-error-states.md) - Handle errors with clear recovery actions - [`feed-notifications`](references/feed-notifications.md) - Use notifications judiciously - [`feed-success-confirmation`](references/feed-success-confirmation.md) - Confirm successful actions appropriately - [`feed-empty-states`](references/feed-empty-states.md) - Design helpful empty states ### 5. UX Patterns (HIGH) - [`ux-onboarding`](references/ux-onboarding.md) - Design minimal onboarding - [`ux-permissions`](references/ux-permissions.md) - Request permissions in context - [`ux-modality`](references/ux-modality.md) - Use modality appropriately - [`ux-confirmation-dialog`](references/ux-confirmation-dialog.md) - Use confirmation dialogs for destructive actions - [`ux-data-entry`](references/ux-data-entry.md) - Minimize data entry friction - [`ux-undo`](references/ux-undo.md) - Support undo for destructive actions - [`ux-settings`](references/ux-settings.md) - Organize settings logically ### 6. Visual Design (HIGH) - [`vis-dark-mode`](references/vis-dark-mode.md) - Support dark mode with semantic colors - [`vis-sf-symbols`](references/vis-sf-symbols.md) - Use SF Symbols with correct rendering mode and weight - [`vis-layout-margins`](references/vis-layout-margins.md) - Use standard layout margins and safe areas ## How to Use Read individual reference files for detailed explanations and code examples: - [Section definitions](references/_sections.md) - Category structure and impact levels - [Rule template](assets/templates/_template.md) - Template for adding new rules ## Reference Files | File | Description | |------|-------------| | [references/_sections.md](references/_sections.md) | Category definitions and ordering | | [assets/templates/_template.md](assets/templates/_template.md) | Template for new rules |
More Accessibility skills
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
ui-ux-pro-max
nextlevelbuilder/ui-ux-pro-max-skill
UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.
