Docs
One manual, straight from the repo
Everything here renders from the same markdown your agent reads in the monorepo — the site can't drift from the docs, because it is the docs.
Sandboxes
Twelve single-mechanic labs — physics, particles, lighting, synth — one primitive each, with knobs.
ExploreThemes
Complete looks for your game. Regalia ships today; the contract is built for more.
ExploreDesign Codex
216 design modules — anchors, genres, systems, mechanics — the library your agent composes games from.
ExploreStart here
QuickstartInstall from npm, define a game, prove it correct headlessly — a complete runnable example.Errors & gotchasThe common newcomer mistakes and what each [hayao] guard message means.ConventionsHow games are structured, the house style, and the definition of done.API digestThe full public surface — every export and signature, greppable in one page.
The engine
ArchitectureThe authoritative design and the determinism contract.Engine internalsWhy a custom engine, the simulation kernel in depth — and when not to use one.VerificationThe proof harness: solvers, bots, golden replays, and the two verification channels.NetworkingDeterministic multiplayer — lockstep and rollback over a pluggable transport.EmbeddingShip a game as one self-contained HTML file — Artifacts, itch.io, CodePen.
Art & sound
The instruments
The build record
Build logThe Build-Measure-Learn campaign, game by game.LessonsTransferable lessons from real LLM-authored game builds.Friction logWhat fought an AI session, and the check or doc that now prevents it.ArchiveThe corpus-v0 prototype set — 33 games, archived, recoverable by git tag.Triage — July 2026The recreation-friction triage that shaped 0.4.0.
Working with an agent? Point it atAGENTS.md— the operating manual an AI author reads first.