ios-hig-design-guide — Claude Code skill: what it does, how to install
ios-hig-design-guide is a Claude Code skill that turns Apple Human Interface Guidelines into specs for iOS features. It activates for questions about UI rules, accessibility, components, or interaction patterns.
MIT 133 installs ★ 3,785 updated 2026-10-25
npx skills add davepoon/buildwithclaude --skill ios-hig-design-guide -a claude-codeWhat ios-hig-design-guide does
The skill selects relevant Apple Human Interface Guidelines and turns them into decisions for a specific iOS feature. Its spec can cover user scenarios, screen structure, interaction states, accessibility, and localization. Major rules are linked to their source pages.
To answer questions about current or latest guidance, refresh the source files with python3 scripts/sync_apple_hig_sources.py --skill-dir .. The sync script needs Python 3. Reference files include a curated HIG text for routine work and a full page dump; generated files are not meant for manual edits.
What it helps with
- write a design spec for an iOS feature
- define screen and component states
- account for accessibility and localization
- ground UI decisions in Apple guidance
Example prompts for the agent
- Draft an iOS feature spec using Apple’s interface guidance.
- List the interaction states and accessibility requirements for this screen.
- Refresh the HIG sources and define design rules for the sign-in form.
How to install ios-hig-design-guide
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill ios-hig-design-guide -a claude-code2Manually: put the files in place
~/.claude/skills/ios-hig-design-guide/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ios-hig-design-guide/
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill ios-hig-design-guide -a codex2Manually: put the files in place
.agents/skills/ios-hig-design-guide/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill ios-hig-design-guide -a cursor2Manually: put the files in place
.cursor/skills/ios-hig-design-guide/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davepoon/buildwithclaude plugins/all-skills/skills/ios-hig-design-guide2Manually: put the files in place
.github/skills/ios-hig-design-guide/SKILL.md1Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill ios-hig-design-guide -a gemini-cli2Platform CLI
gemini skills install https://github.com/davepoon/buildwithclaude --path plugins/all-skills/skills/ios-hig-design-guideManually: put the files in place
.devin/skills/ios-hig-design-guide/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add davepoon/buildwithclaude --skill ios-hig-design-guide -a opencodeClaude.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-design-guide
How do I install ios-hig-design-guide in Claude Code?
Run npx skills add davepoon/buildwithclaude --skill ios-hig-design-guide -a claude-code. The skill file is installed at ~/.claude/skills/ios-hig-design-guide/SKILL.md.
What does ios-hig-design-guide do?
It turns relevant Apple Human Interface Guidelines into a feature-level iOS spec, covering screens, interactions, component states, accessibility, and localization.
What does ios-hig-design-guide need to refresh its sources?
The sync script requires Python 3. Run python3 scripts/sync_apple_hig_sources.py --skill-dir . before asking about current or latest guidance.
Source text
SKILL.md · MIT
--- name: ios-hig-design-guide category: design description: Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data. Use when a task asks for iOS UI/UX rules, Apple design standards, component behavior, accessibility constraints, interaction patterns, or feature-level design-spec writing grounded in official HIG pages. --- # iOS HIG Design Guide Use this skill to produce iOS design recommendations that stay close to official Apple guidance. ## Quick start 1. Sync official sources. 2. Read only relevant sections. 3. Produce a feature-specific spec (not a generic style dump). Run: ```bash python3 scripts/sync_apple_hig_sources.py --skill-dir . ``` ## Source of truth - Full raw index with links and abstracts: `references/apple-hig-ios-raw.md` - Consolidated text dump of all downloaded pages: `references/apple-hig-ios-fulltext.md` - Curated text dump for iOS spec writing: `references/apple-hig-ios-curated.md` - Workflow for selecting relevant HIG pages: `references/ios-design-spec-workflow.md` - Per-page JSON sources: `references/raw/pages/design/human-interface-guidelines/*.json` - Crawl metadata and fetch status: `references/raw/catalog.json` ## Workflow ### 1) Sync and verify - Run sync script before answering "latest" or "current" requests. - Confirm `download_error` is 0 in `references/raw/catalog.json`. - If errors exist, report failed paths and continue with successfully downloaded pages. ### 2) Narrow scope - Start from `/design/human-interface-guidelines/designing-for-ios`. - Add only sections directly related to the requested feature. - Prioritize foundational constraints (accessibility, layout, typography, color, writing, privacy). - Prefer `references/apple-hig-ios-curated.md` for day-to-day use; use full dump only when needed. ### 3) Extract constraints For each selected page, pull concrete rules into implementable statements: - When to use component/pattern - Required states (loading, empty, error, destructive confirmation) - Accessibility behavior (labels, hints, touch target, dynamic type) - Localization/layout behavior (RTL, truncation, multiline) - Platform-specific caveats (iOS-only vs cross-platform) ### 4) Produce deliverable Default output structure: 1. Feature goal and user scenario 2. Information architecture and screen inventory 3. Interaction and state model 4. Component specification 5. Accessibility and localization checklist 6. Open questions and tradeoffs ## Output style rules - Cite source page paths for each major rule. - Translate HIG guidance into actionable product decisions. - Avoid copying large raw passages. - Mark inferred recommendations explicitly as inference. ## Maintenance - Re-run sync script whenever Apple updates HIG content. - Keep generated raw files in `references/`; do not hand-edit generated outputs. - Update this SKILL.md only for workflow or quality improvements.
© davepoon · MIT · davepoon/buildwithclaude