About ios-hig
ios-hig is a design reference skill for people building iOS apps, based on Apple's Human Interface Guidelines. It directs users to relevant references and highlights interaction, accessibility, visual design, and other common pitfalls.
Key features
- 01Guidance for selecting design references
- 02Touch target and layout considerations
- 03Dynamic Type and VoiceOver accessibility
- 04Contrast and Reduce Motion checks
- 05Advice on haptics and feedback
Use cases
- 01Checking an iOS screen's accessibility
- 02Reviewing interaction and navigation patterns
- 03Planning motion, feedback, and color choices
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ johnrogers/ claude-swift-engineering --skill ios-higAfter installing, type/ios-higin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/accessibility.mdcontent.mdfeedback.mdinteraction.mdperformance-platform.mdprivacy-permissions.mdvisual-design.mdDetails
From the project READMEiOS Human Interface Guidelines
Apple's Human Interface Guidelines define the visual language, interaction patterns, and accessibility standards that make iOS apps feel native and intuitive. The core principle: clarity and consistency through thoughtful design.
Reference Loading Guide
ALWAYS load reference files if there is even a small chance the content may be required. It's better to have the context than to miss a pattern or make a mistake.
| Reference | Load When |
|---|---|
| Interaction | Touch targets, navigation, layout, hierarchy, or gesture patterns |
| Content | Empty states, writing copy, typography, or placeholder text |
| Visual Design | Colors, materials, contrast, dark mode, or SF Symbols |
| Accessibility | VoiceOver, Dynamic Type, Reduce Motion, or accessibility labels |
| Feedback | Animations, haptics, loading states, or error messages |
| Performance | Responsiveness, system components, or app launch |
| Privacy | Permission requests, data handling, or privacy-sensitive APIs |
Common Mistakes
-
Touch targets smaller than 44x44 points — Buttons and interactive elements must be at least 44x44 points (iOS) to accommodate thumbs. Smaller targets cause frustrated users and accessibility failures.
-
Ignoring Dynamic Type constraints — Text with fixed sizes doesn't respect user accessibility settings. Use Dynamic Type sizes, test with Large or Extra Large settings, and avoid hardcoded font sizes.
-
Insufficient color contrast in dark mode — Colors that work in light mode may fail accessibility in dark mode. Test with Reduce Contrast accessibility setting enabled for both modes.
-
Over-animating transitions — Animations that feel smooth at 60fps can trigger motion sickness in users with vestibular issues. Respect Reduce Motion settings and keep animations under 300ms.
-
Missing VoiceOver labels on custom controls — Custom buttons, toggles, or interactive views need
.accessibilityLabel()and.accessibilityHint()or they're completely unusable to screen reader users. -
Haptic overuse — Every action does NOT need haptic feedback. Reserve haptics for confirmations (purchase, critical action) and errors. Excessive haptics are annoying and drain battery.