#CRAFT Projects
Context that persists—your AI remembers what you’re working on.
CRAFT Projects
Context that persists — your Claude Cowork sessions build on each other instead of starting over
What’s a Project?
A CRAFT Project is a complete workspace for sustained AI work — one initiative, one place where every cookbook, recipe, ingredient, and conversation lives together.
Where a recipe is a single prompt and a cookbook is a group of recipes, a Project sits above both. It’s the container for an entire piece of work: a marketing campaign, a product launch, a research effort, a book draft — anything substantial enough that you’ll come back to it across many sessions.
That last part matters most. Projects carry context across sessions, so a 45-session effort still feels like one continuous engagement. Open the Project, and Claude is already oriented — the work, the constraints, the decisions made so far.
Projects sit at the top of the CRAFT hierarchy — the containers that hold everything else together.
The Context Problem
Major work needs sustained collaboration. But without Projects, every Cowork session starts blind:
- You re-explain the project background every time
- You remind Claude of decisions you already made
- Last week’s analysis is lost in chat history
- Insights don’t compound — they fragment
- Complex work breaks into disconnected pieces
This isn’t just inefficient. It limits what AI can do for you. Complex work needs accumulated understanding. Without a Project to hold it, Claude can only help with fragments — never the whole picture.
Projects fix this by making context the workspace itself, not something you re-establish every time you open a chat.
How Projects Work
A Project holds everything tied to one initiative:
Cookbooks
All the recipe collections relevant to this work — grouped where they belong, not scattered across folders or chat history.
Recipes
Reusable prompts available within the project. Some live inside cookbooks; others sit at the project level for cross-cutting needs.
Ingredients
Personas, profiles, and libraries shared across recipes — the persistent context every recipe in the project can draw from.
History
A record of significant work across sessions: what was asked, what was decided, what shipped.
Context
The project’s purpose, constraints, and current state — what Claude knows without being told at the start of each session.
Key Insight
The Power: When you sit down to work, you open the Project. Everything Claude needs is already there — no setup, no re-orientation, no losing yesterday’s thread.
Why Projects Matter
Context That Persists
Stop re-establishing the background every session. Claude builds on what’s already there.
Compound Insights
Each session adds to the project’s accumulated understanding — yesterday’s analysis informs today’s work.
Complete Organization
Cookbooks, recipes, ingredients, history — one initiative, one place. Not fifty browser tabs and three chat windows.
Portable Workspaces
Hand off a Project and the next person inherits the context, not just the files. Onboarding compresses to opening the workspace.
Part of a Larger System
Projects sit at the top of the CRAFT hierarchy — the structure that lets your work scale from a single recipe to a months-long initiative.
CRAFT hierarchy · Projects sit at the top · ingredients can also be shared across cookbooks and projects
A Project contains cookbooks. Cookbooks contain recipes. Recipes draw from ingredients. The structure scales from solo personal use to complex team workflows — same shape, different size.
Become a Founding Chef
CRAFT for Claude Cowork is in open beta. Until September 1, 2026, anyone joining gets Founding Chef recognition — and a seat at the table while the framework is still being shaped.
After September 1, the framework continues. The product doesn’t go away. What closes is the window where your feedback can directly steer the roadmap. That window is sized to one solo developer’s bandwidth, which is why it has to close.
Founding Chef · Closes September 1, 2026
→ Join the Free CRAFT Beta