> 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.
curl "https://skillshub.wtf/pproenca/dot-skills/ios-hig?format=md"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 |
> related_skills --same-repo
> rust-write-tests
Skill for writing expert-level Rust tests. Teaches the "What Could Break?" framework, five transformations from superficial to expert tests, flake hunting protocol, intent-based assertions, naming conventions, and a mandatory self-review checklist. Triggers on writing Rust tests, designing test cases, improving test quality, or reviewing test coverage.
> rust-implement
Write production-grade Rust code using a multi-pass approach. Design types first, then implement, then simplify, then verify with automated lint. Use this skill whenever writing new Rust functions, structs, modules, or features. Triggers on Rust implementation, new Rust code, Rust functions, Rust modules, error handling in Rust, async Rust, or type design in Rust.
> valid-skill
A valid test skill with proper formatting. This skill should pass all validations and serves as a reference for the expected format.
> too-long-skill
This skill has more than 500 lines which should fail validation.