Documentation
How Gamestage helps you take a vibe coded game into production.
- Introduction
An intro to Gamestage and what it does for game developers.
- Set up Gamestage
Add Gamestage to Claude, Claude Code, Codex, Cursor or a terminal, and what an account is for.
- How it works
How Gamestage works for game creators.
- Getting started
Make a small game, play it against the real Engine, then bring your own.
- The journey
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.
- Game formats
Engines that your game will run on.
- Design a game fans come back to
What the most successful daily games have in common - checkable with gamestage review.
- Build and deploy
Move authority into the Engine
- Choose how your game sits on the screen
Where your game is embedded, how it fits on the screen
- Dataset
The private values a round is scored against, and how to keep them current.
- Data sources
The sources a round can be scored on, the arrangement behind each one and how requests are made
- Live data
Put a real contest into your game as it happens, in any sport: the score, the clock, each side's numbers and every moment.
- Theming
Read the producer's colour palette and other settings so your game takes their brand with no code changes.
- Draft a theme from Figma
Give Gamestage your brand's Figma file, get a draft theme on real Gamestage UI components, revise it in plain words, and publish it when it is right.
- Your organisation's context, starter apps and themes
One private file that tells every agent in your organisation how a game fits your app, starter apps every new game begins from, and themes that give your games your brand's look.
- Live Graphics
Put your leaderboard and a QR promo on broadcast overlays, vertical panels and stadium screens.
- 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.
- Host files on cdn.gamestage.ai
Publish App Spec documents and brand files that Studio and clients fetch by URL, at an address that never changes.
Reference
Look these up rather than read them.
- App Manifest reference
The sections, statuses, provenance and server-owned container.
- Player API reference
Read public state, send intent and render the Engine's committed result.
- CLI reference
Every command, its options, and what each exit code means.
- Schemas and endpoints
The public URLs that answer, and what each one serves.
- Gamestage UI
Components for the interface a live game wears: choices, score, timer, rewards and the leaderboard.
- Third-party tools and assets
Open-source tools and asset packs that suit a sports fan game, their licences, and when to reach for one.
- App Manifest reference
- Use your own domain
Serve a game from an address of your own, such as quiz.myclub.com, with one DNS record.
- Ads
Partner products on the result card after a win. In preview: switched on per game by Monterosa, subject to approval and commercial terms.
- Plans and limits
What Starter plan includes, what it limits, and what a paid plan adds.
- 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.