The engine behind the method
The Jiffi build workflow as an installable Claude Code plugin — your expert 2IC. It takes a raw idea to a shipped, well-built product and keeps you iterating on it — with real gates, not vibes.
It replaces the copy-paste setup and mega-prompts from the guides. The guides still teach the why and stay the taught path the first time through; builder-kit is the accelerator for every project after.
Install in Claude Code
Two commands, then restart your session. Run /builder-kit:setup in any project to check your machine is ready.
/plugin marketplace add jiffi-co/claude-plugins /plugin install builder-kit@jiffi-claude-plugins # then restart your Claude Code session — plugins load at session start
The whole lifecycle, each step a skill or command. Run /builder-kit:cheatsheet any time for the one-screen map.
A tiered health check (with --json) confirms your machine is ready, then a scaffold with rollback stands up a new project.
Pressure-test the idea, then build the Idea Pack, PRD, architecture, design system, ADRs and a phased implementation plan.
Work a step, verify acceptance criteria and the UI, complete the phase with learnings written back, and pass a deterministic /builder-kit:checkpoint gate — not vibes.
One-time CI setup, then ship runs the review, opens the PR, deploys, and verifies after deploy.
Run operations, keep a decision log, resume where you left off, and add a feature to a product that is already shipped.
Second opinions from agents that haven't seen your reasoning, so they catch what you'd miss.
ac-verifierreview-idea-packreview-build-plansecurity-auditorseo-specialistbuilder-kit prompts, it never decides for you. It automates the mechanical and surfaces the judgement.
The courses teach the workflow builder-kit automates. Start there, then install the plugin and go.