Skill routing
How to shortlist foundation skills with apple-development-foundation and master-skill.json.
Default entry: $apple-development-foundation
Use the master skill when:
- A new chat needs a curated shortlist for an Apple-platform task
- The user asks for a foundation audit or inventory comparison
Do not treat it as proof of automatic activation, a replacement for child skill instructions, or an implied repository scan.
Procedure
- Read
.agents/skills/apple-development-foundation/master-skill.json(machine-readable catalog). - Shortlist only children relevant to the request (IDs, roles, purposes in the JSON).
- Read only those children’s
SKILL.mdfiles and follow their workflows. - For a new consumer project, use
$codex-bootstrapafter routing. - Run foundation verification commands from the JSON only for an explicit audit of this repository or its installer.
Direct invocation
When the task already matches a skill, invoke it by name:
$codex-bootstrap
$swiftui-tab-navigation
$swiftui-component-author
$maestro-apple-app-testing
…
Full table: Skills inventory.
Catalog ownership
| Artifact | Role |
|---|---|
.agents/skills/manifest.json |
Canonical inventory, router metadata, and audit definitions |
.agents/skills/apple-development-foundation/master-skill.json |
Generated router projection |
.agents/skills/README.md |
Generated human-readable use / do-not-use table |
Each skill’s SKILL.md |
Executable instructions |
When catalog metadata changes, update the manifest and run ./Scripts/generate-skill-catalog.py. Keep executable instructions hand-written in each SKILL.md.
External skills
Some workflows stay outside this repo (for example App Store marketing screenshots via $app-store-screenshots). See External skills.