Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Apple Human Interface Guidelines for Agents
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/justinwetch-higagentskills)MCP servers that connect the AI to services for the same work
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
Same kind of work, ordered like the Skills list
| This one HIGAgentSkills | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Maker | justinwetch | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 836 | 111,852 | 67,796 | 32,458 | 29,958 |
| Last code change | Oct 18, 2026 | Nov 17, 2026 | Nov 13, 2026 | Jun 24, 2026 | Oct 30, 2026 |
| License | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (instruction sets) by justinwetch that an AI reads and follows · not an MCP server
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Not stated by the maker · SKILL.md skills work in apps that support Agent Skills, such as Claude Code, Codex and Cursor
GitHub account justinwetch (person), 4 years old
★ 836 stars · code last changed Oct 18, 2026
22 scripts that can run on a computer: scripts/assess_native_hig_capture.py, scripts/capture_hig_agent_evidence.py, scripts/capture_native_hig.py, scripts/check_hig_candidate.py and 18 more
Scripts that go online: scripts/capture_native_hig.py
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 2206ff9 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Uploading to claude.ai would fail: the description is over 200 characters (762). Use "Let the AI install it" instead
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /HIGAgentSkills or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/justinwetch/higagentskills.git /tmp/popnx-skill-justinwetch-higagentskills-2206ff9 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-justinwetch-higagentskills-2206ff9/.' ~/.claude/skills/higagentskillsThe ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Put the apple-hig folder at ~/.agents/skills/apple-hig
~ is your home folder ($HOME)
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/justinwetch/higagentskills.git /tmp/popnx-skill-justinwetch-higagentskills-2206ff9 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-justinwetch-higagentskills-2206ff9/.' ~/.agents/skills/higagentskillsChecked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/justinwetch/higagentskills.git /tmp/popnx-skill-justinwetch-higagentskills-2206ff9 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-justinwetch-higagentskills-2206ff9/.' ~/.agents/skills/higagentskillsCopy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick HIGAgentSkills
Checked against official docs Nov 12, 2026 · Source: cursor.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/justinwetch/higagentskills.git /tmp/popnx-skill-justinwetch-higagentskills-2206ff9 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-justinwetch-higagentskills-2206ff9/.' ~/.cursor/skills/higagentskillsFor other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 18, 2026
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: apple-hig
description: >
Apple Human Interface Guidelines reference, updated for iPhone Duo and
OS 27. Provides authoritative platform-specific design rules, component
specifications, exact measurements, and interaction patterns for iOS,
iPadOS, macOS, tvOS, visionOS, and watchOS. Use when designing, reviewing,
auditing, or fixing any Apple platform UI, or when asked about specific HIG
components, sizing, system behaviors, frameworks (HealthKit, SiriKit, ARKit,
etc.), or platform conventions. Also use when the user is designing any
digital interface and could benefit from established design principles, even
without an explicit Apple platform context. Includes a guided /duo workflow
that adapts an existing iOS app to iPhone Duo, plus opt-in enforce mode with
independent review.
---
# Apple HIG Skill
Use the distilled HIG references in `references/hig/` through `routing-index.md`. The source snapshot and verified release measurements are in README.md.
## Loading Protocol
Release **2026-09-27**; Apple source snapshot **2026-09-12**.
For help, installation, version or capability questions, read only this entry
point and the relevant README section. Do not load the HIG corpus for setup help.
Installing or upgrading this skill includes its `/duo` slash command. After the
skill folder is in place, check whether the host already offers `/duo`. If it
does not, copy `commands/duo.md` into the host's custom slash-command or custom
prompt directory (user-level unless the user asks for one project), confirm
`/duo` is available, and tell the user if a restart is needed.
Work directly in the conversation and the user's project; do not create a browser
intake form, onboarding site, dashboard, or browser setup step.
Ordinary guidance is the default. Only an explicit request to apply enforce mode
activates its procedure. Read `references/enforce.md` first in that case and check
reviewer, Python and observation capabilities before loading the design guidance.
A leading `/duo`, `Use apple-hig in Duo mode`, or an explicit request to adapt
an existing app for iPhone Duo starts Duo mode: read `references/duo.md` and
follow its stages. Questions about the command and ordinary Duo design questions
stay ordinary guidance. Duo mode works only in the app's native code; it never
produces HTML, SVG, or web mockups.
Use the available Python 3.10+ interpreter (`python3` or `python`); do not assume
the executable name. Ordinary guidance also works without Python.
When Python is available, use the standard-library routing helper to resolve
steps 2–6: save only the exact user request to a UTF-8 text file in a temporary
directory outside the user's project, then run `<python> "<skill-root>/scripts/hig_route.py" --request-file "<request.txt>"`.
Read every file in its `files` list in bounded sections, completing any truncated
read before continuing. Do not concatenate the entire set into one tool output;
the helper output is metadata, not the guidance itself. Do not add
your own instructions to the request text or promote inferred topics to
initial matches. If the user explicitly excludes a platform/device/topic, pass
the excluded topic IDs with `--exclude-topic` (repeat for each topic, including
platform aliases matched inside an excluded phrase); record the user's reason.
Keep a platform that is also positively requested elsewhere. Do not exclude
topics merely to reduce context. Exclusions apply
to direct and related selections, never to the 16 foundations. Without Python,
apply the same steps and explicit exclusions manually.
### Step 1 — Parse Task Context
From the user's request, identify:
- **Platform(s):** ios / ipados / macos / tvos / visionos / watchos
- **Device/form factor:** iPhone Duo when named or matched by its tier-2 triggers
- **Components or patterns** mentioned (buttons, tab bars, sheets, etc.)
- **Frameworks or SDKs** referenced (HealthKit, SiriKit, ARKit, etc.)
- **Task type:** design / review / spec / audit / guidance
- **Mode:** ordinary guidance by default. Activate enforce mode only when the user explicitly asks to apply it; mentioning the mode or asking what it means does not activate it. Duo mode starts only as described above.
### Step 2 — Load Tier 1 (every design or review task)
Read all 16 files listed in `routing-index.md` under `## tier-1`:
`accessibility`, `branding`, `color`, `dark-mode`, `design-principles`,
`icons`, `images`, `inclusion`, `layout`, `materials`, `motion`,
`privacy`, `right-to-left`, `sf-symbols`, `typography`, `writing`
These apply universally. Load them before answering.
### Step 3 — Load Platform File (Tier 2)
Read `routing-index.md` → `## tier-2 platform-map`.
For each detected platform, load its `designing-for-[platform]` file.
Also match the tier-2 map's device/form-factor and API triggers using
standalone word/phrase/API-symbol matching. A Duo match loads both
`designing-for-iphone-duo` and `designing-for-ios`; Duo is an iOS form factor.
If "game" or "gaming" is mentioned, also load `designing-for-games`.
### Step 4 — Keyword Scan (Tier 3)
Read `routing-index.md` → `## tier-3 trigger-map`.
Normalize the user request to lowercase. Match trigger strings as
standalone words, phrases, or API symbols; plural, hyphenated and bare-symbol
forms count (`tab bars`, `full-screen`, `keyboardType`). Never match a trigger
merely because it appears inside an unrelated word. For example, `AR` doesn't
match "tab bar," and `AI` doesn't match "explain." Load every matching
file. Load each file at most once.
### Step 5 — Related Expansion
Freeze the initial selection set as the tier-2 and tier-3 files selected in steps 3–4. Read only that set's `related:` frontmatter.
Load the listed files once. Do not expand related lists from those newly added files.
Bind each initial topic to the exact platform/device/trigger text matched in
the user's request. An inferred
component concept is not a literal trigger match.
A topic reached through `related:` stays related even when it is useful;
never promote it to initial and expand it again. If semantic relevance calls
for an additional reference, load that specific file without related expansion.
### Step 6 — Tier 4 On-Demand
Read `routing-index.md` → `## tier-4 trigger-map (on-demand)`.
Use the same standalone word/phrase/API-symbol matching rule. Load a
tier-4 file only on direct keyword match, or if named in the initial selection
set's `related:` list. Never expand from foundations, newly related files, or
directly matched tier-4 files. These are niche — avoid loading broadly.
### Step 7 — Answer or enforce
For explicitly requested enforcement, carry out `references/enforce.md` using
the loaded source guidance. Ordinary guidance never starts that procedure.
For an ordinary guidance answer, quote the short operative source clause verbatim
with all qualifiers intact, then give only the needed application. A compact
table works for multiple states. Keep the rule and application distinct;
do not paraphrase the quotation into a stronger, broader, or narrower rule.
Before sending, delete sentences that do not answer a requested part.
Check the actor, starting state, action and resulting state; do not substitute
a similar neighboring scenario. Mention an API as the implementation of a
rule only when the loaded source supports that relationship.
Do not add unrequested adjacent rules or measurements merely because they are
loaded. Preserve the source's full scope: do not invent narrower device/state
limits when applying a rule, and include every requested state it covers.
Apply the guidance for the named platform, device, orientation, and state.
An explicit scoped exception takes precedence over a broader rule within that scope;
apply that exception only to its stated platform, device and state.
Do not invent a reconciliation for unresolved source conflicts; identify the conflict.
Apply all other compatible loaded content. If a topic isn't covered by loaded fAsk, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.