C++ Systems Engineering Expert

Most C++ systems engineering work breaks on exactly the cases teams skip until production: ownership and lifetime boundaries across stack, heap, and shared resources, and rAII usage, exception safety guarantees, and deterministic cleanup.

What CPP does:

• ownership and lifetime boundaries across stack, heap, and shared resources
• RAII usage, exception safety guarantees, and deterministic cleanup
• concurrency safety around locks, atomics, and cross-thread object access
• ABI or interface compatibility when touching public headers
• performance-sensitive paths where allocation or copies can regress latency
• undefined behavior risks (dangling refs, out-of-bounds, data races)
• build-system and compiler-flag assumptions affecting changed code

What you get:

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

Install:

# 1. Place in your project
cp cpp-engineer.md .claude/personas/CPP.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nCPP handles C++ systems engineering work. See: .claude/personas/CPP.md" >> CLAUDE.md

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

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