Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Skill Test Spec: /test-setup
Skill Summary
/test-setup [force] scaffolds the test framework for the configured engine.
It reads engine.name from project.yaml (falling back to
technical-preferences.md) and stops with a /setup-engine redirect when
neither names an engine. It checks for existing infrastructure, presents a plan,
and asks "May I create these files? I will not overwrite any test files that
already exist at these paths." before writing.
It creates tests/README.md, tests/smoke/critical-paths.md,
production/qa/evidence/, .github/workflows/tests.yml, and the engine's test
root: for Godot tests/unit/ and tests/integration/ (placeholder files, and
no runner script — gdUnit4's addons/gdUnit4/bin/GdUnitCmdTool.gd is the
runner); for Unity Assets/Tests/EditMode/ and Assets/Tests/PlayMode/ with
their .asmdef files; for Unreal Source/<Module>/Private/Tests/. When the
infrastructure already exists it exits early unless force is passed, and
force only creates missing files — it never overwrites. No director gates
apply. The verdict is COMPLETE when the scaffold is in place.
Static Assertions (Structural)
Checked against the SKILL.md by /skill-test spec — no fixture needed.
- Has required frontmatter fields:
name,description,argument-hint,user-invocable,allowed-tools - Has ≥2 phase headings
- Contains verdict keyword: COMPLETE
- Contains ask-before-write language before creating files ("May I create these files?")
- Has a next-step handoff (Phase 6 Next steps:
/qa-plan sprint,/smoke-check)
Director Gate Checks
None. /test-setup is a scaffolding utility. No director gates apply.
Fixture Defaults
Every case's project.yaml sets modes.rigor: minimal and
modes.automation: collaborative, with no project.local.yaml, unless its own
Fixture says otherwise. Rules: studio-tests/CLAUDE.md §
Fixture defaults.
Test Cases
Case 1: Happy Path — Godot project, scaffolds GdUnit4 test structure
Fixture:
project.yamlhasengine.name: Godottests/does not exist;addons/gdUnit4/is not installed; no CI workflow- The user approves the plan
Input: /test-setup
Expected behavior:
- Phase 1 reports "Engine: Godot. Test directory: not found. CI workflow: not found."
- Phase 2 presents the plan:
tests/unit/,tests/integration/,tests/smoke/,tests/README.md,production/qa/evidence/,.github/workflows/tests.yml— and no runner script - Skill asks "May I create these files? I will not overwrite any test files that already exist at these paths."
- On approval:
tests/unit/.gdignore_placeholder,tests/integration/.gdignore_placeholder,tests/README.md(with the Installing GdUnit4 steps and the capital-Uaddons/gdUnit4/path),tests/smoke/critical-paths.md, and a file underproduction/qa/evidence/ .github/workflows/tests.ymlusesgodot-gdunit-labs/gdUnit4-action@v1withversion: 'installed'andchecks: write- The documented test command matches
coding-standards.md's CI command:godot --headless -s -d --remote-debug tcp://127.0.0.1:0 res://addons/gdUnit4/bin/GdUnitCmdTool.gd -a res://tests --ignoreHeadlessMode - Phase 6 summary; verdict COMPLETE
Assertions:
-
tests/unit/,tests/integration/,tests/smoke/andproduction/qa/evidence/all exist afterwards (each holds a written file) - No custom runner script is written (the old hand-written runner loaded a file gdUnit4 never shipped and failed every run)
- The test command matches the coding-standards.md CI command
- Approval is asked before any file is created
- Verdict is COMPLETE
Case 2: Unity Project — Scaffolds Unity Test Runner with asmdef
Fixture:
project.yamlhasengine.name: UnityPackages/manifest.jsonlistscom.unity.test-framework- No
Assets/Tests/; the user approves the plan
Input: /test-setup
Expected behavior:
- Skill reads engine → Unity; the Test Framework package check passes
- The plan places unit and integration tests under
Assets/Tests/— Unity compiles onlyAssets/andPackages/— not undertests/unit/ - Skill generates
Assets/Tests/EditMode/EditModeTests.asmdef(Editor-only) andAssets/Tests/PlayMode/PlayModeTests.asmdef .github/workflows/tests.ymlrunsgame-ci/unity-test-runner@v4foreditmodeandplaymode, and theUNITY_LICENSEsecret is noted- The README's Running Unity tests note gives two runs — Edit Mode into
test-results/editmode.xml, Play Mode intotest-results/playmode.xml - The Phase 6 gate note names Unity's test root (
Assets/Tests/EditMode/andAssets/Tests/PlayMode/), nottests/unit/andtests/integration/ - Approval is asked before writing; verdict COMPLETE
Assertions:
- Tests are under
Assets/Tests/, nevertests/or a top-levelTests/(neither is compiled: 0 tests, "Passed") -
.asmdeffiles are generated - EditMode and PlayMode runner config is present, in CI and as two local runs with separate results files
- The gate note names the Unity test root
- Verdict is COMPLETE
Case 3: Infrastructure Already Exists — Early exit, nothing re-initialized
Fixture:
- Godot project;
tests/unit/,tests/integration/,.github/workflows/tests.ymlandaddons/gdUnit4/bin/GdUnitCmdTool.gdall exist - No
forceargument
Input: /test-setup
Expected behavior:
- Phase 1 reports "Engine: Godot. Test directory: found. CI workflow: found."
- Skill says: "Test infrastructure appears to be in place. Re-run with
/test-setup forceto regenerate. Proceeding will not overwrite existing test files." - No plan approval is requested and no file is written
Assertions:
- Skill does NOT re-initialize when the infrastructure exists
- The message points to
/test-setup force - No existing file is modified and no new file is written
Case 4: No Engine Configured — Redirects to /setup-engine
Fixture:
project.yamlhas noengine.name;technical-preferences.mdshows[TO BE CONFIGURED]for Engine
Input: /test-setup
Expected behavior:
- Skill checks
project.yaml, thentechnical-preferences.md— no engine - Skill stops: "Engine not configured. Run
/setup-enginefirst, then re-run/test-setup." - No directories or files are created
Assertions:
- Error message explicitly states engine is not configured
-
/setup-engineis suggested as the next step - No write tool is called
- Verdict is not COMPLETE (blocked state)
Case 5: Director Gate Check — No gate; test-setup is a scaffolding utility
Fixture:
- Engine configured, tests/ does not exist
Input: /test-setup
Expected behavior:
- Skill scaffolds and writes all test framework files
- No director agents are spawned
- No gate IDs appear in output
Assertions:
- No director gate is invoked
- No gate skip messages appear
- Verdict is COMPLETE without any gate check
Protocol Compliance
- Reads the engine (
project.yaml, thentechnical-preferences.md) before generating any scaffold - Generates engine-appropriate test runner config and CI workflow (not generic)
- Puts unit and integration tests in the engine's test root (
tests/for Godot,Assets/Tests/for Unity,Source/<Module>/Private/Tests/for Unreal) - Creates
production/qa/evidence/— the path the Phase 6 summary reports - Asks approval before creating files
- Exits early when infrastructure exists;
forcecreates only missing files and never overwrites - Verdict is COMPLETE when scaffold is in place
Coverage Notes
- Unreal Engine test scaffolding (
Source/<Module>/Private/Tests/README.md, a self-hosted Windows CI runner) is not separately fixture-tested. - The
forcepath on a partial scaffold (create only the missing files) is covered by protocol compliance, not by its own case. - The case where tests/ exists but is from a different engine (e.g., Unity tests in a now-Godot project) is not tested.
- A Unity project without
com.unity.test-framework(the skill asks to add the version the installed editor bundles, never a copied number) is not tested.