THE ARCADE / SPEC-DRIVEN GAMES

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.

1game1builder0first spec projects
THE COLLECTION

Pick a game.

1 game

HOW A GAME GETS HERE

Spec first. Then play.

  1. 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.

  2. 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.

  3. 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.

ADD YOUR GAME

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.

I built a game with a spec-driven workflow and I want it listed in the Automate Your Network Arcade. Fetch https://automateyournetwork.com/arcade/ARCADE.md, copy it to ARCADE.md at the root of this repository, and fill it in from this build session: the model ID you reported, the harness you ran in, every MCP server, document, RFC and skill you used, the spec artifacts in the repo, how the game runs, and how it was verified. Do not guess. Write "unknown" for anything you did not record. Ask me only for my name, GitHub username, location, links, whether this is my first spec-driven project, and whether I consent to being listed. Run the game once to confirm the Runtime section, then commit ARCADE.md.

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.