Agent Skills: Apple iOS HIG Best Practices

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.

UncategorizedID: pproenca/dot-skills/ios-hig

Install this agent skill to your local

pnpm dlx add-skill https://github.com/pproenca/dot-skills/tree/HEAD/skills/.experimental/ios-hig

Skill Files

Browse the full folder contents for ios-hig.

Download Skill

Loading file tree…

skills/.experimental/ios-hig/SKILL.md

Skill Metadata

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.

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)

2. Interaction Design (CRITICAL)

3. Accessibility (CRITICAL)

4. User Feedback (HIGH)

5. UX Patterns (HIGH)

6. Visual Design (HIGH)

How to Use

Read individual reference files for detailed explanations and code examples:

Reference Files

| File | Description | |------|-------------| | references/_sections.md | Category definitions and ordering | | assets/templates/_template.md | Template for new rules |