From xcode-build-skills
Benchmarks Xcode clean/incremental builds with repeatable timings, summaries, and .build-benchmark/ artifacts for performance baselines and change comparisons.
npx claudepluginhub avdlee/xcode-build-optimization-agent-skill --plugin xcode-build-skillsThis skill uses the workspace's default tool permissions.
Use this skill to produce a repeatable Xcode build baseline before anyone tries to optimize build times.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Use this skill to produce a repeatable Xcode build baseline before anyone tries to optimize build times.
.build-benchmark/.Confirm or infer:
DerivedData path is neededIf the project has both clean-build and incremental-build pain, benchmark both. That is the default.
When benchmarking inside a git worktree, SPM packages with exclude: paths that reference gitignored directories (e.g., __Snapshots__) will cause xcodebuild -resolvePackageDependencies to crash. Create those missing directories before running any builds.
COMPILATION_CACHE_ENABLE_CACHING = YES is detected, run 3 cached clean builds. These measure clean build time with a warm compilation cache -- the realistic scenario for branch switching, pulling changes, or Clean Build Folder. The script handles this automatically by building once to warm the cache, then deleting DerivedData (but not the compilation cache) before each measured run. Pass --no-cached-clean to skip.benchmark_builds.py invocation (no --touch-file flag).--touch-file path/to/SomeFile.swift to touch a representative source file before each build..build-benchmark/.Use the shared helper when possible:
python3 scripts/benchmark_builds.py \
--workspace App.xcworkspace \
--scheme MyApp \
--configuration Debug \
--destination "platform=iOS Simulator,name=iPhone 16" \
--output-dir .build-benchmark
If you cannot use the helper script, run equivalent xcodebuild commands with -showBuildTimingSummary and preserve the raw output.
Return:
--touch-file was used)If results are noisy, say so and recommend rerunning under calmer conditions.
Stop after measurement if the user only asked for benchmarking. If they want optimization guidance, hand off the artifact to the relevant specialist by reading its SKILL.md and applying its workflow to the same project context:
xcode-compilation-analyzerxcode-project-analyzerspm-build-analysisxcode-build-orchestrator for full orchestration