Free games
made with AI

Browser games built by Claude, Anthropic's AI, from a written prompt. Free to play with nothing to download, on your phone or computer, most played first. Each one comes with the exact prompt that made it: copy it, change the idea and make your own.

They're prompting experiments. Diego Balarezo's work as a Technical Animator in Unreal Engine is something else, done by hand, and it's in the portfolio.

How to write the prompt Español

Ajedrez

Full chess with the real rules: castling, en passant, promotion and draws. Against the computer, two players on one device, or online with a code.

  • Medium
  • Classic
  • Strategy
  • Online
Play Ajedrez How it was made Ajedrez

Bola 8

8-ball pool with its own physics: spin, cushions and ball in hand. Against the computer, two players on one device, or online with a code.

  • Medium
  • Physics
  • Sports
  • Online
Play Bola 8 How it was made Bola 8

Kuru

Greedy worms in a night field: eat the seeds, grow long and make the others crash into you. Solo against bots or online with up to 6.

  • Medium
  • Action
  • Arcade
  • Online
Play Kuru How it was made Kuru

Horda

Hold out against waves of shadows in a closed map. Four weapons, exploding barrels and barricades. Solo, two on one keyboard, or online.

  • Hard
  • Action
  • Co-op
  • Online
Play Horda How it was made Horda

How to write the prompt, from scratch

A small browser game can be requested in a single message. Whether it comes out playable on the first try doesn't depend on the idea: it depends on how concrete the prompt is. The prompts on this page have six parts.

  1. 1. Name and reference

    Say what it looks like and what you change. Like the bird-launching games, but with a rocket settles a hundred decisions in one line. Ask for original art: you take the mechanics from the reference, not the characters.

  2. 2. The mechanics, in verbs

    What the player does, how the game responds, how you win and how you lose. One rule per line. If a rule has a number (3 rockets, 5 levels), write it down: whatever has no number, Claude makes up.

  3. 3. The screens

    Title, game with HUD, level cleared, game over. If you don't name them, you usually get just the match, with no way to retry.

  4. 4. Keyboard and touch controls

    Ask for them separately. Touch controls are the first thing missing when you don't mention them.

  5. 5. The style, in traits you can check

    Pretty tells nobody anything. Dark space, parallax stars, red rocket, particles on impact does: every trait is something you can verify while playing.

  6. 6. The technical constraints

    A single file, no libraries or CDN, fits any screen and pauses in the background. Without this, the game may depend on files you don't have or break when you upload it to a website.

Template to copy

Replace what's in brackets. Leave the last two parts as they are: they're what makes the game work in any browser and get delivered as one file instead of in pieces.

Make me a browser game about [what it is, in one sentence], in the style of [a well-known game], but with original art.

- [what the player does and how the game responds]
- [how you win]
- [how you lose]
- [the numbers: lives, levels, time, score]
- Screens: title, the game with [what the scoreboard shows], and game over with a retry button.
- Controls: [keyboard] on desktop; [touch] on mobile.

Technical: a single HTML file with the CSS and JavaScript inside, no libraries and no external images, everything drawn on canvas. It should fill the window and be playable with a finger on a phone and with keyboard or mouse on a computer.

Give me a single, complete HTML file, nothing cut out, ready to save as index.html and open in the browser.

Paste it into Claude or ChatGPT. Save what you get back as index.html and double-click it. The detailed steps are on any game's page, under How it was made. The original prompts of each game are in Spanish, exactly as Diego wrote them.

Then: play, and ask for one change at a time

The first result is almost never the final one. Play, note what breaks and ask for one fix per message, saying what happens and what you expected. For example: if I release the rocket too close to the slingshot it shoots backward; a short drag shouldn't launch it. If you ask for several changes in one message, one ends up undoing another.