Use when ANY iOS build fails, test crashes, Xcode misbehaves, or environment issue occurs before debugging code. Covers build failures, compilation errors, dependency conflicts, simulator problems, environment-first diagnostics.
This skill inherits all available tools. When active, it can use any tool Claude has access to.
You MUST use this skill for ANY build, environment, or Xcode-related issue before debugging application code.
Use this router when you encounter:
BUILD FAILED, compilation errors, linker errors)This router invokes specialized skills based on the specific issue:
Triggers:
BUILD FAILED without obvious code causexcodebuild processesWhy xcode-debugging first: 90% of mysterious issues are environment, not code. Check this BEFORE debugging code.
Invoke: /skill xcode-debugging
Triggers:
Invoke: /skill build-performance
Triggers:
Invoke: /skill build-troubleshooting
User reports build/environment issue
├─ Is it mysterious/intermittent/clean build fails?
│ └─ YES → xcode-debugging (environment-first)
│
├─ Is it dependency conflict?
│ └─ YES → build-troubleshooting
│
└─ Is it slow build time?
└─ YES → build-performance
Do NOT skip this router for:
Environment issues are the #1 time sink in iOS development. Check environment before debugging code.
User: "My build failed with a linker error"
→ Invoke: /skill xcode-debugging (environment-first diagnostic)
User: "Builds are taking 10 minutes"
→ Invoke: /skill build-performance
User: "SPM won't resolve dependencies"
→ Invoke: /skill build-troubleshooting