# CRAFT Recipes
New Recipes:
-
RCP-000-000-080-STAKEHOLDER-DISCOVERY-ENGINE
You describe a decision or initiative, the AI helps you identify relevant stakeholder groups, maps what you already know (and what you do not), and generates targeted Deep Research prompts to fill your knowledge gaps. The output is a self-contained Stakeholder Map you carry into the next recipe.
-
RCP-000-000-083-DISCUSSION-SYNTHESIS-STRATEGIC-ALIGNMENT
A comprehensive Strategic Alignment Report with 13 sections covering everything from executive summary through real-world action steps. The report converts simulation insights into specific conversations to have, questions to ask, and proposals to test with actual stakeholders. This is preparation, not prediction — your first real conversation will update the strategy.
-
RCP-000-000-082-STAKEHOLDER-DISCUSSION-SIMULATOR
Attach your Stakeholder Persona File and describe the topic you want to discuss. The AI confirms the persona roster and recommends a discussion format. Then the discussion runs in rounds — all personas respond, you get a moderator summary, and you direct what happens next. When you are satisfied, tell the AI to conclude and it produces a comprehensive Discussion Transcript.
-
RCP-000-000-081-STAKEHOLDER-PERSONA-BUILDER
Attach your Stakeholder Map and paste your Deep Research findings. The AI matches research to stakeholders, then builds each persona one at a time. You review, correct, and validate each persona individually before the AI moves to the next. Once all personas are confirmed, you receive a single Persona File ready for RCP-082.
-
RCP-000-000-077-COPYWRITING-FRAMEWORK-TRANSFORMER
You get two versions: a clean copy ready to publish, and an annotated copy explaining why each structural choice works — so you learn copywriting principles while getting better content.
-
RCP-000-000-076-COPYWRITING-FRAMEWORK-RESEARCHER
Instead of relying on AI opinion about which copywriting framework fits your situation, this recipe uses Deep Research to find actual evidence — case studies, A/B test results, conversion data, and expert analysis about framework performance for your specific content type, industry, audience, and goals. It produces a Framework Recommendation Report with 2–3 options, each backed by labeled evidence, honest confidence ratings, and specific trade-offs for your situation. This is Recipe 2 of 3 in the Copywriting Frameworks workflow.
-
RCP-000-000-075-COPYWRITING-CONTEXT-ANALYZER
You share written content you want to improve; the AI analyzes it for structure, persuasive elements, and quality, then builds a Voice Fingerprint capturing your writing identity — tone, vocabulary patterns, sentence style, and personality markers. Through guided questions, you define your audience, goals, and constraints. The AI compiles everything into a structured Content Brief that feeds into the Framework Researcher (RCP-076) for evidence-based framework selection or the Framework Transformer (RCP-077) for direct transformation. This is Recipe 1 of 3 in the Copywriting Frameworks workflow.
-
RCP-000-000-071-WEBSITE-QUALITY-SCORECARD
Build a section-by-section inventory of your website content with quality scores across five dimensions: Clarity, Consistency, Depth, CTA Strength,…
-
RCP-000-000-072-WEBSITE-EVIDENCE-AUDITOR
Use First Principals with Your AI Create genuinely innovative products, services, or business models by identifying core human needs and rebuilding…
What’s in the CRAFT recipe library
All current recipes, all current cookbooks, all updates to the public version. What they are, how they’re organized, and how to find the one you need.
A CRAFT recipe is a structured text file that turns a Claude Cowork prompt into a reusable, validated workflow. Recipes are versioned, named, and tested. The same recipe runs the same way in every project that uses it.
The library covers the full surface of Claude Cowork session work — starting a session, handing it off, validating output, transferring knowledge between projects, and generating content.
This page is the entry point. Browse the cookbooks below, scan the recipe anatomy, or jump straight to /craft-downloads/ to clone the public repo.
The cookbooks
Each cookbook serves a different layer of Claude Cowork work. Recipes live in exactly one cookbook — no orphans, no duplicates.
CAT-001 · CORE
CORE
Recipe-system infrastructure. Required by every CRAFT project. Session init, handoff, confidence calibration, COM monitoring, prompt intelligence, persona management.
Sample recipes CWK-001 Session Init · CWK-002 Handoff · CWK-018 Persona Manager
CAT-CWK · COWORK
COWORK
Claude Cowork session capabilities. CLAUDE.md generation, sub-agent orchestration, MPCS personas, cross-project knowledge transfer, brand kits, subproject lifecycle.
Sample recipes CWK-031 MPCS Orchestrator · CWK-026 Transfer Packager · CWK-040 Brand Kit Builder
The complete recipe index ships with the framework in plain text. Clone the repo →
Anatomy of a CRAFT recipe
Every recipe in the library is built from the same five parts. Once you can read one recipe, you can read all of them.
ID and name
Every recipe has a permanent address (CWK-031, CWK-002) and a human-readable name (MPCS Orchestrator, Handoff). The address never changes. The name describes what the recipe does.
Purpose and when to use it
One sentence on what the recipe does. A second on the conditions that should make you reach for it. If the trigger isn’t there, the recipe isn’t the right tool — the framework prefers a clean “not this one” over a forced fit.
AI specification
A machine-readable section Claude parses on every run. Inputs, outputs, validation rules, expected behavior. This is the contract that makes the same recipe run the same way in every project that calls it.
Steps, inputs, outputs
The actual work. What the recipe asks for, what it does with that input, and what it returns. Steps are sequenced and named so a session can pause at step three, hand off, and resume at step four next session without losing the thread.
Cookbook home
Every recipe belongs to exactly one cookbook. The cookbook is the folder, the recipe is the file. No duplicates across cookbooks, no orphan recipes outside any cookbook. The home is part of the recipe’s identity.
How to find what you need
Three entry points. Pick the one that matches how you’re thinking about the work right now.
By cookbook
Start here if you’re new
The cookbooks sort recipes by layer. CORE handles the recipe system itself. COWORK handles session capabilities. Pick the layer closest to your work.
By category
Once you’ve picked a cookbook
Within each cookbook, recipes group by category. CORE’s categories run from Session/Handoff to Execution. COWORK’s categories cover session lifecycle, platform bridges, MPCS, cross-project transfer, and more.
In the public repo
The canonical index
The full recipe catalog ships with the framework. Clone the repo and the framework/ directory holds every recipe in plain text — searchable, greppable, the source of truth this site links to.
A subset of recipes have full pages on this site as we build out the catalog. The complete library lives in the repo today — clone it and explore →
Why text files for recipes
A CRAFT recipe could have been a JSON config, a YAML schema, a database row, a managed-service API. It’s a text file. That choice has consequences worth saying out loud.
Text files version cleanly. Git tracks every change line by line. A recipe edit in March is reviewable in October. The framework’s evolution shows in the diff — not in a changelog someone has to remember to write.
Text files audit cleanly. Every recipe shows its inputs, its steps, its outputs in a single file. No separate dashboards, no plugin state, no telemetry pipeline. “Why did the AI do that” is answerable from the recipe and the run log together.
Text files compose cleanly. A recipe references another recipe by ID. A cookbook references its recipes by filename. A multi-recipe workflow chains recipes through normal file paths. No registry, no service mesh, no platform lock-in.
The text-file choice keeps the framework portable across model upgrades, platform changes, and project transitions. A recipe written for the current Claude Cowork build still loads when Anthropic ships the next model. The framework moves with the product.
Building with the recipe library?
Founding Chefs lock in direct creator access.
CRAFT for Claude Cowork is open during Beta through September 1, 2026. Founding Chefs get full library access, direct contact with the person building it, and 50% off the published rate for the first two years after CRAFT 1.0 ships.
Become a Founding Chef →Recipes that compound.
CRAFT for Claude Cowork is open during Beta through September 1, 2026. Clone the public repo, run a recipe, decide for yourself.
Get the framework freeOpen source · GitHub · Free during Beta