01 · Test
🧪 Stop & play-test
After the AI adds something, stop and play. Try the new thing.
- Does the new thing work?
- Can I actually use it?
- Did anything else break?
Don’t just say “it works”. Actually test it.
🎮 Holiday Cheat Sheet · Beginner Friendly
Make cool stuff.
Don’t let it break.
You bring the ideas. The AI helps build them. Your most important job is to actually play the game after changes are made.
Tiny tests beat giant “it should work” answers.
You do not have to remember a professional development process.
The AI should help carry it: after a significant change, it should stop and ask you to test before the project gets bigger.
The AI should help carry it: after a significant change, it should stop and ask you to test before the project gets bigger.
Seven useful habits
Keep the fun. Lose the chaos.
These are not homework rules. They are small habits that stop an AI-built project from turning into 3,000 mysterious lines before anyone notices.
02 · Version
💾 Save before big changes
Before a big change, save a copy of the version that works.
Example: PoorFighter-working.html
If the new version goes crazy, you have something safe to return to. You do not need a new copy after every tiny change.
03 · Collaborate
🗣️ Talk to the AI like a team-mate
You do not need fancy prompts.
“Add a shop where I can buy weapons.”
If something breaks, say what you saw. If you are confused, ask “Where do I put this?” or “What does this part do?”
04 · Scope
🧩 One big thing at a time
Try not to add 15 major features at once.
SHOP → TEST
BUYING WEAPONS → TEST
WEAPON UPGRADES → TEST
NEXT FEATURE → TEST
BUYING WEAPONS → TEST
WEAPON UPGRADES → TEST
NEXT FEATURE → TEST
Small steps make bugs much easier to find.
05 · Debug
🐛 When something breaks, don’t panic
You do not need to know the solution. Tell the AI what you did, what you expected and what actually happened.
Observable behaviour is enough to start debugging.
06 · Pause
🏗️ If the game gets really complicated
Stop adding new features for a moment.
“Let’s stop and make sure the current game is organised and working before adding anything else.”
The AI can help clean things up.
07 · You
⭐ You don’t have to be an expert
You do not need perfect prompts. You do not need to understand every line of code.
HAVE IDEASPLAY-TESTREPORTFIXKEEP BUILDING
Something broke?
Describe what happened.
You do not need special programming vocabulary. Give the AI three pieces of evidence and let it help investigate.
What I did“I clicked the attack button.”
What I expected“The player should punch.”
What actually happened“Nothing happened.”
That’s enough to begin. You are reporting evidence, not sitting an exam.
Things you can just say
Normal language works.
The useful skill is not sounding like a programmer. It is being clear about what you want, what you saw and what you do not understand.
New idea
Add a shop where I can buy weapons.
New enemy
I want a boss that shoots fireballs.
Something broke
The boss appears, but I can’t damage it.
Confused
Where do I put this? What does this part do?
The one thing to remember
BUILD → TEST → FIX → NEXT
Have ideas. Make things. Play them. Fix them. Keep building. 🚀