ios-hig · johnrogers — Claude Code skill for iOS interfaces
ios-hig is a Claude Code skill that applies Apple's iOS interface guidance to accessibility, visual design, and interaction. It supports screen creation and control review.
MIT ★ 233 updated 2026-01-18
/plugin marketplace add johnrogers/claude-swift-engineering
/plugin install swift-engineering@claude-swift-engineeringWhat ios-hig does
ios-hig covers VoiceOver, Dynamic Type, dark appearance, touch area sizing, animation, haptic feedback, and permission prompts. Its guidance is divided by topic, with references for interaction, visual design, accessibility, feedback, performance, and privacy. That gives Claude Code a focused place to consult for a design question.
Interactive controls should have touch areas of at least 44x44 points. Custom controls also need .accessibilityLabel() and .accessibilityHint() so VoiceOver can describe them. Check motion against Reduce Motion settings; animations that ignore this setting can cause problems for users with vestibular conditions. The skill is for Claude Code.
What it helps with
- check iOS controls for adequate touch areas
- adapt screen text to Dynamic Type
- add VoiceOver labels to custom controls
- review transitions against Reduce Motion
- handle permission prompts in an iOS app
Example prompts for the agent
- Review this settings screen for iOS accessibility guidance.
- Show me how to adapt this screen for Dynamic Type and VoiceOver.
- Check these animations and haptics against Reduce Motion guidance.
How to install ios-hig
1Plugin marketplace
/plugin marketplace add johnrogers/claude-swift-engineering/plugin install swift-engineering@claude-swift-engineeringThis installs the whole swift-engineering plugin with all its skills
2Skills CLI (Vercel)
npx skills add johnrogers/claude-swift-engineering --skill ios-hig -a claude-code3Manually: put the files in place
~/.claude/skills/ios-hig/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ios-hig/
1Skills CLI (Vercel)
npx skills add johnrogers/claude-swift-engineering --skill ios-hig -a codex2Manually: put the files in place
.agents/skills/ios-hig/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add johnrogers/claude-swift-engineering --skill ios-hig -a cursor2Manually: put the files in place
.cursor/skills/ios-hig/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install johnrogers/claude-swift-engineering plugins/swift-engineering/skills/ios-hig2Manually: put the files in place
.github/skills/ios-hig/SKILL.md1Skills CLI (Vercel)
npx skills add johnrogers/claude-swift-engineering --skill ios-hig -a gemini-cli2Platform CLI
gemini skills install https://github.com/johnrogers/claude-swift-engineering --path plugins/swift-engineering/skills/ios-higManually: put the files in place
.devin/skills/ios-hig/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ios-hig
How do I install ios-hig in Claude Code?
Run /plugin marketplace add johnrogers/claude-swift-engineering, then run /plugin install swift-engineering@claude-swift-engineering.
What does ios-hig do?
It guides iOS interface work around Apple’s recommendations for accessibility, appearance, and interaction, including VoiceOver, dark mode, and permission prompts.
What touch area size does ios-hig recommend?
Buttons and other interactive elements should have touch areas of at least 44x44 points.
Source text
SKILL.md · MIT
--- name: ios-hig description: Use when designing iOS interfaces, implementing accessibility (VoiceOver, Dynamic Type), handling dark mode, ensuring adequate touch targets, providing animation/haptic feedback, or requesting user permissions. Apple Human Interface Guidelines for iOS compliance. --- # iOS 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](references/interaction.md)** | Touch targets, navigation, layout, hierarchy, or gesture patterns | | **[Content](references/content.md)** | Empty states, writing copy, typography, or placeholder text | | **[Visual Design](references/visual-design.md)** | Colors, materials, contrast, dark mode, or SF Symbols | | **[Accessibility](references/accessibility.md)** | VoiceOver, Dynamic Type, Reduce Motion, or accessibility labels | | **[Feedback](references/feedback.md)** | Animations, haptics, loading states, or error messages | | **[Performance](references/performance-platform.md)** | Responsiveness, system components, or app launch | | **[Privacy](references/privacy-permissions.md)** | Permission requests, data handling, or privacy-sensitive APIs | ## Common Mistakes 1. **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. 2. **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. 3. **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. 4. **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. 5. **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. 6. **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.
© John Rogers (@johnrogers) · MIT · johnrogers/claude-swift-engineering
Similar skills
All skills for Mobile →ios-hig by other authors comes first.