Apple Xcode Workflow
Purpose
Use this skill as the top-level entry point for Apple and Swift work in or around Xcode. The skill guides agent-side tool use, while scripts/run_workflow.py enforces local policy, mutation guards, cooldown behavior, docs routing, and structured fallback planning.
When To Use
- Use this skill for Xcode workspace inspection, read or search, diagnostics, build, test, and run tasks.
- Use this skill for Swift toolchain checks and official Apple CLI fallback.
- Use this skill for Apple and Swift documentation requests that should prefer Dash local sources before official web docs.
- Use this skill when direct filesystem mutation in an Xcode-managed scope may be required.
- Recommend
apple-dash-docsetswhen the user needs Dash docset search, install, or generation work instead of Apple execution work. - Recommend
apple-swift-package-bootstrapwhen the user needs to create a brand new Swift package rather than work inside an existing Xcode or Swift project.
Single-Path Workflow
- Classify the request into one operation type:
- workspace or session inspection
- read, search, or diagnostics
- build, test, or run
- package or toolchain management
- docs lookup
- mutation
- Apply the Apple docs gate before any Apple design, architecture, implementation, or refactor guidance:
- read the relevant Apple documentation first
- use Dash or Xcode-local documentation first, then official Apple documentation if needed
- state the documented API behavior, lifecycle rule, or workflow requirement being relied on before proposing changes
- do not rely on memory as the primary source when Apple docs exist
- if the docs and the current code conflict, stop and report that conflict
- if no relevant Apple docs can be found, say that explicitly before proceeding
- Run
scripts/run_workflow.pyto apply runtime configuration, mutation-guard checks, docs-routing order, advisory cooldown, and CLI fallback planning. - Use the guidance in
references/mcp-tool-matrix.mdfor agent-executed MCP operations. - If MCP fails, use the structured fallback output from
scripts/run_workflow.pytogether withreferences/cli-fallback-matrix.md. - Report which parts were agent-executed, which parts were locally enforced by script, the Apple docs relied on, and any required next step.
Inputs
operation_type: one of the operation types listed above.workspace_path: optional absolute path for the target Xcode or Swift workspace.tab_identifier: optional MCP tab identifier when already known.mcp_failure_reason: optional input when continuing from an earlier MCP failure.docs_query: required whenoperation_typeisdocs.filesystem_fallback_opt_in: optional explicit opt-in when planning direct filesystem fallback in Xcode-managed scope.- Defaults:
- runtime entrypoint: executable
scripts/run_workflow.py - agent-side MCP retries once for transient failures
- advisory cooldown is
21days - docs source order is
dash-mcp,dash-local,official-web - mutation operations require the explicit guard in Xcode-managed scope
- runtime entrypoint: executable
Outputs
statussuccess: the workflow completed on its primary or fallback pathblocked: prerequisites, policy, or mutation safeguards prevented completionhandoff: the workflow is handing off supporting context to another step or skill
path_typeprimary: the guided agent-side MCP path completed successfullyfallback: the official CLI fallback path completed successfully
output- operation type
guard_resultdocs_routefallback_commands- advisory status
- one next step or handoff payload when needed
Guards and Stop Conditions
- Apply the mutation guard from
references/mutation-risk-policy.mdonly when the operation type ismutation. - Do not skip the mutation guard for direct filesystem edits inside Xcode-managed scope.
- Stop with
blockedwhen the required workspace context cannot be resolved and the operation cannot safely continue. - Stop with
blockedwhen allowlist or sandbox rules prevent the official CLI fallback and no safe alternative exists. - Stop with
blockedwhenoperation_type=docsanddocs_queryis missing.
Fallbacks and Handoffs
- Official CLI execution is the only fallback path when the primary agent-side MCP path cannot complete.
- Use
references/mcp-failure-handoff.mdfor the canonical fallback and handoff payload. - Use
references/allowlist-guidance.mdwhen a safe official CLI fallback is blocked by local rules. - Use
references/dash-docs-flow.mdto describe docs lookup as an operation profile under this same execution engine. - Recommend
apple-dash-docsetsdirectly when the task becomes Dash management work. - Recommend
apple-swift-package-bootstrapdirectly when the task becomes new-package scaffolding. scripts/run_workflow.pyplans fallback commands and docs-route changes; MCP execution itself remains agent-side tool usage guided by this skill.
Customization
- Use
references/customization-flow.md. scripts/customization_config.pystores and reports customization state.scripts/run_workflow.pyloads and enforces the runtime-safe knobs documented inreferences/customization-flow.md.- MCP tool execution itself remains agent-side and is not performed by the local runtime entrypoint or by the skill as a direct runtime.
References
Workflow References
references/workflow-policy.mdreferences/mcp-tool-matrix.mdreferences/cli-fallback-matrix.mdreferences/toolchain-management.mdreferences/mutation-risk-policy.mdreferences/mutation-via-mcp.mdreferences/dash-docs-flow.md
Contract References
references/mcp-failure-handoff.mdreferences/customization-flow.md
Support References
- Recommend
references/snippets/apple-swift-core.mdwhen the user needs reusable Apple and Swift baseline policy content in their own repo alongside execution, docs, or mutation workflows. references/allowlist-guidance.mdreferences/skills-installation.mdreferences/mcp-setup-advisory.mdreferences/skills-discovery.mdreferences/snippets/apple-swift-core.md
Script Inventory
scripts/run_workflow.pyscripts/advisory_cooldown.pyscripts/detect_xcode_managed_scope.shscripts/customization_config.py