Menu
Use when game implementation quality must be maintainable, understandable, and safe to extend.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when auditing structure, boundaries, coupling, or state-management risks in an existing game project.
Use when auditing UI sounds, reward/failure cues, danger cues, or audio feedback layering in a game.
Use when converting game audit findings into a structured multi-axis scorecard.
Use when choosing a backend profile for a game based on capabilities, project state, and quality target.
Use when reviewing a built or in-progress game against the locked brief before claiming completion.
Use when deciding development mode, quality target, task granularity, or refactor policy for game work.
| name | gsp-production-code |
| description | Use when game implementation quality must be maintainable, understandable, and safe to extend. |
Raise the code-quality floor. Unless the user explicitly asks for a throwaway spike, code should be written as though the project may continue and ship.
Use:
./shared/checklists/production-code-checklist.md./shared/reference/game-dev-abstractions.mdGameManager, controllers, state machines, systems, UI flow owners, sound layers.Follow the gsp-orchestrator output strategy:
docs/game-studio/architecture.md and docs/game-studio/quality-target.md.