Make your own game

Every game on this shelf was made by a kid, mostly in an afternoon, with an AI helper doing the typing. If you have an idea, you can make one too, and other people will play it.

This month, November 2026

Very small, very big

Make a game about size. Something tiny in a huge world, something enormous in a tiny one, or something that changes between the two.

Stuck? Try one of these:

  • You start the size of a crumb and end the size of a house
  • One tap makes you big, the next makes you small
  • Everything is normal except you, who is the size of a bus

You do not have to use the theme. It is only there for when you cannot think of anything.

How it works

  1. Think of your game. It can be small. The best ones usually are: one thing you do, over and over, that is hard to stop doing.
  2. Ask your AI helper to build it. Claude, or whichever one you use. Copy the words below and paste them in, then fill in your idea where it says so.
  3. Try it, and tell your helper what to fix. Too hard, too fast, too boring? Say so. This is the part where a game turns good.
  4. Send it in. Ask a grown-up to help you put it on the shelf. Another grown-up plays it, and then it is on the site for anyone to find.

What to paste to your helper

Copy all of this. Where it says <<say what you want your game to be>>, write your idea instead.

I want to make a game for Juicebox Arcade, a website where kids publish browser games.

Before you write any code, open https://www.juiceboxarcade.com/agents.md and follow it. It says what the
game file has to look like, what works inside the arcade's sandbox, and how to save progress.
If you cannot open web pages, tell me and I will paste the rules in for you.

My game idea: <<say what you want your game to be>>

When the game is ready, check it yourself before you give it to me:

  curl -X POST --data-binary @game.html \
    -H "Content-Type: text/html" \
    https://www.juiceboxarcade.com/api/validate

Fix everything it lists under "problems". Fix the things under "warnings" too: those are the
ones a grown-up usually sends a game back for. Keep checking until "problems" is empty and
there are no warnings left.

Then give me the finished .html file, and these details so I can send it in at
https://www.juiceboxarcade.com/upload: game name, maker name (a nickname, not my real name), flavour,
what the game is about, the controls in a few words, how many players, and the longer
"how to play".

The longer "how to play" is not an afterthought, so follow the part of the guide called
"Writing the how to play". Five to seven short paragraphs, in my voice, every fact taken from
the code you actually wrote: what you do, how the game is won, the thing nobody would work out
on their own, what loses it with the real number, and a tip or two. It is the only writing on my
game's page, so it is what someone reads before they press play and it is how people find my
game when they search. Send it to the checker along with the file and you will be told if it is
missing or too thin.

If my game has a score, call Juicebox.submitScore(score) once when a run ends, so the arcade can
show my best and today's best. It is already there inside the arcade, so there is nothing to
include; guard it with if (window.Juicebox) so the game still runs on its own.

A few things worth knowing

I have a game, send it in

Helpers that want the exact rules can read the page written for them.