name: apple-platform-capability-discovery description: Use when you need to inspect the current Codex plugin surface, project-local skills, subagents, MCP configuration, and repository state before proposing Apple workspace setup changes.
Apple Platform Capability Discovery
Run this step before the project interview and before proposing any install.
When to Use
Use this skill when:
- starting Apple workspace setup from an unknown environment
- auditing an existing Apple repository before standardization
- checking whether plugin-provided capabilities already cover the need
- determining whether the repo is
greenfieldorexisting_structured_repo
Discovery Checklist
Inspect:
- plugin-provided skills already available in the active Codex session
- project-local skills under
.codex/skills/ - project-local subagents under
.codex/agents/ - configured MCP servers in
.codex/config.toml, when present
Record:
discovered_pluginsdiscovered_project_local_skillsdiscovered_project_local_subagentsdiscovered_mcp_servers
Treat plugins discovered here as session-level capability surfaces, not project-local artifacts.
Repository State Detection
Inspect the target repository before asking for setup choices.
Classify:
greenfieldexisting_structured_repo
Use structural signals such as:
Package.swift*.xcodeproj*.xcworkspaceproject.yml.gitignore.swiftlint.yml.gitlint.github/workflows/.codex/config.tomlAGENTS.md
If the repo is already structured, switch the overall run to preserve-first audit-and-align behavior.
Apple Plugin Surface Rules
- Treat
Build iOS Apps,Build macOS Apps, andExpoas preferred plugin capability surfaces when they are already available in the active session. - Treat Superpowers as a Codex plugin capability surface.
- Do not install, clone, or mirror
obra/superpowersas a project-local skill target.
For Expo iOS loops:
- prefer
expo start - for simulator launch, prefer
expo start --iosor a matching CodexRun iOSaction - do not default to
expo run:ios, prebuild, oreas buildjust to get a simulator loop
Guardrails
- Do not propose new skills, subagents, or MCP until the current capability surface is known.
- Do not confuse plugin-provided skills with project-local installed skills.
- Do not skip repo-state detection after environment discovery.