Xcode App Project Workflow

Purpose

Use this skill as a compatibility surface for older references to xcode-app-project-workflow while the repo transitions to narrower Xcode execution skills. The real long-term owners are xcode-build-run-workflow for build, run, diagnostics, toolchain, and guarded mutation work and xcode-testing-workflow for Swift Testing, XCTest, XCUITest, and .xctestplan work. scripts/run_workflow.py is intentionally routing-only now: it infers enough workspace context to choose the real owner and preserves the direct .pbxproj warning boundary so older flows continue to work during the migration window.

When To Use

• Use this skill when older docs, prompts, or install surfaces still name xcode-app-project-workflow.
• Use this skill when the request is broad and the first job is deciding between the narrower Xcode build/run and testing skills.
• Use this skill after Apple or Swift docs have already been gathered through explore-apple-swift-docs and the work has shifted into Xcode-aware execution or implementation.
• Do not use this skill as the default path for ordinary Xcode build/run work or ordinary Xcode testing work now that narrower skills exist.
• Do not use this skill as the default path for ordinary Swift package development when Package.swift is the source of truth and Xcode-managed behavior is not the main concern.
• Recommend xcode-build-run-workflow when the task is primarily about workspace inspection, diagnostics, build, run, previews, toolchain work, file membership, Metal-toolchain-aware execution, or guarded mutation.
• Recommend xcode-testing-workflow when the task is primarily about Swift Testing, XCTest, XCUITest, .xctestplan, test filtering, retries, or test diagnosis.
• Recommend explore-apple-swift-docs when the user needs Apple or Swift documentation lookup, source selection, Dash compatibility, or docs install follow-up rather than execution work.
• Recommend format-swift-sources when the user needs to integrate or maintain SwiftLint or SwiftFormat across CLI, Xcode, SwiftPM, Git hooks, GitHub Actions, or SwiftFormat config export rather than active Xcode execution work.
• Recommend structure-swift-sources when the user needs file splitting, source-tree cleanup, DocC coverage, or TODO/FIXME ledger normalization rather than active Xcode execution work.
• Recommend bootstrap-swift-package when the user needs to create a brand new Swift package rather than work inside an existing Xcode or Swift project.