# CRAFT Recipe Ingredients

Define once, use everywhere—personas, profiles, and libraries.

Define once, use everywhere — personas, profiles, and libraries that travel with your Claude Cowork projects

In Claude Cowork, every kitchen has pantry staples — olive oil, salt, garlic — that appear across many recipes. You don’t buy new salt for each dish.

CRAFT Ingredients work the same way: reusable components that keep consistency across all your Cowork projects. Define your brand voice once. Drop your client’s preferences in once. Pin the reference data once. Then any recipe in any project can reach for it — without you re-typing the setup or hoping you remembered every constraint.

In production-systems terms, Ingredients are the dependency layer. Without them, every recipe has to re-establish context from scratch — and re-establishing context is exactly where prompt drift sneaks in. Define once. Audit once. Reuse everywhere.

Ingredients are the consistency layer that makes CRAFT for Claude Cowork production-grade.

A.I. Personas

Who the AI becomes when running your recipe.

A persona defines the AI’s expertise, communication style, and approach. Instead of writing “Act as an experienced marketing strategist who communicates clearly and focuses on ROI…” in every prompt, you create that persona once and reference it by name.

Examples

  • Strategic Marketing Advisor — business-focused, ROI-oriented
  • Technical Documentation Writer — precise, comprehensive, structured
  • Creative Brainstorm Partner — playful, divergent, idea-generating

Personal and Brand Profiles

Consistent context that recipes need to know.

Profiles store information that multiple recipes reference: brand voice guidelines, client preferences, project context, company information. Define once, access from any recipe.

Examples

  • Acme Corp Brand Profile — voice, values, terminology, style guide
  • Q4 Campaign Context — goals, audience, key messages, constraints
  • My Writing Style — personal preferences for tone and format

Prompt Library

Reference materials recipes can draw from.

Libraries contain data, examples, templates, or documentation that recipes might need. Instead of pasting reference material into each prompt, point to the library.

Examples

  • Product Feature Database — specifications, benefits, use cases
  • Email Template Examples — proven formats for different situations
  • Industry Terminology — definitions and proper usage

How CRAFT Works

Create a Recipe

Turn any successful prompt into a reusable recipe. Add variables for the parts that change. Version it the first time it ships work that holds up under review.

Organize Into Cookbooks

Group related recipes together. Marketing cookbook. Research cookbook. Client cookbook. Your structure, your system — not someone else’s taxonomy.

Run in Claude Cowork

Recipes execute as portable scaffolding inside Cowork projects, with handoff state and audit trail intact. Your work is reproducible across sessions, not improvised every time.

Improve Together

Recipes evolve through use. Confidence gates flag what’s ready to ship versus what needs another pass. Versioning preserves what worked. The audit trail is the product.

What’s in the Framework

  • Recipes — Individual prompts with variables and instructions
  • Cookbooks — Collections of related recipes
  • Projects — Complete workspaces with context and history
  • Ingredients — Reusable elements (personas, profiles, libraries)
  • Workflows — Multi-recipe sequences for complex tasks

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 cohort · Closes September 1, 2026

→ Join the Free CRAFT Beta

Define once. Use everywhere.