How do I install the IOS Hig Design Guide skill?

Run npx skillmds@latest add gabrielmoreira/ios-hig-design-guide in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is IOS Hig Design Guide safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with IOS Hig Design Guide?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is IOS Hig Design Guide free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published IOS Hig Design Guide?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

IOS Hig Design Guide by gabrielmoreira

Name: IOS Hig Design Guide
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

IOS Hig Design Guide

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.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

iOS HIG Design Guide

Use this skill to produce iOS design recommendations that stay close to official Apple guidance.

Quick start

Sync official sources.
Read only relevant sections.
Produce a feature-specific spec (not a generic style dump).

Run:

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:

Feature goal and user scenario
Information architecture and screen inventory
Interaction and state model
Component specification
Accessibility and localization checklist
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.

---name: ios-hig-design-guidedescription: 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.

Frequently asked questions