#CRAFT Framework

Structure without complexity—organized AI workflows for everyone.

What CRAFT for Claude Cowork is

CRAFT for Claude Cowork is the opinionated governance and methodology layer that turns Claude Cowork’s raw capabilities into reliable, auditable, repeatable workflows.

It is not software. It is not a SaaS platform. It is not a plugin. CRAFT for Cowork is a file-based framework — structured Markdown files in a public GitHub repository you clone to your own machine, sitting alongside your Claude Cowork projects and applying production-systems discipline to AI work.

Clone the repo, point Cowork at it, and Claude starts behaving like a team member who reads the playbook before acting.

The promise underneath all of it is simple: Claude work that compounds. Yesterday’s session sets up today’s. Today’s recipe runs the same way next month. The work you do in one project becomes a first-class asset in the next.


The three pillars

CRAFT for Cowork organizes around three properties that are missing from raw Claude Cowork — and that production systems take for granted.

Repeatable

Today’s session runs like yesterday’s.

Recipes replace remembered prompts. Session init replaces the 20-minute re-grounding tax. Handoff replaces “where were we?” The same workflow runs the same way without re-typing setup.

Portable

What works in Project A works in Project B.

A recipe built in one project is a first-class asset in the next. Cross-project knowledge transfer moves lessons and patterns, not just files. New projects inherit institutional memory automatically.

Auditable

Every output traces back.

Logged recipe runs, versioned cookbooks, confidence gates on recommendations, write-only backups. “Why did we do it this way” is always answerable — from the file, not from memory.

See it in practice

Each pillar shows up in the recipe library as a different kind of file. Browse the recipe library →


The CRAFT hierarchy

CRAFT for Cowork is built from four layers. Each layer has a single job. Together they turn ad-hoc Claude Cowork sessions into structured project work that survives the gap between Tuesday and Thursday.

Recipes

The fundamental unit

A reusable AI prompt with structured inputs and a defined output shape. Write once, validate, then run the same way every time — like a function for your AI conversations.

Learn more about CRAFT Recipes →

Cookbooks

Recipes, organized

Collections of related recipes grouped around a common purpose. A marketing cookbook, a research cookbook, a client cookbook — structure that matches how the work actually clusters.

Learn more about CRAFT Cookbooks →

Projects

Context that persists

Complete workspaces that hold cookbooks, history, and the resources tied to one initiative. Projects carry context across sessions so a 45-session effort still feels like one continuous engagement.

Learn more about CRAFT Projects →

Ingredients

Reusable components

Building blocks that recipes draw from. Personas define how Claude behaves. Profiles store consistent context. Libraries provide reference data the AI can rely on across runs.

Learn more about CRAFT Ingredients →
Going deeper

The Ingredients layer includes two surfaces worth their own pages: CRAFT A.I. Personas for structured AI behavior, and Multi-Recipe Workflows for chaining recipes into pipelines.


What CRAFT actually does

The framework ships as a working set of capabilities — not a marketing taxonomy. Six of the most-used surfaces:

Recipe System

Validated workflow templates

Reusable templates for the work you do in Claude Cowork. Each recipe is structured, validated, and tested before it ships to the public version of the framework.

Session Handoff

State that survives the gap

Structured text files preserve session decisions, priorities, and context. The next session picks up exactly where the last one ended — no re-explaining the project.

Lessons Learned

Operational intelligence, captured

Per-session lessons accumulate in a project file. Mistakes get caught once and not repeated. The project gets smarter the longer it runs.

CLAUDE.md auto-loading

Init in minutes, not 20

Claude Cowork reads the project’s CLAUDE.md automatically at session start. Persona, communication preferences, project context, and standing instructions load before the first message.

Persona System (MPCS)

Consistent voice across sessions

Structured AI communication preferences with expertise tiers. The persona that worked yesterday behaves the same way today — and across every session of the project.

QA Framework

Production-grade output

Validation recipes, fact-checking, integrity checks, sub-agent review patterns. The discipline that makes incident-response playbooks work, applied to AI output.

Want the complete list?

The full capability set ships in the public repo — clone it and explore →

Ready to build? Get the framework free.

CRAFT for Claude Cowork is open during Beta through September 1, 2026. Clone the repo, run a recipe, decide for yourself.

Start My Beta

How CRAFT is different

Methodology, not software

Most things sold around AI are software — a SaaS dashboard, a Chrome extension, a managed service that sits between you and the model. CRAFT for Claude Cowork is none of those.

It is text files. The recipes are text files. The cookbooks are folders of text files. The project state lives in text files. The persona system is text files. There is nothing to install beyond git clone, nothing to subscribe to, and nothing that breaks when Anthropic ships a new model next month.

That choice is deliberate. CRAFT for Cowork is built by a senior cybersecurity incident responder, not an AI thought leader. Production-systems thinking — structured playbooks, discipline under pressure, multi-role validation, audit-first reflex — is precisely what AI workflows have been missing. The framework applies that discipline to Claude Cowork specifically because Cowork is where the multi-session knowledge work happens.

The honest test: if Anthropic shipped a feature next month that did one of these things natively, would the rest of CRAFT still be useful? Yes — because the value is the methodology and the file structure, not the specific capability. The framework moves with the product.

Curious about the details?

The methodology, the cookbook structure, and the recipe format are all documented in the public repo. Get CRAFT free from Github→


Stop rebuilding prompts from scratch.

CRAFT for Claude Cowork gives you every recipe, every cookbook, and every update to the public version of the framework. Free during Beta through September 1, 2026.

Founding Chef · Closes September 1, 2026

→ Start My Free Beta

CRAFT for Claude Cowork is not a course, not a newsletter, not a gated demo, and not a private community. It is a working framework you clone, run, and build with. The repo is public. The docs are public. You evaluate on your own terms.


Did this page land?

Did we nail it? Tell us in one sentence whether this page made CRAFT click for you — and if it didn’t, what tripped you up. Quick feedback below goes straight to Richard’s inbox.

CRAFT Framework Clarity Check

Your responses are stored securely on CRAFTFramework.ai. We don't share your data with third parties. Anonymous submissions are welcome.

No account required. Three quick questions, plain answers, no follow-up unless you ask for one.

Claude work that compounds.

CRAFT for Claude Cowork takes Claude Cowork from a single-session tool to a multi-session project platform. Founding Chefs lock in their access — and their roadmap influence — before September 1, 2026.

Become a Founding Chef

Open source · GitHub · Free during Beta