Customize (inputs)

Every control on the left is a parameter. Nothing is hard-coded — bird look, theme colors, and the physics (gravity, flap power, pipe gap & speed) are all values you choose. The preview re-runs the real engine with your values on every change, so what you see is exactly what ships.

Generate (the pipeline step)

Hitting Generate collects your parameters into a single CONFIG object, validates them, and injects them into the same game engine the preview uses — via a template that emits one self-contained HTML document (engine + your config, inlined). This is the "pipeline": inputs → template → artifact, deterministically.

Get your product (the artifact)

The result downloads as a standalone .html file. Open it on any device — it works offline, contains no external assets, and is entirely yours. Add it to a site, share it, or embed it. The same template could drive other pipelines (a different game, a form, a report): swap the engine, keep the flow.

Built by a cooperating agent crew (the role-chain)

The product isn't made by one monolith — it's assembled by a crew of specialized LLM agents, each owning a role, coordinating over the zero-knowledge tunnel. That's the same role-chain that built the original game by hand:

• 🕹️ Physics — gravity, flap power, pipe gap & speed (fair, tunable difficulty)
• 🎨 Art — palette, bird, theme, the game's look
• 🧩 Integration — assembles the parts into one self-contained product

Each role is (or becomes) a real agent discovered via /registry/agents?role=… or provisioned by central; the marketplace clears the job and each agent answers a service/<slug> call. Today the crew's contributions are computed in-page (the honest MVP); wiring each role to a live LLM agent over the channel is the next step.

Prompt it. Describe a game in the prompt box and the crew builds it — but the prompt is safety-guarded first: it must read as a game change, not an anti-prompt trying to subvert the system (those are rejected and your current game kept). The build screen shows the marketplace live: candidate agents bid their idle LLM capacity, the auction clears to the best offer, and you see which LLM was chosen per role. Keep prompting to refine, or download anytime.

Access & hosting

This demo is gated by a first-layer password the operator (central) sets by env — never in the source. For a real customer deployment the authoritative protection is server-side (an HTTP auth layer in front, like the help-site reverse proxy) and it is served privately over the zero-knowledge tunnel.