Help us improve
Share bugs, ideas, or general feedback.
From xcode-build-skills
Analyzes Swift and mixed-language Xcode compile hotspots from build timings and diagnostics, recommends prioritized source optimizations. For slow builds, type-checking warnings, long CompileSwiftSources.
npx claudepluginhub avdlee/xcode-build-optimization-agent-skill --plugin xcode-build-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/xcode-build-skills:xcode-compilation-analyzerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when compile time, not just general project configuration, looks like the bottleneck.
Analyzes Swift/Xcode compile hotspots from timing summaries, frontend diagnostics, and type-checking warnings to surface slow compiles, bridging header bloat, and parallelizable work.
Audits Xcode projects for build performance issues in configurations, settings, schemes, scripts, dependencies, and parallelization with approval gates. For slow incremental builds and optimization.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Share bugs, ideas, or general feedback.
Use this skill when compile time, not just general project configuration, looks like the bottleneck.
.build-benchmark/ artifact or raw timing-summary output.Build Timing Summary output from clean and incremental buildsCompileSwiftSources or per-file compilation tasksSwiftEmitModule time -- can reach 60s+ after a single-line change in large modules; if it dominates incremental builds, the module is likely too large or macro-heavyPlanning Swift module time -- if this category is disproportionately large in incremental builds (up to 30s per module), it signals unexpected input invalidation or macro-related rebuild cascading-Xfrontend -warn-long-expression-type-checking=<ms>-Xfrontend -warn-long-function-bodies=<ms>-Xfrontend -debug-time-compilation -- per-file compile times to rank the slowest files-Xfrontend -debug-time-function-bodies -- per-function compile times (unfiltered, complements the threshold-based warning flags)-Xswiftc -driver-time-compilation -- driver-level timing to isolate driver overhead-Xfrontend -stats-output-dir <path> -- detailed compiler statistics (JSON) per compilation unit for root-cause analysispython3 scripts/diagnose_compilation.py \
--project App.xcodeproj \
--scheme MyApp \
--configuration Debug \
--destination "platform=iOS Simulator,name=iPhone 16" \
--threshold 100 \
--output-dir .build-benchmark
This produces a ranked list of functions and expressions that exceed the millisecond threshold. Use the diagnostics artifact alongside source inspection to focus on the most expensive files first.Look for these patterns first:
AnyObject instead of a concrete protocolfinal that are never subclassedpublic/open) on internal-only symbolsbody properties that should be decomposed into subviewsFor each recommendation, include:
If the evidence points to project configuration instead of source, hand off to xcode-project-analyzer by reading its SKILL.md and applying its workflow to the same project context.