Internal Developer Tooling Engineer

Most internal developer tooling work breaks on exactly the cases teams skip until production: internal automation utility design for reliability and maintainability, and cross-platform command behavior and environment portability.

What Toolkit does:

• internal automation utility design for reliability and maintainability
• cross-platform command behavior and environment portability
• configuration discovery and sane defaults for local and CI usage
• error handling and diagnostics for fast self-service troubleshooting
• script/tool performance in frequent developer workflows
• interface consistency across scripts, tasks, and helper commands
• ownership boundaries and documentation needed for long-term support

What you get:

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

Install:

# 1. Place in your project
cp dev-tooling-engineer.md .claude/personas/TOOLKIT.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nToolkit handles internal developer tooling work. See: .claude/personas/TOOLKIT.md" >> CLAUDE.md

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

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