Game Build Executor
Turns an approved game design into a minimal BUILD_BRIEF plus a runnable candidate, iterated with replayable evidence.
Dev & CodingAdvanced★ 813⑂ 115AI score 7/10Last updated: Sep 21, 2026
What it does
- Splits building into whitebox (probe the riskiest design question) and production (implement the approved design) stages, declaring
buildStageandbuildPathup front. - Reads
GAME_DESIGN.md(plusART_DIRECTION.mdfor production) and compresses only product boundaries, must-preserve experience facts, run instructions and completion evidence intobuild/BUILD_BRIEF.md. - Forces a minimal-but-complete core loop first: boot → real input → state change → outcome → restart, before any presentation layer.
- Puts all state commits behind a deterministic rules arbiter; the model may parse free input and narrate, but cannot mutate resources, position, knowledge or win/loss directly.
- Pins content/rules/save versions, initial state, seed and input sequences, and logs events so failing paths can be replayed without re-calling online models.
- Never silently swaps to a web build when the target toolchain is missing; records
targetRuntime,testedRuntimeand uncovered items separately, withNOT_AVAILABLE: reasonfor unknowns. - Hands final QA verdicts to the
game-qaskill instead of writing them itself.
Who it's for
- Teams running a multi-stage novel/script-to-game pipeline
- Developers of text or simulation games where an LLM narrates but rules must stay deterministic
- Anyone who wants prototypes backed by reproducible evidence rather than demos that merely look playable
Examples
- "Prototype only the riskiest question — the real-time control feel" → narrowest playable whitebox plus structured observations returned to the design owner.
- "Implement the approved design" → BUILD_BRIEF, a runnable candidate, and one authoritative verification command for
game-qa. - "Fix what playtesters found" → localize the failure to a node, patch it, then replay the failing path and neighbouring counter-examples.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/worldwonderer/novel-to-game/HEAD/skills/game-build/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the skills/game-build folder from the GitHub repo worldwonderer/novel-to-game into my ~/.claude/skills/game-build/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/worldwonderer/novel-to-game.git && mkdir -p ~/.claude/skills && cp -r novel-to-game/skills/* ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
placeholder
View source on GitHub ↗License: MIT