Donchitos/Claude-Code-Game-Studios v1.3.0

v1.3.0 — make me a game

on GitHub

"Make me a game" is the main road: /prototype asks a few questions, writes a one-page brief, builds a browser game from it, checks it against the brief, and fixes what the check finds before you get it. After you play it, you change it by asking, and when you like it you grow it into a real web project and build on it one feature at a time. A minor release after 1.2.0.

Highlights

• Make me a game. One round of at most about eight questions drawn from the genre, with the usual answer shown so "you pick" works. A vague idea gets two or three one-line pitches first. The answers become design/game-brief.md: your words kept exactly, how it looks, its first minute, its challenge, your systems, and Keep, Avoid and Out of scope lines.
• The build and its check. The game is built in your session as a browser game in prototypes/<name>/ that opens with a double-click: no emoji art, no copy of another game, and not trivially easy. A short scripted check runs before you get it: a headless browser presses a few keys, a screenshot is compared with the brief, and every line of the brief is marked pass, missing, broken or not assessed. The handover card shows what is still broken and what was guessed, and ends "Not yet played by a person".
• Change it after play. Each change is checked against the brief's Keep, Avoid and Out of scope lines, gets a light check, and is one commit you can go back to. "Too easy" adds a new rule before any number moves.
• The tweak panel, added when you ask to tune: a slider for each value in config.js, opened with the backquote key or ?tune. Paste the saved block back and /prototype writes it into config.js.
• Share it, or bring your own game in. one-shot-share.sh makes a copy without the working files; /prototype --from <path> copies in a browser game you already have so it can be changed and grown.
• Grow it. On PROCEED, a one-shot grows into a Vite and TypeScript web project with data files, tests and a same-seed run, then takes one feature a sitting. Stories, epics and gates only when you ask for them.
• /cut, a new skill: cuts and a polish list to finish the game from its brief, and you pick each cut.
• Web is an engine. engine.name: Web, with three.js, Phaser and PixiJS starters and a pinned web reference. Every engine's folders and commands come from one table, .claude/engines/engines.tsv. Genre sheets for 69 genres live in .claude/genres/.
• Studio mode. The agents, the team-* pipelines and the design-document ladder are now called studio mode, and /start and /next-step say when it fits.
• Renamed skills: /help is /next-step, /settings is /project-settings, /changelog is /write-changelog. The old names still work.
• Fixes, among them: rotating the session state can no longer lose its notes (#158); git commit -m "message" -a is checked on a machine without Python (#155); the Godot reference says Vulkan is the Windows default and Compositor is a resource (#143); five skills that change a file in place can now edit it (#156). The full list is in the CHANGELOG.

What is shown, and what is not yet

In a blind comparison, the brief written from these questions was picked over a hand-written brief for all three game ideas tried. Growing was shown on one game, grown through six stories. The engine route and deepening one system in a design document are built but not yet shown in a test like these.

Upgrading from 1.2.0

Take .claude/scripts/, .claude/hooks/, .claude/genres/ and .claude/engines/ whole. If you edited settings.json, every hook command has a new form, and there are 28 new allow rules for the read-only scripts: UPGRADING.md → v1.2.0 → v1.3.0 lists every merge and the three renamed skill specs to delete. A skillOverrides entry or permission rule naming an old skill needs the new name.

Tested on

• Platforms: Windows, Linux (bash 5 and 3.2) and macOS (bash 3.2 with BSD tools), with and without jq.

Contributors

Thank you to everyone who reported, proposed or fixed something in this release:

• @rudycelekli: found and proposed fixes for three bugs. Rotating the session state could lose its notes (#158). The commit check missed -a after a quoted message on a machine without Python (#155). Five skills could not edit a file in place (#156).
• @mamonbleau: reported that the Godot reference had the Windows renderer default and Compositor wrong (#143).

Full changelog: v1.2.0...v1.3.0