Files
avdlee__xcode-build-optimiz…/AGENTS.md
T
Antoine van der Lee 753cff9cb7 Update Xcode build optimization skills and documentation
- Added a new skill: `xcode-build-fixer` for applying approved optimization changes.
- Introduced `xcode-build-orchestrator` to manage the optimization workflow.
- Updated existing skills to reflect new names and roles, including `xcode-compilation-analyzer` and `xcode-project-analyzer`.
- Revised documentation across multiple files to include six installable skills and their purposes.
- Enhanced contribution guidelines to align with the new skill structure.
- Updated plugin metadata to reflect the addition of new skills.
2026-03-15 13:07:12 +01:00

1.6 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

  • 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.