A Claude Code plugin for building and tending contract-first software.

Four uses, and the first prompt for each

Each prompt is a plain sentence you type in a Claude Code session; the skill that answers it takes over from there. Every use needs Claude Code and the plugin, and each says what else to have ready: everything each use needs.

1. Start a project from the template

   A protobuf contract, a Go backend (TypeScript on request), an Expo client and a docs site, with one example resource wired through every layer from the first commit.

   You need Python 3 and git, Node 24 and pnpm 10, and Docker for the Go backend’s database and toolchain.

   In a session started in an empty folder:

   Bootstrap a new maybloom stack project called Orchard.

   • The bootstrap, in the quick start
   • Every skill in the family

2. Have agents build and review a slice

   For work bigger than one conversation: an architect session writes the brief, a builder builds it, and a fresh reviewer reviews it round by round until it is ready to merge.

   You need A forge and its client (gh for GitHub, fjo for Forgejo), a tracker and its skill, a Delegation section in AGENTS.md, and the status line.

   In a session in your project:

   Help me write a brief for this slice: <what you want built>.

   • Running a loop: every launch command and one run, card to merge

3. Decide how a screen looks before it is built

   A designer sketches directions and builds one pass on the design board, a critic judges it from screenshots, and you look last.

   You need A laptop with Chrome, and an interface scaffolded from the template, with its design board.

   In a session in that project:

   Run the design loop for the notes list screen.

   • The design loop: launch commands and the capture script

4. Watch your usage and session budget

   Two lines under the prompt: the 5-hour and weekly windows with their resets, context against your session budget, and the prompt cache countdown.

   You need jq, curl and git, a claude.ai sign-in for the usage numbers, and Claude Code 2.1.251 or later for the cache countdown.

   In any session:

   Install the status line.

   It draws this under the prompt:

   ~/workspace/app | [main] | Fable 5.1
   5h:31% (2h00m) | weekly:55% (2d07h33m) | fable:53% (4d08h39m) | ctx:12% | cache:4m50s

   • The status line: each segment, the install, the checks