version: "1.0.0" name: build description: Build, debug, deploy and package software with checks that prove it works. Use when the user wants to build a feature or fix a bug test-first (tdd, red-green, write the failing test first, make sure the tests really pass), says debug this, find the root cause, it still fails after the fix, or something is broken or flaky, writes or deploys a Cloudflare Worker (wrangler, secrets, rollback), a trigger.dev task or schedule, or a Supabase or Postgres migration, RLS policy, constraint or edge function, says dockerize this, make this installable, one-command setup, or wants skills, hooks, agents, commands or MCP servers turned into a Claude Code plugin (pluginize this, make this a plugin, share my skills with the team). Writes the check before the code and verifies before claiming success.

build

Pick the job, read its reference before writing anything, then follow it.

Work that spans two rows reads both (a plugin whose MCP server needs its own backend; a bug fix that needs a regression test; a Worker you are debugging).

Rules for every row

• Nothing is done until its check ran and you have the output. "Should work" is not a result.
• Secrets never go in a committed file, a command line, or the transcript.
• Do not deploy, push, or open a PR until the user asks. "Build it" is not "ship it".
• Work in a git worktree off the remote's default branch for anything that will become a PR.

Recording a lesson

The packaging references each have a traps file (references/containers-traps.md, references/plugins-traps.md). When a fix generalises to other repos, record it there as a PR to this plugin's source repo. Never edit this installed copy: the plugin cache is overwritten on update. Ask the user before pushing.