Game Build Execution (game-build)
Compresses an approved game design and art direction into a minimal BUILD_BRIEF, then drives implementation of a genuinely playable build with evidence-based iteration.
Dev & CodingAdvanced★ 668⑂ 100AI score 7/10Last updated: Aug 17, 2026
What it does
- Reads
GAME_DESIGN.mdandART_DIRECTION.mdand writesbuild/BUILD_BRIEF.mdcontaining only product boundaries, must-preserve experience facts, run instructions and completion evidence. - Hands implementation to the current coding agent or a stronger model without re-litigating concept, level or art decisions.
- Forces a minimal-but-complete core loop first: launch → real input → state change → outcome → restart.
- Records the actual toolchain plus install/build/start commands and versions; unknowns must be written as
NOT_AVAILABLE: reasoninstead of guessed. - Keeps
targetRuntimeandtestedRuntimeseparate, logs uncovered platform/input/perf items as limitations, and leaves the final QA verdict to thegame-qaskill.
Who it's for
- Teams using the novel-to-game pipeline to turn narrative source material into playable prototypes.
- Anyone who wants to stop agents from claiming "done" on builds that never actually run.
- Producers who want platform, engine and scope decisions frozen in docs before implementation.
Example uses
- "Implement the approved game design as a running prototype" → BUILD_BRIEF first, then the core loop.
- "The target engine toolchain isn't installed" → no silent switch to a web build; NOT_AVAILABLE and limitations are recorded instead.
- "Get this ready for QA" → produces one authoritative verification command and minimal observable state so game-qa can run clean start → core action → outcome → restart in a single pass.
· · · 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.
- Open a terminal.
- Clone the repository:
git clone https://github.com/worldwonderer/novel-to-game.git - Create the skills directory:
mkdir -p ~/.claude/skills - Copy the skills:
cp -r novel-to-game/skills/* ~/.claude/skills/(copy all of them, since game-build depends on sibling skills such as game-qa). - Verify the contract docs exist under
~/.claude/skills/game-build/references/. - Restart Claude Code and confirm the skill is recognized.
- Prepare
PRODUCT_BRIEF.md,GAME_DESIGN.mdandART_DIRECTION.mdin your project, then ask Claude to "build the game from the approved design".
View source on GitHub ↗License: MIT