xcode-project-analyzer

1# Xcode Project Analyzer
2 
3Use this skill for project- and target-level build inefficiencies that are unlikely to be solved by source edits alone.
4 
5## Core Rules
6 
7- Recommendation-first by default.
8- Require explicit approval before changing project files, schemes, or build settings.
9- Prefer measured findings tied to timing summaries, build logs, or project configuration evidence.
10- Distinguish debug-only pain from release-only pain.
11 
12## What To Review
13 
14- scheme build order and target dependencies
15- debug vs release build settings against the [build settings best practices](references/build-settings-best-practices.md)
16- run script phases and dependency-analysis settings
17- derived-data churn or obviously invalidating custom steps
18- opportunities for parallelization
19- explicit module dependency settings and module-map readiness
20- "Planning Swift module" time in the Build Timing Summary -- if it dominates incremental builds, suspect unexpected input modification or macro-related invalidation
21- asset catalog compilation time, especially in targets with large or numerous catalogs
22- `ExtractAppIntentsMetadata` time in the Build Timing Summary -- if this phase consumes significant time, record it as `xcode-behavior` (report the cost and impact, but do not suggest a repo-local optimization unless there is explicit Apple guidance)
23…