ios-hig
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+DesignSystemonly (neverData, never sibling features) - App target is the convergence point and owns
DependencyContainer, concrete coordinators, and Route Shell wiring Domainstays pure Swift and defines models plus repository,*Coordinating,ErrorRouting, andAppErrorcontractsDataowns 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- Design tab bars for top-level navigationnav-navigation-stack- Use NavigationStack for hierarchical navigationnav-toolbar-placement- Place actions in toolbars using standard placements
2. Interaction Design (CRITICAL)
inter-touch-targets- Maintain 44pt minimum touch targetsinter-gesture-patterns- Use standard gesture patternsinter-haptic-feedback- Add haptic feedback for meaningful eventsinter-keyboard-handling- Handle keyboard appearance gracefullyinter-drag-drop- Support drag and drop for content transferinter-pull-to-refresh- Support pull to refresh for listsinter-swipe-actions- Add swipe actions for contextual operationsinter-list-search- Use searchable for built-in search
3. Accessibility (CRITICAL)
acc-labels- Provide meaningful accessibility labelsacc-dynamic-type- Support Dynamic Type for all textacc-color-contrast- Maintain sufficient color contrastacc-reduce-motion- Respect reduce motion preferenceacc-color-independent- Never rely on color aloneacc-focus-management- Manage focus for assistive technologiesacc-scaled-metric- Use ScaledMetric for adaptive sizingacc-view-that-fits- Use ViewThatFits for adaptive layouts
4. User Feedback (HIGH)
feed-loading-states- Show appropriate loading indicatorsfeed-error-states- Handle errors with clear recovery actionsfeed-notifications- Use notifications judiciouslyfeed-success-confirmation- Confirm successful actions appropriatelyfeed-empty-states- Design helpful empty states
5. UX Patterns (HIGH)
ux-onboarding- Design minimal onboardingux-permissions- Request permissions in contextux-modality- Use modality appropriatelyux-confirmation-dialog- Use confirmation dialogs for destructive actionsux-data-entry- Minimize data entry frictionux-undo- Support undo for destructive actionsux-settings- Organize settings logically
6. Visual Design (HIGH)
vis-dark-mode- Support dark mode with semantic colorsvis-sf-symbols- Use SF Symbols with correct rendering mode and weightvis-layout-margins- Use standard layout margins and safe areas
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions - Category structure and impact levels
- Rule template - Template for adding new rules
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
More from pproenca/dot-skills
zod
Zod schema validation best practices for type safety, parsing, and error handling. This skill should be used when defining z.object schemas, using z.string validations, safeParse, or z.infer. This skill does NOT cover React Hook Form integration patterns (use react-hook-form skill) or OpenAPI client generation (use orval skill).
2.0Kclean-architecture
Clean Architecture principles and best practices from Robert C. Martin's book. This skill should be used when designing software systems, reviewing code structure, or refactoring applications to achieve better separation of concerns. Triggers on tasks involving layers, boundaries, dependency direction, entities, use cases, or system architecture.
1.4Kemilkowal-animations
Emil Kowalski's animation best practices for web interfaces. Use when writing, reviewing, or implementing animations in React, CSS, or Framer Motion. Triggers on tasks involving transitions, easing, gestures, toasts, drawers, or motion.
917vitest
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should be used when writing or debugging Vitest tests. This skill does NOT cover TDD methodology (use test-tdd skill), API mocking with MSW (use test-msw skill), or Jest-specific APIs.
906typescript
This skill should be used when the user asks to "optimize TypeScript performance", "speed up tsc compilation", "configure tsconfig.json", "fix type errors", "improve async patterns", or encounters TS errors (TS2322, TS2339, "is not assignable to"). Also triggers on .ts, .tsx, .d.ts file work involving type definitions, module organization, or memory management. Does NOT cover TypeScript basics, framework-specific patterns, or testing.
820nuqs
nuqs (type-safe URL query state) best practices for Next.js applications. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, or Next.js routing with state.
734