3D Games

The AI plans the game, gathers references, and writes it as a typed game definition that a Three.js runtime plays. It is then checked for legibility, audited, repaired, play-tested and measured for performance before it is published. The builder shows that report — the audit score, the frame budget and the playtest — next to the game.

Built on the Game Spec engine. These are the stages it runs, in order — the same list the builder shows live while it works.

1. 1PlanCode

   Reads the prompt and fixes the genre, the goal, the world size and the win condition before any inference runs.

2. 2ReferenceCode· the prompt names an existing product

   Turns a named product — "like Minecraft" — into mechanics, structure and an originality boundary.

3. 3ResearchCode· the prompt names a technology, or the feature has a known stack

   Looks up the current facts a build depends on — package versions, peer ranges, licences — from an allowlist of public sources.

4. 4KnowledgeCode· a knowledge base is configured for this deployment

   Asks the design knowledge base what it knows about a brief like this one — palette, mood, legibility, and the Three.js guidance that applies to a browser game.

5. 5VarietyCode· the workspace has built games before

   Reads what this workspace has already been given, so the next build is not a near-copy of the last.

6. 6GenerateAI call

   One forced tool call emits the complete GameSpec: world, player, entities, objectives and theme.

7. 7LegibilityCode

   Brightens a scene that would render as an unreadable black screen, in code rather than by asking again.

8. 8AuditCode

   Scores the spec for playability, genre fit, world and challenge, and lists what is wrong with it.

9. 9RepairAI call· the audit found something worth fixing

   Sends the audit's complaints back for one revision, and keeps the result only if it scores better.

10. 10PlaytestCode

    Walks the objective graph to prove the game can actually be finished, and reports how long it takes.

11. 11PerformanceCode

    Counts draw calls, triangles and shadow casters, and says which of them will cost frames.

12. 12PublishCode

    Emits the runtime and puts it at a URL that runs in any browser.

• Play it in the builder and refine it.
• Share its published link.

The report is there so you can see why an idea will not work — a goal the level cannot reach, for example — before you share a game that never ends.