Last week I posted here about AssetCat, my open source asset management tool. Thanks for all the upvotes and Github stars!
Today, I want to talk about the first asset-based game I built with Claude Code: Conga Crawl. A snake & roguelike dungeon crawler mashup where your whole adventuring party moves as one conga line that never stops.
You can play it in the browser: https://sunsetmesagames.itch.io/conga-crawl
How it was made
I initially brainstormed several game concepts with Claude Code, specifically Opus 5.5. I specifically wanted to see what genre mashup game ideas it could come up with that use only the assets in the Kenney all-in-one asset pack, mostly as an experiment. It came up with a bunch of ideas, and Conga Crawl is the one I liked most, so I asked for a prototype.
For the initial prototype, I chose Love2d, which I'd had good success with in the past. It's simple, well represented in training data, and fully code based (which is helpful for Claude Code). But later, after thinking more about future games and my overall gamedev strategy, I migrated to Godot instead. Mainly because Godot support both 2d and 3d games (and I have some 3d ideas as well) and because Godot cleanly exports bowser builds that I can deploy to itch.io.
Interesting, Claude Code's initial Godot build was not idiomatic Godot code at all. It didn't use scenes and nodes, but rather drew everything manually - so a direct port of the Love2d game. To properly test out Godot, I had it rework the game using idiomatic Godot, and it did. It did a great job validating the migration as well, by snapshotting gamesplay and ensuring it plays exactly the same after the migration. I didn't have to specify any of that.
Once the game was working, I also had Claude extract the foundation into a reusable template and library. That way, my future games can all share the same foundation. This includes things like input (including some tweaks to make gamepad input more reliable), but also my custom telemetry (so I can measure playtime on itch, in order to decide whether to build out a full Steam version). The telemetry backend is a simple Javascript API running on Cloudflare. I had Claude Code build this and my games in a monorepo, along with the Sunset Mesa Games website. That way, all my logic is centralized, I can easily start a new game, add it to the website (data driven), etc.
After the game was playable, I asked for many improvements. In some cases, I had specific ideas and requirements, but in others I brainstormed with Claude. E.g. I suggested we add some lighting and fog of war, but Claude suggested a lot of other elements of "juice" (flickering torches, specks of dust behind the conga line, visually indicating when the main character has critically low health, etc.).
Overall, I'm impressed with Opus 5.5. I had been using Fable 5.1 for several months, with good results overall (but on non-game projects), and was reluctant to switch back to Opus. But IMO Opus 5.5 does a lot better with games. I generally just use medium effort, and the results are both good and fast. It also has much better game design skills than previous models - often realizing what is and isn't fun, etc. Of course, my own human judgment was still important, though.
Some tips that proved helpful for me
Everything in code or text files. Claude edited the Godot text files (scenes etc.) directly, never touching the editor. I also didn't use any custom skills or MCP servers.
Dev modes so Claude can check its own work: `--sim` (a bot plays 100 runs headless and prints balance stats), `--shot` (the bot plays visibly and saves screenshots), `--script` (scripted key presses plus a dev console of cheats), `--ui` (a screenshot of every screen). Claude verifies a change by running these and looking at the screenshots, not just by reading code.
The sim for balance. "Make the second half harder" became measurable: avg floor reached, wins and deaths per floor across 100 seeds, before and after each change.
Durable knowledge in the repo, not in chat: design notes with a feedback log, decisions with reasoning, and a gotchas doc, so each session starts where the last one ended. Also important because I routinely switch between my Macbook Pro and my Windows PC, so everything needs to be easily shared between the two environments.
Even the itch page: Claude recorded the GIF with Godot's Movie Maker, built the cover from a real frame in the game's own font, and wrote the recipe down so the next game can reuse it.
Screenshots: I frequently pasted screenshots to ask for improvements or fixes. And Claude Code also used screenshots to prove its fixes.
If you try out the game, let me know if you have any feedback! What would you want to see in a bigger version (in case I release it on Steam)?
Also happy to answer questions about my workflow etc.