Claude Code Game Studios: a browser game from one line
Give it one line of a game idea; a few questions and a one-page brief later, a browser game opens with a double-click
- Who
- An MIT-licensed Claude Code template by Donchitos, for one person with a game idea up to a team that wants process.
- When
- Public since February 2026; v1.3.0, "make me a game", made /prototype the main road on 9 November.
- Where
- Runs inside Claude Code on Windows (Git Bash), macOS and Linux; the games open in a browser on your own machine.
What was hard
Ask an AI to make you a game and something comes out. But what you wanted was never written down, so the result is thin; or the other way, documents pile up and the game you can play comes late. And "done" sometimes means a menu drawn off the screen.
What it does about it
/prototype asks one round of questions fitted to the genre and turns the answers into a one-page design/game-brief.md. Say Build it and it makes a game in prototypes/<name>/ from that brief alone, one that opens with a double-click. Before handing it over, a headless browser presses a few keys and takes a screenshot, and every line of the brief is marked built, missing or broken. The card still ends "Not yet played by a person": whether it is fun is yours to find out.
How it runs inside
- 1
You → /prototype
/prototype + one line of ideaThe skill picks questions from the genre's sheet and asks them in one round, each with a usual answer..claude/skills/prototype/SKILL.md - 2
/prototype → design/game-brief.md
answers → a one-page briefYour words kept as typed, plus the look, the first minute, the challenge and features; it waits for Build it..claude/skills/prototype/references/one-shot-1-card.md - 3
Claude Code → prototypes/<name>/
one-shot-new.sh → index.html, config.jsMakes the folder from the starter and builds the game from the brief alone, every tuning value in config.js..claude/scripts/one-shot-new.sh - 4
one-shot-check.sh → prototypes/<name>/
headless browser: keys + screenshotPlays from a fresh start with set keys, measures errors, freezes and overlapping text, and takes a shot..claude/scripts/one-shot-run.sh - 5
one-shot-check.sh → design/game-brief.md
each line: pass / missing / brokenMarks every brief item from a screenshot or a line of code and keeps it in evidence/checklist.tsv..claude/skills/prototype/references/one-shot-2c-self-check.md - 6
Claude Code → You
handover card + play screenshotWhat to open, what is still broken, what was guessed, ending "Not yet played by a person"..claude/skills/prototype/references/one-shot-3-handover.md - 7
You → prototypes/<name>/
double-click index.html, playPlay it, then ask for changes, or grow it into a web project when you like it..claude/skills/prototype/references/one-shot-3-handover.md
What goes in, what comes out
Is it for you
Good for
- Trying a game idea with your hands the same evening
- A game jam, where a playable prototype matters more than paperwork
- Picking up a browser game you already have and growing it (--from)
- Checking the fun first, even if Godot, Unity or Unreal comes later
Not for
- Per the README, what has been tested is the first build and one game grown through six stories; the engine route is built but not yet tested the same way.
- The automatic check only sees that it opens, responds and has readable text; it does not judge fun.
- Without Chrome, Edge or Chromium the play checks are not assessed, and without Python 3 every setting falls back to its default.
- Your own Claude Code session builds the game; "build it at medium" is cheaper and thinner.
Reviewed by Devalley’s editor before publishing. How the column is made