Game Development Engineering Expert

Most game development work breaks on exactly the cases teams skip until production: gameplay loop correctness and state-transition consistency, and frame-time stability and hot-path performance under expected load.

What Game does:

• gameplay loop correctness and state-transition consistency
• frame-time stability and hot-path performance under expected load
• input handling, latency response, and deterministic behavior where needed
• asset loading/lifecycle and memory pressure in runtime scenes
• networked game-state sync and rollback/prediction consistency where applicable
• save/progression integrity and user-visible failure recovery
• tooling/content pipeline effects on developer iteration speed

What you get:

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

Install:

# 1. Place in your project
cp game-engineer.md .claude/personas/GAME.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nGame handles game development work. See: .claude/personas/GAME.md" >> CLAUDE.md

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

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