Consumer workspace

Skills target the app the user is building — not this repository’s archived package.

The rule

Skills in Apple Development Foundation apply to the active workspace: the iOS/macOS app or Swift package the user is building. They do not land code in this reference repository’s archive/Sources/ unless the user explicitly asks for that.

Location	Agent should…
User’s app / package (consumer)	Implement features, components, tests, modules
Consumer root `AGENTS.md`	Own project-local operating rules; preserve existing content and change only with authorization
This repo `.agents/skills/`	Maintain skills only when asked (`$codex-skill-maintainer`)
This repo `archive/`	Leave the preserved package, apps, examples, and old website alone unless explicitly requested
This repo `docs/`	Update agent playbook when documenting the workflow

Archive boundary

The Swift package, examples, apps, and old website are archived exploratory work. See repo ARCHIVE.md.

Do not:

Add modules with ./archive/Scripts/create-module.sh for “product” work
Rebuild DesignSystem / FileKit / ComponentKit here as live libraries
Treat package verification (cd archive && ./Scripts/verify.sh) as the default gate for skill work

Do:

Create shared modules inside the consumer repo when extraction is needed ($swift-package-module-author, $reusable-code-extractor)
Use this foundation repo as skills + MCP/commands reference

New project bootstrap

When the user wants a new app:

Confirm an explicit consumer path, platforms, navigation shape, and design-system constraints.
Inspect existing consumer AGENTS.md files and preserve them.
With authorization, preview or create a missing root contract from the codex-bootstrap/assets/consumer-AGENTS.md.template skill asset using ./Scripts/init-consumer-guidance.sh --target <consumer> --dry-run, or copy from AGENTS.md template.
Invoke $apple-development-foundation so it routes to $codex-bootstrap against the consumer path (use $codex-bootstrap directly only when already selected).
Chain sibling skills as needed (tabs, design system, components, reviews).
Verify with XcodeBuildMCP in that consumer project.

The initializer requires --target, refuses the foundation repository and any existing AGENTS.md, and never modifies global Codex configuration. Existing instructions require a reviewed, explicitly authorized manual merge. When creating or merging the consumer contract, set the Apple verification policy knobs (XcodeBuildMCP CLI fallback and raw Xcode tooling: default require-approval) so agents do not invent fallback permission.

Details: Bootstrap · AGENTS.md template.

Skill maintenance (this repo only)

When the user is editing foundation skills themselves:

Use $codex-skill-maintainer.
Follow docs/skills/skill-authoring-guide.mdx.
Update canonical manifest.json metadata and run ./Scripts/generate-skill-catalog.py when adding or recataloging skills.
Run ./Scripts/verify-skills.sh and, if installer behavior changes, ./Scripts/test-install-skills.sh.