CRAFT Tutorials · Getting Started · 7 of 12
You don’t install recipes one at a time. The complete everyday set already lives inside your CRAFT for Claude Cowork — ready the moment you open the folder. Here’s what’s in the box, and how to reach for any of it.
In the last post you ran a recipe by naming what you wanted. Now the natural questions: what else can I ask for, and how do I find it? The short answer is that you already have everything, and you look it up rather than memorize it.
What comes in the box
Your CRAFT for Claude Cowork ships with the full user-tier recipe set already inside it — nothing to download recipe-by-recipe. It comes in two families:
The engine
The machinery that makes CRAFT run — session memory, handoffs, and the recipe system itself. You rarely call these by name; they’re what makes everything else work.
The everyday tools
The ones you’ll actually ask for: saving handoffs, backing up files, starting subprojects, using personas, validating claims, planning work, and more.
All told it’s 87 recipes (17 CORE + 70 COWORK) — but please don’t memorize that. You’ll never need the number, or most of the names. The few you use often become second nature; the rest simply wait until you need them.
One small distinction. These recipes come with CRAFT — the kit you added to your project — not with Cowork by itself. Cowork is the app; CRAFT is what’s inside the folder. That’s why everything works the instant you open a CRAFT project.
How to use any of them
The same way you ran your first one: say what you want, in plain language. You can name the recipe or just describe the outcome — both work.
- “Save a handoff.” — names the recipe directly.
- “I’m done for today.” — describes the moment; Claude offers to save a handoff.
- “Back up this file before we change it.” — a plain request, matched to the backup recipe.
If your wording is close, Claude picks the right recipe. If it’s unsure, it asks first — so you can’t really get it wrong.
You don’t memorize them — you look them up
So what’s the honest answer to “which recipes do I have?” It’s: open the cheatsheet and see. Every included recipe is listed there with the plain words that trigger it — so the cheatsheet is both your menu and your reminder. (We’ll look at it properly in What is a cheatsheet? later in this series.)
And if you’d rather just ask, you can — anytime:
✓ The takeaway: you already have the whole set, you never need to memorize it, and you can always find the right recipe by checking the cheatsheet or simply asking. You can’t lock yourself out.
You stay in control
Recipes that change files tell you what they’re about to do and, where it matters, ask before doing it. Nothing happens to your files by surprise — so it’s safe to explore and try things.
That’s the whole recipe picture: the full set ships inside your kit, you ask for any of it in plain language, and you look up the rest when you want it. Next up: Start a subproject — how to give a bigger piece of work its own focused space.