Files
avdlee__xcode-build-optimiz…/AGENTS.md
T
Antoine van der Lee 608a82e0b4 Refocus all skills on wall-clock build time as the primary success metric
User feedback showed the skills were over-indexing on cumulative task time
(which Xcode parallelizes) and presenting it as build-time savings. This led
to many source-level fixes that reduced compiler workload without actually
reducing how long the developer waits.

Key changes:
- AGENTS.md: wall-clock first principle inherited by all skills
- Orchestrator: blocking-vs-parallel heuristics, impact language templates,
  wall-clock-first final report
- Report script/template: timing-table disclaimers, wait-time impact field,
  plain-language verification
- Compilation analyzer: parallel workload labeling when not on critical path
- Project/SPM analyzers: wall-clock qualifier on prioritization tiers
- Fixer: wall-clock delta leads reporting, honest language when task metrics
  improve but wait time does not
- Benchmark artifacts: documents wall-clock vs cumulative distinction
- Recommendation format: new wait_time_impact required field
2026-03-23 08:30:21 +01:00

2.0 KiB

Agent Guidance

This is a multi-skill Xcode build optimization repository.

Layout

  • skills/ contains six installable Agent Skills, each with a SKILL.md entrypoint.
  • references/, schemas/, and scripts/ at the repo root are shared support files used by the skills.
  • .claude-plugin/ contains plugin and marketplace metadata.

Skills

Skill Purpose
xcode-build-benchmark Repeatable clean and incremental build benchmarking
xcode-compilation-analyzer Swift compile hotspot analysis and source-level recommendations
xcode-project-analyzer Build settings, scheme, script phase, and target dependency auditing
spm-build-analysis Package graph, plugin overhead, and module variant review
xcode-build-orchestrator Orchestrator: benchmark, analyze, prioritize, approve, delegate fixes, re-benchmark
xcode-build-fixer Apply approved optimization changes and verify with benchmarks

Rules

  • Wall-clock build time (how long the developer waits) is the primary success metric. Every recommendation must state its expected impact on wall-clock time. If the impact cannot be predicted, say so.
  • Cumulative task time from the Build Timing Summary is diagnostic evidence, not proof of wall-time impact. Xcode parallelizes aggressively, so reducing parallel task time may produce zero wait-time improvement.
  • Recommend-first by default. Never apply project, source, or package changes without explicit developer approval.
  • Benchmark before optimizing. Use .build-benchmark/ artifacts as evidence.
  • Treat clean and incremental builds as separate metrics.
  • The orchestrator (xcode-build-orchestrator) is the primary entrypoint for end-to-end work.
  • Shared references and schemas live at the repo root, not inside individual skills.

Handoff Between Skills

When one skill identifies an issue outside its scope, read the target skill's SKILL.md under skills/ and apply its workflow to the same project context. Pass along any benchmark artifacts or timing evidence already collected.