Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Agent Test Spec: engine-programmer
Agent Summary
Domain: Rendering pipeline, physics integration, memory management, resource loading, and core engine framework. Does NOT own: gameplay mechanics (gameplay-programmer), build infrastructure (devops-engineer), editor/debug tool UI (tools-programmer). No gate IDs assigned.
Static Assertions (Structural)
-
description:field is present and domain-specific (references rendering / memory / engine core) -
tools:list includes Read, Write, Edit, Bash, Glob, Grep - Model tier is
inherit— frontmattermodel:reads exactlyinherit(tiers:.claude/docs/model-tiers.md) - Agent definition does not claim authority over gameplay mechanics or tool UI
Test Cases
Case 1: In-domain request — appropriate output
Input: "Implement a custom object pool for projectiles to avoid per-frame allocation." Expected behavior:
- Produces an engine-level object pool implementation with acquire/release interface
- Pool is typed to the projectile object type, uses pre-allocated fixed-size storage
- Provides thread-safety notes (or clearly marks as single-threaded-only with rationale)
- Includes doc comments on the public API per coding standards
- Output is compatible with the project's configured engine and language
Case 2: Out-of-domain request — redirects correctly
Input: "Add a wall-jump ability to the player controller." Expected behavior:
- Does NOT produce the wall-jump gameplay code
- Explicitly states that gameplay features belong to
gameplay-programmer - Redirects the request to
gameplay-programmer - If it offers an engine-level query the ability can call (e.g., wall contact and surface normal), that API does not depend on gameplay code (strict dependency direction)
Case 3: Memory leak diagnosis
Input: "Memory usage grows by ~50MB per level load and never releases. We suspect the resource loading system." Expected behavior:
- Diagnoses by measurement before changing code: memory baseline, repeated load/unload cycles, numbers documented (profile before and after)
- Audits the resource loading/caching and object lifecycle code it owns for references that are never released, naming likely causes (orphaned resource handles, circular references, a cache that never evicts)
- Produces a concrete fix for the identified leak pattern
- Provides a test to verify the fix (memory baseline before load, measure after unload, confirm return to baseline)
Case 4: Cross-domain coordination — shared system optimization
Input: "I need to optimize the physics broadphase, but the gameplay system is tightly coupled to the physics query API." Expected behavior:
- Does NOT unilaterally change the physics query API surface (would break gameplay-programmer's code)
- Coordinates with
lead-programmerto plan the change safely - Proposes a migration path: new optimized API alongside old API, with a deprecation period
- Documents the coordination requirement before proceeding
Case 5: Context pass — checks engine version reference
Input: Engine version reference (Godot 4.6) provided in context. Request: "Set up the default physics engine for the project." Expected behavior:
- Reads the engine version reference and notes Godot 4.6 change: Jolt physics is now the default
- Produces configuration guidance that accounts for the Jolt-as-default change (4.6 migration note)
- Flags the GodotPhysics3D→Jolt differences
docs/engine-reference/godot/modules/physics.mddocuments — HingeJoint3Ddampis unsupported under Jolt, collision margins may behave differently, Jolt warns at runtime about unsupported properties — and that existing projects keep their current engine setting; says the reference lists no other API differences rather than inventing any - Does NOT suggest deprecated or pre-4.6 physics setup steps without noting they apply to older versions
Protocol Compliance
- Stays within declared domain (rendering, physics, memory, resource loading, core framework)
- Redirects gameplay feature requests to gameplay-programmer and build infrastructure changes to devops-engineer
- Returns structured findings (implementation code, diagnosis steps, migration plans)
- Coordinates with lead-programmer before changing shared API surfaces
- Checks engine version reference before suggesting engine-specific APIs
- Provides test evidence for fixes (memory before/after, performance measurements)
- Asks "May I write this to [filepath]?" naming the file before writing
Coverage Notes
- Object pool (Case 1) must include a unit test in
tests/unit/engine/ - Memory leak diagnosis (Case 3) should produce evidence artifacts in
production/qa/evidence/ - Engine version check (Case 5) confirms the agent treats VERSION.md as authoritative, not LLM training data