Skip to content

Create with OpenGame

The tools, the setup and the prompts we use to go from an idea to a game people come back to.

Browse concept art

Copies a brief for your agent and the open guide, to paste into Claude Code or Codex.

  1. Step 1: Set up OpenGame

    npm i -g @opengamehq/cliopengame setup

    Installs the opengame command and gives your agent the OpenGame skills, which stay current as the CLI updates. Needs Node 18.17 or newer on macOS, Linux or Windows.

  2. Step 2: Give your agent this

    Build a new browser game with me and put it on OpenGame.1. Install the CLI with npm i -g @opengamehq/cli if it is missing or out of date, then run opengame setup.2. Use the OpenGame skills that setup installs, starting with opengame-router, and read https://docs.opengame.io/llms.txt for the guides.3. Sign in only with my approval.4. Ask what game I want, then build it with me in its own folder, starting with opengame init. Run opengame dev so I can play as we go.5. When I say it is ready, run opengame check --build and opengame deploy, with --publish if I ask you to publish it, and fix confirmed game findings.6. Give me the deployment page link and the private preview link.Review starts by itself and writes the details. I check them and publish there, unless I asked you to.

    Works in Claude Code, Codex, Cursor and OpenCode.

01  What you need

Your ideas and a coding agent.

  • 01

    A coding agent

    All you need to make a great game is your creativity and a coding agent like Claude Code or Codex.

  • 02

    A plan

    Coding agents cost $20 a month. Many creators choose the $100 or $200 plans, or Codex’s $500 plan, which give more use in total and for each dollar.

  • 03

    Questions

    If you’re unsure about anything, ask Claude or Codex. It can explain almost anything, and do most of it for you.

  • 04

    Free tools

    Blender is free, and makes, rigs and animates 3D models. Your agent can run it for you.

02  Models

Pick the model with care.

The model you use and how hard it thinks can change your game more than any other choice.

Claude

Best for games

Use Fable or Opus. Sonnet is a good backup. Skip Haiku for games.

OpenAI

A close second

Use Astra or Sol. We wouldn’t use the others.

Gemini, Grok and Kimi

Other options

Use the newest model in the family, or the one just below it. In our experience these make weaker games than Claude and OpenAI.

Reasoning

Set reasoning to High, or Medium. Going above High spends far more tokens, costs much more, and in our experience makes worse games.

03  Engines

three.js to start.

three.js

For beginners

3D in the browser with no install and no export step. Coding agents write it well, because there is more of it to learn from than any other engine.

Unity, Godot and Unreal

For experienced developers

Full editors with a web export. Unity is the industry’s most used engine; Godot is free and open source; Unreal Engine 5.9 adds an experimental WebGPU export.

Kaigen

Something in between

A new engine, open to everyone and free for web games like the ones in our jam. OG Clash is made with it.

04  Art and sound

Generative models are optional. Sound comes first.

Your agent can make a game in code alone. Generative models give you higher quality art, which is what our jams are for.

ElevenLabs

Sound effects, voices and music

Sound matters most. Procedural sound is made in code while the game runs. It’s free and instant, and often sounds thin. Generated sound is made once by a model and saved into your game, and it sounds real.

Meshy

3D models

Characters, creatures and props from a picture, rigged and animated. Best paired with Blender for cleanup.

fal

Images and video

Hundreds of generative models behind one key: 3D models, sound effects, music, concept art and concept videos.

05  Making it good

Good games take rounds, and time.

Play, tell it, repeat

Good games come from feedback loops. You play a version, tell your agent what to change, and repeat. Time helps models the way it helps people.

A playable loop first

Don’t try to make the whole game in one prompt. Get something playable, then improve it round by round.

Feel before looks

How it plays and how smoothly it runs matter more than how the first build looks. Measure the frame rate and give it a budget.

A game people return to

Aim for a game you and other people want to play again.

Hours, not minutes

Expect your agent to spend at least 4 to 8 hours improving the game, and the best games often get 10 to 20 or more. That isn’t hours of prompting. After each message the agent works on its own for a long while.

06  Starter resources

Start from what others made.

OpenGame skills

What we learned making our games, written for your agent to read. They teach Claude Code, Codex, Cursor or OpenCode how to build a game that plays well, check it and deploy it to OpenGame. Run the command below in your game’s folder.

npx skills add opengamehq/opengame
Download skills
opengame-all-in-one

Every OpenGame skill in one install, with the order to use them in, for taking a browser game from an idea to a AAA-feeling release, a trailer and a montage.

Start here

All in one

opengame-all-in-one

Every OpenGame skill in one install, with the order to use them in, for taking a browser game from an idea to a AAA-feeling release, a trailer and a montage.

Carries all 36 skills, so your agent knows which to use and when.

Sample workflows

Their work, shown with their credit. Each step list is our short version of the post.

  • Video to game

    Video by @OdinLovis on X

    H3 Max on fal, Claude, three.js

    1. A video model on fal makes a short gameplay video of the game first.
    2. Claude turns that video into a game you can play in the browser, in three.js.
    3. Every image, 3D model and sound is generated on fal.

    An agent alone designs safe games. A video gives it something original to aim at.

  • An original game in 24 hours

    Video by @xikhar on X

    Opus 5.5, Flux 3 Max, GPT Image, Tripo, Blender, three.js

    1. Generate a gameplay video with Flux 3 Max on fal. It sets the look, the world and the character.
    2. Screenshot it, rebuild the assets in Blender and place them in three.js.
    3. For the character, make four side views with GPT Image, turn them into a model in Tripo, and let the agent add cloth and animation.
    4. Play the prototype and check it works before building more.
    5. Make concept art for each level in the same style, then build each one and keep playing and fixing.
  • A platformer that runs on a phone

    Video by @sorenxet on X

    GPT Image 2.5, Tripo, Blender, Opus 5.5, ElevenLabs

    1. Mood boards first: the storm, the piers, the wrecks and one glowing boss.
    2. Tripo turns them into 3D; Blender fixes scale and pivots and cuts polygons so a phone holds 60 frames a second.
    3. The hero stays a 2D sprite inside the 3D world.
    4. Opus writes the game: movement, jumps, camera, rain and water.
    5. The boss has one rule a player can read. Its light shows where the fist will land.
    6. Sound effects and music from ElevenLabs, at the very end.

    Make it exist first. Make it good after.

  • A Zelda-like in two days

    Video by @sorenxet on X

    Opus 5.5, Tripo, Blender, Unity

    1. Write the game on one page, and start every prompt from it.
    2. Draw four views of each character, A-pose, empty hands, white background.
    3. Make each model in Tripo from three or four views, so it doesn’t invent the back.
    4. Opus writes Blender scripts that shrink the models, rig them and animate the boss.
    5. Build the village in code with free props from Poly Haven.
    6. One brief per system, each in a fresh session. Play it, list what’s off, and that list is the next brief.

    31 sessions and about $88, because rigs, animation and the village are code.

  • An open-world RPG with no coding background

    Video by @M__Houser on X

    Fable 5.2, Opus 5.5, three.js, Tripo, Blender, ElevenLabs

    1. Paint every landmark as concept art first, then build it as a place you can walk to.
    2. Make every character, creature and prop in Tripo.
    3. Have Claude rig them all in Blender on one shared skeleton.
    4. Make the voices, effects and music with ElevenLabs.
    5. Run a critic loop: 25 rounds of screenshots, each judged and fixed.

    A 12 by 12 km world, made by someone who had never written code.

  • A Souls-like in three days

    Video by @MengTo on X

    Fable 5.2, Opus 5.5, Claude Code, Seedream 5.0 Pro, Tripo, three.js

    1. Make a level and a boss playable before anything else. Fable 5.2 took 6 hours and 12 prompts.
    2. Fable gives lighting, effects, characters, UI and sound each to its own Opus thread, up to 9 at once.
    3. Seedream draws each character in an A-pose on grey, Tripo makes the model, and the agent writes the rig and animations in code.
    4. Seedream repaints a screenshot of the game with the same camera and pose, and the agents chase that picture.

    Judge every change blind, before against after from the same camera, and keep only what wins.

More skills

Terminology

The overview as one Markdown file, for any agent or your notes.

07  Upload it

Made a game? Give your agent one prompt.

Your agent does the uploading. You copy a prompt, paste it in, and say yes when it asks.

  1. 01Copy your promptPress Get your prompt to open the prompt for your agent. If your account can’t enter yet, that page says why.
  2. 02Paste it into your agentYour coding agent (Claude Code, Codex, Cursor or OpenCode) exports your game, checks it and uploads a private preview for you to play. You don’t run any commands.
  3. 03Approve when it asksIt asks before it signs you in. Review starts by itself and writes the details, and when it passes you check them and enter the jam on the deploy’s page.

An automated review playtests your entry before it is public. Judges score it whether it is public yet or not.

Then bring it to the jam.

A month to make a game. Anybody can play it for free on OpenGame.