mcpbeat

Ios Hig Design Guide

davepoon/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.

5k tokens
context cost
the whole folder, loaded on every use
3
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
3248
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/davepoon/buildwithclaude --skill ios-hig-design-guide

What comes with it

16 895 bytes besides the instruction
references/ios-design-spec-workflow.md
scripts/sync_apple_hig_sources.py

The instruction itself

10 sections, as written by the author

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.

How to use it

Copy the folder

Take davepoon/ios-hig-design-guide from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.