Ios Hig Design Guide logo

Ios Hig Design Guide

CommunityPopular
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.

Overview

Publisherdavepoon
Repositorybuildwithclaude
Skill nameios-hig-design-guide
Stars
3.6K
Forks
586
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by davepoon on GitHub. Read the source before you install it.

Installation

Install the Ios Hig Design Guide AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/ios-hig-design-guide
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/davepoon/buildwithclaude.git /tmp/buildwithclaude
mkdir -p .claude/skills
cp -r /tmp/buildwithclaude/plugins/all-skills/skills/ios-hig-design-guide .claude/skills/ios-hig-design-guide
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ios Hig Design Guide in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ios Hig Design Guide on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ios Hig Design Guide is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ios Hig Design Guide AI skill do?

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.

Why use Ios Hig Design Guide on TypingMind?

Because you install it once and use it with any model. Ios Hig Design Guide is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ios Hig Design Guide in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/davepoon/buildwithclaude/tree/main/plugins/all-skills/skills/ios-hig-design-guide. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ios Hig Design Guide?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ios Hig Design Guide?

As many as you like. As long as a model supports skills, you can use Ios Hig Design Guide with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ios Hig Design Guide AI skill free?

Yes. It is published on GitHub by davepoon under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇