Learn the network.
Play the spec.
Every game here started as a written specification and was built with an AI coding agent. Play them, read how they were made, then build one of your own.
Pick a game.
1 game
No games match. Clear a filter or add the one you want to see.
Spec first. Then play.
Write the spec
Start from the workshop StarterKit: a constitution, a specification and a plan. The game is built from those, not the other way round.
Let the agent build it
Your coding agent builds, tests and checks the game against the spec, and keeps a record of how it did it.
Send it to the Arcade
Your agent fills in one file,
ARCADE.md. You send me your GitHub URL and the game is indexed with its card, builder and build details.
Two minutes, one file.
Your build agent knows the model, harness, MCP servers and sources it used. Paste this prompt into the same session that built the game, check what it asks you, and commit the result.
Then send your public GitHub URL to John or in the VibeOps Slack. It lists your name, optional location, the model and harness you used, whether it is your first spec-driven project, and how to play. Nothing is listed without the consent box ticked in your file.
