name: apple-platform-project-setup-skill description: Use when bootstrapping or standardizing an Apple platform workspace end to end and you need the full setup flow orchestrated across discovery, interview, workspace selection, capability install, config, artifacts, AGENTS guidance, and verification.
Apple Platform Project Setup
Run the Apple workspace setup flow in strict order.
This is the only plugin skill that should trigger implicitly. The leaf skills are narrow helpers for explicit use or for the orchestrated flow below.
When to Use
Use this skill when:
- starting a new Apple platform repository or local workspace
- standardizing an existing Apple repository without skipping discovery
- choosing or confirming
SPMversusXcode - aligning
.codex/config.toml, MCP, lint, CI, README, andAGENTS.mdin one pass
Do not use this skill for:
- non-Apple projects
- one-off cleanup unrelated to workspace bootstrap or standardization
Shared Source Of Truth
Use these shared assets throughout the flow:
catalog.yamlinventory/skills.yamlinventory/subagents.yamlreferences/source-precedence.mdreferences/capability-discovery.mdreferences/project-interview.mdreferences/codex-config.mdreferences/mcp-setup.mdreferences/github-actions.mdreferences/swiftlint-setup.mdreferences/spm-readme.mdreferences/app-readme.mdreferences/xcodegen-setup.mdreferences/agents-personalization.mdreferences/skill-verification.mdsnippets/
Mandatory Execution Order
- Use
$apple-platform-capability-discoveryto inspect session plugin surfaces, project-local capabilities, configured MCP, and repo state before proposing installs or migrations. - Use
$apple-platform-project-interviewto collect project role, platforms, policies, personalization, scope, config, MCP, and standardization decisions. - Use
$apple-platform-workspace-selectionto choose or confirmSPMversusXcode, thennative xcodeprojversusXcodeGenwhen the workspace isXcode, and to check tool prerequisites. - Use
$apple-platform-capability-installto map project needs to inventory-backed skills and subagents, recommend one best-fit option per gap, and install or copy only the confirmed missing capabilities. - Use
$apple-platform-codex-configto create or align project.codex/config.toml, multi-agent runtime settings, and optional MCP integrations. - Use
$apple-platform-artifact-applicationto apply or refine README, SwiftLint,.gitignore, workflows, XcodeGen specs, and other snippet-backed repo artifacts. - Use
$apple-platform-agents-renderingto generate the final repo-localAGENTS.mdonly after workspace, capability, config, and artifact decisions are settled. - Use
$apple-platform-setup-verificationto validate the final state, run repository checks, and summarize configured versus pending items.
Never skip or reorder these steps.
Cross-Phase Invariants
- discovery is mandatory before any install proposal
- the interview completes before workspace choice and artifact application
- existing structured repos use preserve-first
audit-and-alignbehavior - global installs and user-home changes always require explicit confirmation
AGENTS.mdis generated only after selected skills and subagents are installed or intentionally skipped- verification is last
Leaf Skills
$apple-platform-capability-discovery: early environment and repo-state inspection$apple-platform-project-interview: intent, policy, and personalization collection$apple-platform-workspace-selection: workspace and toolchain decisions$apple-platform-capability-install: inventory-backed skill and subagent selection$apple-platform-codex-config: project config and MCP setup$apple-platform-artifact-application: snippet-backed repo artifacts$apple-platform-agents-rendering: final-stateAGENTS.md$apple-platform-setup-verification: contract checks and final summary
What Not To Do
- Do not install
obra/superpowersas a project-local skill target. - Do not choose
SPMorXcodebefore the interview. - Do not generate
AGENTS.mdbefore final capability choices are installed or intentionally skipped. - Do not replace structured repo files without compare-and-confirm behavior.