Skip to main content
OpenGame

Quickstart

Quickstart your first game

Create your first playable OpenGame project without beginning from an empty chat. Start with a reference, write a focused brief, generate once, and judge the playable output before asking for more changes.

Play a referenceOpen Studio

First build

A focused path to first play

  1. 01Play a reference1–2 min
  2. 02Write the brief2–3 min
  3. 03Generate a runqueued
  4. 04Test the artifactplayable

01 · Starting point

Choose what you already know

A reference reduces prompt ambiguity. Pick the closest interaction pattern, even when its theme is different from the game you want to make.

Play a demo

Start from a finished OpenGame build and study the controls, pace, camera, feedback, and restart loop.

Featured games

Explore an idea

Use the homepage generator when you have a rough genre or mechanic but still need help shaping the requirements.

Open generator

Start a project

Open Studio directly when the core loop, controls, goal, and output format are already decided.

Open Studio

02 · Game brief

Describe the playable behavior first

The best first prompt reads like a compact game specification. It names the experience, core loop, controls, feedback, failure state, and technical constraints.

Example game briefOpenGame
Build a short browser arcade game.

Core experience: Skill challenge with fast retries.
Core loop: Move, dodge hazards, collect score, reach the exit.
Controls: WASD or arrow keys; Space to dash.
Camera: Fixed side view.
Feedback: Clear hit flash, score change, and short sound cues.
Failure: One-hit failure with an immediate restart button.
Visual direction: Dark neon arcade, readable shapes, minimal UI.
Constraints: Desktop browser first, no external network assets.

Make the loop concrete

Define what the player repeats every few seconds. A short, testable loop gives the first build a clear center.

  • One primary action and one clear goal
  • Visible feedback for success and failure
  • A restart path that takes only one click

Constrain version one

Keep the first output small enough to judge. Extra systems make it harder to see whether the core interaction is fun.

  • Choose desktop or mobile first, not both
  • Prefer one level or a short repeatable session
  • Name non-goals such as multiplayer or persistence

03 · Generate

Run once, then inspect

Sign in before creating the run. The generator queues the build, exposes progress, and returns a playable artifact when processing completes.

  1. 01SubmitSend the focused brief from the homepage generator or a new Studio thread.
  2. 02WaitKeep the run open while its queued and processing states advance.
  3. 03PlayFocus the game canvas and test the full core loop, including failure and restart.
  4. 04RefineChange the largest visible problem first: controls, clarity, pacing, or visual direction.

04 · Delivery

Verify the artifact, then choose its destination

A generation is complete only after you can play the result. Test before downloading or publishing it.

Preview and verify

Play from start through failure and restart. Confirm input focus, readable feedback, and a stable frame rate.

  • All documented controls respond
  • The goal and failure state are understandable
  • Restart works without refreshing the page
  • No asset or network error blocks play

Choose how to ship

Keep a local artifact, publish a public OpenGame page, or return to Studio for another focused iteration.

  • Preview privately
  • Download the artifact
  • Publish a playable page

Your first run

Build one clear mechanic today

Use the prompt structure above, keep the first scope small, and let the playable result tell you what to change next.

Create a briefPlay demos