Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Game Build Execution (game-build)

Compresses an approved game design and art direction into a minimal BUILD_BRIEF plus an actually runnable game candidate, iterated with replayable evidence.

Dev & CodingAdvanced★ 833⑂ 117AI score 8/10Last updated: Oct 3, 2026

What it does

  • Forces an upfront declaration of buildStage (whitebox vs production) and buildPath (template vs custom) so risk probing and real production never blur together.
  • Requires GAME_DESIGN.md for whitebox and additionally ART_DIRECTION.md for full candidates, then emits build/BUILD_BRIEF.md plus a running candidate.
  • Enforces a shared build loop: minimal complete core loop first (boot → real input → state change → outcome → restart) before any extra scope.
  • Preserves reproducible initial states and input paths, fixes seeds for randomness, and replays failing paths after revisions.
  • Writes back the real toolchain, install/build/start commands and versions; unknowns must be recorded as NOT_AVAILABLE: reason rather than guessed.
  • Conditionally loads side contracts for Blender assets, playable-model behavior, TTS, and generative media pipelines.

Who it's for

  • Teams running a multi-stage novel-to-game production pipeline
  • Indie developers whose design docs never become a playable build
  • Teams that want hard rules against docs describing features that no longer exist

Examples

  1. "Prototype the riskiest design question" → if real-time feel is the core risk, it refuses to downgrade the project to a text game and builds a whitebox that actually exposes that risk.
  2. "Implement the approved design" → inherits ART_DIRECTION's observable visual constraints, produces a production candidate, and hands game-qa one authoritative verification command covering clean start → core action → designed outcome → restart.
  3. Target toolchain unavailable → it must not silently switch to a web build; it records targetRuntime, testedRuntime, and uncovered platform/performance/packaging limitations separately.

· · · 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/zenstory-ai/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)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download 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 zenstory-ai/novel-to-game into my ~/.claude/skills/zenstory-ai-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/zenstory-ai/novel-to-game.git && mkdir -p ~/.claude/skills && cp -r novel-to-game/skills/game-build ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repo: git clone https://github.com/zenstory-ai/novel-to-game.git
  3. Create the skills directory: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r novel-to-game/skills/game-build ~/.claude/skills/
  5. Verify the references/ contract files (build-brief-contract.md, etc.) came along.
  6. Copy the sibling skills (design, art direction, game-qa) the same way if you want the full pipeline.
  7. Restart Claude Code and try a prompt like "turn this design into a running game" to confirm the skill triggers.
View source on GitHub ↗License: MIT