In Part 1 we got to know Claude Code, installed it, and learned how it keeps us in control. Now it’s time to actually use it, and to have some fun while we’re at it.
In this part we’ll build a small game called Star Catcher. Colourful stars fall from the night sky, you move a basket left and right to catch them, and your score goes up with every catch. Miss three stars and the game is over. It’s simple enough to build in one sitting, but fun enough that you’ll want to show it to someone.
Along the way you’ll learn the handful of habits and shortcuts that make working with Claude Code feel calm instead of confusing. No coding knowledge needed, just the willingness to describe what you want in plain English.
Step 1: Give Your Game Its Own Folder
Before you start, create a new, empty folder for this project. Call it something simple like star-catcher. Think of it like opening a new file at the bank for a new customer. Everything related to that customer goes into that one file, nothing gets mixed up with anyone else’s papers. Claude Code works the same way, it only works inside the folder you start it in, so a dedicated folder keeps things tidy and safe.
Open your terminal, go into that folder, and start Claude Code
cd star-catcher claude
Step 2: Describe the Game Like You’d Explain It to a Friend
Here’s the secret most beginners don’t know, you don’t need technical words to describe a game. You just need to explain it the way you’d explain it to a friend who has never played it. Ask yourself four simple questions:
- What does it look like? A dark night sky with colourful stars.
- What do I control? A basket at the bottom of the screen.
- How do I win points? Catch a falling star.
- How does it end? Miss three stars.
That’s it. Those four answers are your whole game idea. Now we turn them into a request.
Step 3: Ask for a Plan Before Anything Gets Built
The most useful habit for a beginner is ask Claude Code to plan first, build later. Claude Code has something called Plan Mode. In this mode it can think and look around, but it is not allowed to create or change any files. It only tells you what it intends to do. Turn it on by pressing Shift + Tab until you see “plan mode on” at the bottom of the screen. It’s like asking a tailor to show you the design sketch before cutting the fabric. If the sketch is wrong, you’ve lost nothing. Now type this:
I want to make a simple game called Star Catcher that opens in a web browser. The background is a dark night sky. Colourful stars fall slowly from the top of the screen. At the bottom there is a basket. I move it left and right with the arrow keys. When I catch a star, I get one point. If I miss three stars, the game is over and it shows my final score with a "Play Again" button. Show my score and remaining lives at the top. Make it look bright and friendly. Keep everything in one file so it's easy to open. Explain your plan in plain English.
Notice what this request does. Each line describes one thing you’d see or do while playing. No technical terms, no guesswork. The line “keep everything in one file” simply means you’ll get a single file you can double-click to play.
Read the plan Claude Code gives back. If something isn’t what you imagined, just say so, “Make the stars yellow and gold only” or “I’d rather use the mouse than arrow keys.” When you’re happy, approve the plan and let it start building.
Step 4: Play Your Game
Once building starts, Claude Code will ask your permission before saving the game file. Remember from Part 1, it asks before it acts. Take a moment to read what it’s doing, then approve. When it’s done, ask:
How do I open the game and play it?
It will tell you which file to double-click. Your game opens in your web browser. Catch a few stars. You just made a game.
Step 5: Make It More Fun, One Small Change at a Time
This is where it gets enjoyable. Play your game, notice what feels boring or too easy, and ask for one improvement at a time
- “Make the stars fall a little faster every time I score 5 points.”
- “Add a red bomb that sometimes falls. If I catch it, I lose a life.”
- “Add a small sparkle effect when I catch a star.”
- “Show my best score so I can try to beat it.”
After each change, refresh your browser and play again. Think of it like a chef tasting the curry after every spice. Add one thing, taste, then decide on the next. If you add five things at once and it tastes wrong, you won’t know which one caused it.
Step 6: Give Claude Code a Notebook About Your Game
Each time you start Claude Code fresh, it doesn’t automatically remember the details of your last chat. Repeating “it’s a star-catching game, keep it bright and friendly, I like simple controls” every time gets tiring. The fix is a small note file called CLAUDE.md. Claude Code reads it every time it starts in that folder. Type:
/init
Claude Code will look at your project and write a starter version of this note for you. You can then add your own preferences in plain English.
Now your game is ready, hand it to a friend or your kids and watch. They’ll find things you never noticed, and you’ll have your next list of improvements. Your first game is simple, and that’s the point. Every game developer started with something small. That’s it for Part 2. Build your game, play it, break it, undo it, and make it better.
About the Author: Imtiaz is working in a financial organization in Bangladesh and having experience in system, network and security administration. Feel free to contact with him on LinkedIn or Twitter.