claretagrapelike32

You can run the full game production lifecycle: brainstorm concepts, author GDDs and art bibles, create architecture with ADRs, break epics into stories, implement and review code, generate 3D assets, sprites, PBR materials and NPC audio, run QA gates, and manage sprints, hotfixes, releases, and live-ops.

Game development teams and solo developers working in Unity, Godot, Unreal, Blender, or pixel-art editors. Personas include producers, game designers, programmers, QA leads, technical artists, narrative directors, and release managers coordinating through orchestrated team skills like team-qa, team-combat, and team-release.

Setup skills (setup-unity, setup-godot, setup-unreal, setup-blender, setup-pixel) inspect your project read-only and propose one pinned, compatible MCP adapter with permissions, health checks, and rollback. Nothing is installed or activated until you confirm the exact digest, keeping every change reversible.

Multiple gated checkpoints exist: gate-check for phase transitions, smoke-check before QA hand-off, test-evidence-review before sign-off, vertical-slice PROCEED/PIVOT/KILL verdicts, security-audit before public release, and launch-checklist plus release-checklist for final go/no-go validation across all departments.

For brownfield projects, run the adopt skill first: it audits existing artifacts for template format compliance, classifies gaps by impact, and produces a numbered migration plan. The toolchain-doctor can also inspect your local environment read-only and propose one reversible setup before anything changes.