Builders & Runtimes
Game Builder
Game workspaces, engine previews, and generated browser games.
Game Builder
The game builder turns prompts and edits into playable browser games. It shares the same product philosophy as the app builder: generated work should be inspectable, editable, and testable from the browser.
Main Routes
| Route | Purpose |
|---|---|
/game-engine | Game builder landing/workspace selection. |
/game-engine/[gameId] | Opens a game workspace. |
/game-engine/[gameId]/[[...path]] | Runtime route for nested game preview paths. |
APIs
| Endpoint | Purpose |
|---|---|
/api/game-builder/projects | List and create game builder projects. |
/api/game-builder/projects/[gameId] | Load, update, and manage a single game. |
/api/game-engine/workspaces | Runtime workspace orchestration. |
/api/game-engine/workspaces/[workspaceId] | Workspace state, files, preview metadata, and updates. |
Expected Features
- prompt-to-game generation;
- editable game files;
- preview runtime;
- game assets generated through media providers;
- saveable workspace state;
- export or publish path;
- project-specific history.
Quality Bar
Games should open directly into gameplay or an editor with an active preview. Avoid empty landing pages. Check that keyboard controls, mobile layout, audio toggles, and game state reset work before treating a generated game as complete.