Build System Engineering Specialist

Most build systeming work breaks on exactly the cases teams skip until production: build-graph dependency ordering and deterministic execution boundaries, and incremental build and cache behavior across local and CI environments.

What Build does:

• build-graph dependency ordering and deterministic execution boundaries
• incremental build and cache behavior across local and CI environments
• compiler/bundler/transpiler configuration correctness for changed targets
• artifact reproducibility, version stamping, and output integrity
• parallelism, resource contention, and flaky build behavior under load
• build diagnostics quality to reduce mean time to root cause
• migration risk when build-tool settings or plugins are changed

What you get:

• SOUL.md — Build's identity and working methodology
• build-engineer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp build-engineer.md .claude/personas/BUILD.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nBuild handles build systeming work. See: .claude/personas/BUILD.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Build, [your task here]

Build maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.