0% XP
🎮 My games
Quest: Shooter maker → Game designer

You can make a game feel amazing.
Now make one people talk about.

Most people never get a game playable. You've shipped several shooters, so you already know movement, combat feel, and finishing builds. That's the hard part. This quest is the next skill: designing, deciding what the game is, why it's fun, and what to build first. AI tools do a lot of the typing. You are the one with the ideas.

Your save code. Write it down!
…
Your work saves to the cloud under this code as you type. On another computer, enter the code in the Save box at the bottom to open it. Anyone with the code can see the work, so keep it private. There's no login and no personal info is collected.

How the quest works

Level 1 · Dream itAnswer 20 questions about your game. Takes about an hour. Your answers save themselves.
Level 2 · Plan itOne click turns your answers into a prompt for Grok. It writes your game's master plan.
Level 3 · Build the smallest fun versionPick what goes in the first playable. Cut everything else (on purpose).
Level 4 · Playtest with friendsWatch friends play, ask 5 questions, then track your weeks.

5 rules of the game

1. Finished beats perfectA small game your friends can play beats a huge one in your head.
2. Protect the core loopThe loop is what you do over and over. If it's not fun, nothing else saves it.
3. One wow firstPick the one moment friends will show each other. Build that first.
4. Friends are the audienceDesign for the people who will actually play it.
5. Write it down as you goFuture you forgets why you made a choice. Notes fix that.
Pro moveIf time is short, nail Questions 4 to 8 and 12. Those matter most.
LEVEL 1

Dream it

Twenty questions. Use full sentences and be specific. "It's fun" is a weak answer. "You have to choose between loud and fast, or quiet and slow" is a strong one.

About the examples
Under each question is a tiny example from a made-up game called Echo Thief. You play a thief in a pitch-black city who can only "see" by throwing sound pings, and the guards hear every ping too. It's not a shooter on purpose. Use it to see what a good answer looks like, then don't copy it. Your game is yours.
Pro move: if you only have 15 minutes, do Questions 4, 5, 6, 7, 8 and 12 first. That's the heart of your game.
LEVEL 2

Plan it

A PRD is just "the game's master plan doc": what the game is, how it plays, and what to build first. You don't have to write it. Grok writes it from your answers. The better your answers, the better the plan.


  
Open Grok ↗

📄 Upload this file to Grok and say: write my game plan. The .md file holds the full prompt with your answers built in, plus your MVP and playtest notes.

Paste it into Grok (or any AI chat). If the plan has weak spots, fix the answers in Level 1. The prompt rebuilds itself and you can run it again. Ask a parent before creating any new account.

LEVEL 3

Build the smallest fun version

This is called your MVP: the smallest version of the game that's still fun and that you can show a friend in 10 to 15 minutes. Fill this out before you write lots of new code. Cutting things is a skill. Great designers do it all the time.

Game working title
One sentence
In the first playable version, the player will and feel
Must-haves
Max 7. Tick each one when it works in your build. If it doesn't help the core loop or the wow moment, it's not a must-have.
Cut from v1 on purpose
At least 5. Writing it down means you won't wonder later. "Later" is not "never".
The wow moment in this version
What success looks like
  • A friend plays for 10+ minutes without you explaining things
  • They can name the coolest thing they did
  • The core loop feels good
  • You know your next 2 to 3 priorities
Target date for first friend playtest
Sign-off

Side quest: AI tool tips

Be the director. You decide what the game is. AI is a fast teammate that types. If you don't know what you want, it will guess, and the guess is usually boring.
Start every chat with a mini brief. Paste the game title, your one sentence, and your must-have list. The AI stays on track.
Ask for one small thing at a time. "Add a ping that shows nearby objects for 2 seconds" works better than "make the whole game."
Paste the exact error. When something breaks, give it the full error text and the code around it. Ask it to explain why it broke so you learn.
Test after every change. Run the game. If it breaks, you know exactly which change did it.
Save copies. Duplicate your project folder (or use Git) before big changes so you can always go back.
Use AI as a critic. Ask: "What's boring about this loop? What would make it surprising?" Then decide for yourself.
Placeholders are fine. Grey boxes and free sounds are enough to test whether a game is fun. Make it pretty after it's fun.
Check what it gives you. AI is sometimes confidently wrong. If code or facts look odd, ask it to double-check, or test it.
Stay private. Don't paste your full name, address, school, or passwords into any AI tool. Ask a parent before signing up for anything.
LEVEL 4

Playtest with friends

A playtest is when someone else plays your game while you watch. It's the fastest way to learn what's actually fun, because your friends will do things you never expected.

Your playtest checklist

👀 What to watch

  • Where do they get lost or stuck?
  • What do they try first?
  • When do they smile, laugh, or say "whoa"?
  • When do they get bored or go quiet?
  • What do they try that you never planned?
  • Do they say "one more try"?

Hard rules: Don't explain. Don't help for the first 3 minutes. Don't defend your game. If they're confused, that's the data. Write it down.

🎤 Ask these 5 questions after

  1. What was the coolest thing you did?
  2. What was confusing?
  3. When were you bored or frustrated?
  4. What would you tell a friend about this game?
  5. Would you play again? What would make you want to?

Your playtest notes

After the playtest, sort the notes
Fix now (it blocked the fun)
Fix later (nice to have)
Ignore (not what the game is about)
Your next 3 priorities

Weekly tracker

Five minutes once a week. It turns "I kind of worked on it" into proof you're getting better.

SAVE

Save your game

Your work saves to the cloud under your save code, and is also kept in this browser as an offline copy. Download a backup now and then too.

Your save code
…
Open your work on another computer
Type the save code you wrote down. This replaces what's on this device with the cloud copy.
Backups

📄 Upload the .md file to Grok and say: write my game plan.

The .md file is for the AI, and it uses the game you have open. The .json file is for restoring later. "All games" saves every game in one file. Importing a single-game file replaces the open game. Importing an all-games file adds those games to My games. The text copy is for pasting into Google Docs, Notes, or Word.

Import by pasting instead
Start a fresh game

Nothing is erased. Your open game stays in My games, and you get a blank one. Use Delete in the My games bar at the top to remove a game.