Skip to content
cccskills
FreePublished on GitHub

ios-hig-design-guide

Create feature-specific iOS design specifications from Apple's Human Interface Guidelines, its official design guidance. Translate relevant rules into screen structure, component behavior, interaction states, accessibility requirements, and localization checks, with source references.

OriginalShow the original 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.

davepoon/buildwithclaude
See how to install

Good for

  • Writing a design specification for an iOS feature
  • Defining component behavior and screen states
  • Checking accessibility and localization requirements
  • Updating specifications against current Apple guidance

Files included (3)

  • SKILL.md2.9 KB
  • references/ios-design-spec-workflow.md3.5 KB
  • scripts/sync_apple_hig_sources.py13.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

activecampaign-automation

FreeSummary

Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.

  • Finding or registering contacts
  • Adding or removing contact tags
  • Subscribing contacts to lists or unsubscribing them
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

ad-angle-research

FreeSummary

Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.

  • Find angles for new ad copy
  • Plan creative tests using competitor ads
  • Choose a landing page message
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

agent-analytics

FreeSummary

Add website or app tracking, then use command-line tools to review traffic, signups, drop-off, and returning users across projects. Run A/B tests, which compare alternative headlines or buttons, and inspect results to guide changes.

  • Adding page-view and key-action tracking
  • Reviewing traffic and referral sources across projects
  • Finding where visitors drop out before signup or purchase
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

agent-memory-discipline

FreeSummary

Establish rules for when an AI agent should recall past context and save lasting decisions, corrections, preferences, and failures. Works with Markdown files or memory services, preserving decision history and surfacing conflicting records.

  • Carry project conventions into the next session
  • Save user corrections and lasting preferences
  • Record failed approaches and their causes
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

agenttrace-session-audit

FreeSummary

Audit local AI coding-agent sessions with agenttrace to identify spending, token use, tool failures, and operational problems. Produce readable or structured reports and define pass-or-fail thresholds for automated continuous integration checks.

  • Investigating session costs and token waste
  • Finding repeated tool failures and retries
  • Exporting session reports as Markdown or JSON
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

agentwhy-session-audit

FreeSummary

Audit saved agent sessions for access to private files and evidence that secret values entered an agent's context. Get findings without displaying secrets, identify keys needing rotation, and inspect Claude Code or Codex sessions in a local report.

  • Check whether an agent accessed .env files
  • Identify keys that may need rotation
  • Audit private-file access by subagents
davepoon/buildwithclaude3.7KUpdated Oct 20, 2026

See all skills by davepoon

Report a problem with this skill