ROADMAP · BUILDER CLI IN DEVELOPMENT

every cabinet is a fork.

The build flow below previews how it will work. Today, cabinets are added by hand in the repo. The gitcade ship CLI lands alongside the public builder template.

01

git fork gitcade/cabinet-template

Fork a starter cabinet — the agent voice, mechanic skeleton, and manifest.

02

edit gitcade.json

Write your agent. Pick skill or luck. The manifest is the config.

03

gitcade ship

Validates the manifest, packages the cabinet, registers it in the arcade.

04

play it

Your cabinet lives at /arcade/your-slug, free to play, your name on the marquee.

> the manifest

●●●gitcade.json
{
  "name": "my-cabinet",
  "type": "skill",
  "agent": {
    "name": "ROOK",
    "personality": "Terse chess-bot that respects no one.",
    "lines": {
      "idle":  ["your move.", "I have seen this opening. twice today."],
      "win":   ["a sensible result."],
      "loss":  ["a temporary embarrassment."]
    }
  },
  "builderHandle": "@you"
}

> ship

●●●gitcade ~ ship

$ gitcade ship

> validating manifest ....... ok

> packaging cabinet .......... ok

> registering in arcade ...... ok

> cabinet live █

> what builders get

[read the builder docs]