Documentation

How Gamestage helps you take a vibe coded game into production.

  1. Introduction

    An intro to Gamestage and what it does for game developers.

  2. How it works

    How Gamestage works for game creators.

  3. Getting started

    Install the tool, point your agent at it and get going fast.

  4. The journey

    Sixteen steps from a prototype to a game a fan plays, with the command at each one and what your agent is doing while it runs.

  5. Game formats

    The seven Engine rule sets that run, and the four that are declared only.

  6. Design a game fans come back to

    What the most successful daily games have in common, as rules you can check with gamestage review.

  7. Build and deploy

    Move authority into the Engine, run the game locally and prove the result.

  8. Dataset

    The private values a round is scored against, and how to keep them current.

  9. Choose how your game sits on the screen

    Where your game runs, how it sits on the screen, and how it loads smoothly and fast.

  10. Data sources

    The sources a round can be scored on, the arrangement behind each one, and who makes the request.

  11. Live Graphics

    Put your leaderboard and a QR promo on broadcast overlays, vertical panels and stadium screens.

  12. Theming

    Read the producer's Studio colour palette so your game takes their brand with no code change.

  13. Ask fans for consent

    The consent banner every game shows, the object it stores, and how an app that embeds a game passes its own answer in.

  14. Reference

    Look these up rather than read them.

  15. Plans and limits

    What Starter includes, what it limits, and what a paid plan adds.

  16. What Gamestage is built on

    The work this product ships into a creator's project, and its licences.

Reading this as an agent

Every chapter is served as Markdown at /docs/<chapter>.md and as a JSON envelope at /docs/<chapter>.json. The agent front door is /start.md, and the site’s map for a model arriving cold is /llms.txt.