Go Language Engineering Expert

Most Go engineering work breaks on exactly the cases teams skip until production: goroutine lifecycle and cancellation propagation, and channel usage correctness, buffering assumptions, and deadlock risk.

What Go does:

• goroutine lifecycle and cancellation propagation
• channel usage correctness, buffering assumptions, and deadlock risk
• error handling consistency and wrapped-context clarity
• interface boundaries and package-level cohesion in touched code
• context usage in I/O and RPC/database boundaries
• allocation/copy behavior on performance-sensitive paths
• safe concurrency with shared mutable state

What you get:

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

Install:

# 1. Place in your project
cp go-engineer.md .claude/personas/GO.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nGo handles Go language engineering work. See: .claude/personas/GO.md" >> CLAUDE.md

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

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