Iron Dragon Games

Making games, because shouting into the void gets old

← All posts

How I Build Games with Claude as a Solo Artist

October 4, 2026  ·  Workflow, Claude Code  ·  Iron Dragon Games

Hello, and welcome to my blog at irondragonstudios.com. This post covers what I consider my working method, or how I go about tackling problems. I hope you find it useful. If so, please stick around.

Ad Here 1

Where I'm coming from

Lately, like everyone else, I imagine, I'm trying to balance my daily frustration with reading the news and keeping up to date while also not going insane. That's where the problem often happens. So here's what I do, and maybe it will help you. If not, no worries. It's all good.

I come from an art background in the game development field, and my tasks were largely centered around creating environments for games like Godzilla and Betrayal at Krondor, going back a few years, and other noteworthy games.

What I mean to say is that I usually focus on the visuals and some real basic logic, very minor scripting to say the least. With AI now available to everyone, you can love it or hate it, but it really does make life simpler for the solo creative, and I definitely consider myself one. So here's how I use Claude on a daily basis.

A typical day with Claude Code

I wake up, log in, get my Claude Code going, and review the projects I currently have. I think I have three different projects at the moment, and I like to mix it up a bit. These are online games, so I'll go into one and play through it. I'll say, "Okay, this feels good. This doesn't feel good. I don't like the color there," or "I don't like the logic on this enemy boss. Can we modify that particular component?" I find that working in smaller chunks, especially with AI, makes the results closer to what I want in the end.

Oftentimes, Claude will go in and have this amazing dialogue back and forth with itself, seemingly. I find it great to read through just to see what problems it's identifying and solving. Then, at the end of the chat, you always get a summary: here's what happened, here's why it happened, and here's the solution. I really appreciate the summaries that clarify the content.

Being particular about the ask

Through all of this back and forth, I've realized that I have to be very particular about the tasks I ask Claude to take on, and about my descriptions of what I want. There have been several times when Claude will come back with something and I'll think, "Well, technically that is 100% correct, but it's not what I was going for." Then I'll modify my prompt: "What I really meant was this. My end goal is this." After a couple more rounds, we end up with a solution I'm happy with.

One thing I find very useful about doing game development with Claude, from a visual person's perspective, is that I'm not going to be writing anything in assembly or C, or even C#, for that matter. I would rather have a visual interface to connect different nodes that do the thing I want. Claude has helped me get there.

A memory bank for the whole site

I recently found that I can create a memory bank for Claude, which I find invaluable. To backtrack a bit: I want to create a website that has a bunch of different games on it, and most of them will follow the same criteria. They need to work on mobile and on PC, and they need to scale differently for different screens and devices. All of that "programmery" stuff has to happen in the background, and I don't know it well enough. So whenever Claude and I figure something out (I say "we," ha), once we get it nailed, I say, "Okay, commit that to memory, and for any future game, let's use this solution to deal with this specific problem."

That has been a lifesaver, especially now that I'm starting new game ideas. I can say, "Let's follow this template and get it all set up with the proper interface, the proper CSS, the proper button sizes, the responsive design." Everything is already in place, and I'm just putting in a new game from there. I've been liking the results. We'll see if anybody else does, but it's been a good learning ground for me, and I plan to build out the site. Whenever I think, "I want my own version of this game," I now have a place and a template to do it.

From napkin sketch to live site

Another component of hosting web games is figuring out all the web stuff. In my case, I decided to go with GitHub Pages. I can commit directly from Claude to GitHub, which then gets hosted on my website. From initial thought to completion, I'm at about half an hour, give or take, from a napkin sketch to actually seeing it live on the web. That was the goal all along.

The automation for committing and pushing my content has been huge for me, because version control has always been a bit dicey, especially for artists. Somebody commits something, there's a conflict, and you're supposed to compare lines of code to see which one to take, and I'm thinking, "I have no idea what to do here." Claude has made that much easier, and I continue to use it that way.

Ad Here 2
© 2026 Iron Dragon Games  ·  About  ·  Contact  ·  Dev Blog  ·  Privacy Policy