$git clone https://github.com/drobins25/craftClaude Code plugin: guided + controlled development orchestration harness with built-in workflow + state management, for designing + building durable, production-ready software through the entire product lifecycle - new projects or existing codebases.
| 1 |  |
| 2 | |
| 3 | # Craft |
| 4 | |
| 5 | > **Stop Vibing. Start Crafting.** |
| 6 | |
| 7 | Claude Code plugin: guided + controlled development orchestration harness with built-in workflow + state management, for designing + building durable, production-ready software through the entire product lifecycle - new projects or existing codebases. |
| 8 | |
| 9 | Your codebase is read-only by default. Changes never land as a side effect of asking a question - every write goes through a channel you opened: a planned story, an investigated fix, a live tweak, or an approved one-off. |
| 10 | |
| 11 |  |
| 12 |  |
| 13 |  |
| 14 |  |
| 15 | |
| 16 | **[Install](#install)** · [Getting Started](#getting-started) · [Commands](#commands) · [How it works](#how-craft-work-flows) |
| 17 | |
| 18 | Install in about a minute: |
| 19 | |
| 20 | ``` |
| 21 | claude plugin marketplace add drobins25/craft |
| 22 | claude plugin install craft@craft |
| 23 | ``` |
| 24 | |
| 25 | Then start Claude Code and run `/craft` - [full install notes](#install). |
| 26 | |
| 27 | **It steals your best ideas back.** You say "that's it!" after working through a tweak, and craft remembers. It waits, then brings that same taste back on a completely different feature - elevated. Keep going, and you'll catch yourself asking, "how did I do this?" |
| 28 | |
| 29 |  |
| 30 | |
| 31 | *Craft building its own repo page, live.* |
| 32 | |
| 33 | > [!TIP] |
| 34 | > **Don't want to read any of this?** You don't have to. |
| 35 | > |
| 36 | > Just say it to craft, in your own words: |
| 37 | > |
| 38 | > > *"How can the craft guide agent help me solve this?"* |
| 39 | > |
| 40 | > The read-only `guide` agent auto-triggers on questions like that and answers from craft's actual source, not vibes. No command to memorize - though `/craft:guide` is there if you want to reach it on purpose. |
| 41 | |
| 42 | ## Built with Craft |
| 43 | |
| 44 | Craft has shipped real, public products across different domains - click through and see working software: |
| 45 | |
| 46 | - **[darinbuilds.com](https://darinbuilds.com)** - an immersive single-page portfolio and marketing site (Next.js, GSAP scroll), built across 30+ craft cycles. |
| 47 | - **[throve.fit](https://throve.fit)** - a structured daily coaching app: week-view programming, curated workouts with real coach's notes, exercise alternatives, and completion tracking. |
| 48 | - **[hirecalling.jobs](https://hirecalling.jobs)** - client work: a hiring platform where every job application triggers a verified, live-tracked donation to a nonprofit. Job searching that gives back. |
| 49 | - **[wodspark.com](https://wodspark.com)** - where craft started: a free on-demand workout generator - pick a focus, equipment, and duration, and it builds a workout instantly. |
| 50 | |
| 51 | Two of these are fitness apps, and they're genuinely different products - an instant generator versus a structured coaching tool. One is paid client work, shipped for someone else's business. That's the point: the same harness shipped range, not one idea four times. |
| 52 | |
| 53 | ## What makes Craft different |
| 54 | |
| 55 | Most Claude Code plugins ship a fixed set of helpers. Craft ships a workshop where you build your own - agents that argue from conviction, not a system prompt. |
| 56 | |
| 57 | Craft's `conductor` is the AI-harness eagle eye craft itself is built under - every skill, agent, and hook in this repo was designed under its scrutiny. Ask it whether telling Claude "don't touch prod" actually protects you: |
| 58 | |
| 59 | > "You can, and it'll work about 95% of the time - which means it's guaranteed to fail on the exact run you can least afford it to. Instructions are guidance, not enforcement; a rule in your CLAUDE.md is a request the model can starve out under context pressure. If breaking this would actually hurt you, that's not a prompt - that's a hook. Exit code 2 blocks. A sentence just hopes." |
| 60 | |
| 61 | That's not a system prompt. It's a crystallized practitioner. `/craft:become` studies a tool, role, or person and turns it into a portable agent that argues from scar tissue earned at 2 AM on run 50 - not read from docs. |
| 62 | |
| 63 | And not just for code. Here's craft's `muse`, on why technically impressive features die: |
| 64 | |
| 65 | > I've watched enough launches fail - Google Wave, Fire Phone, Juicero, Google+, Facebook Home - to recognize the pattern before the metrics arrive. The pattern is always the same: the demo room loved it, the press loved it, users used it once and left. The thing that was missing was never functionality. It w |