Build your own real game in 8 days using AI as your coding partner. Zero experience needed — just your ideas.
Do this one-time setup before the first day. It takes about 5 minutes. You only need to do it once per computer.
Node.js lets JavaScript run on your computer. Go to nodejs.org, download the LTS version, run the installer, and click Next until it finishes.
The terminal is a text window where you type commands. It looks intimidating but you only need it for one step.
Terminal → EnterTerminal → EnterCopy the command below into your terminal and press Enter. It downloads and installs Claude Code globally. This takes 1–2 minutes.
npm install -g @anthropic-ai/claude-code
In your terminal, type claude and press Enter. The first time you run it, Claude Code will ask you to log in — use the API key your teacher gives you.
claude
Click any day to open a full step-by-step guide — complete with Claude prompts, what to expect, and teacher tips.
This mini-game was built using the exact same steps you'll follow — one Claude prompt at a time.
Day 1: A screen + a player square that moves.
Day 2: Stars falling, score, lives, game over.
Day 3: Space theme, colors, name on screen.
Day 4: High score saves. Bugs fixed.
Day 5: Sound effects + particle explosions.
Day 6: Stars speed up as your score grows.
Every step was just describing what you want — no memorizing code, no tutorials, no copying confusing examples. Just ideas becoming games.
Claude Code is like a senior developer sitting right next to you. The better you describe what you want, the better it performs.
Use plain English. Colors, sizes, what moves, what happens when buttons are pressed. No technical words needed — just describe it like you're talking to a friend.
Open the file Claude gives you. Play it. Notice what feels wrong or missing. That becomes your next prompt. The feedback loop is the skill.
If something breaks, open the console (F12), copy the red error text, and paste it to Claude. If something feels wrong, just describe it. Claude will fix it and explain why.
❌ Too vague. Claude doesn't know what "better" means to you. It might change things you didn't want changed. Always be specific about what you want to improve.
✅ Specific, visual, and measurable. Claude knows exactly what to build. The clearer the instruction, the better the code it writes.
❌ Which bug? Claude can't see your screen. Always open the browser console with F12, copy the exact red error message, and paste it so Claude knows exactly what went wrong.
✅ The error message + the code gives Claude everything it needs to diagnose and fix the exact problem without guessing.
Check off each milestone as you complete it. Your progress is saved automatically in this browser.