Doc Summary
Learn what CRAFT recipes are, how they work, and why they make AI interactions more consistent and efficient.
Reading time: About 5 minutes Skill level: Beginner
WHAT YOU WILL LEARN
After reading this article, you will understand what a CRAFT Recipe is, how recipes differ from regular prompts, and how to read and use recipes in your own work.
WHAT IS A RECIPE
A recipe is a reusable prompt template with defined parameters, structure, and expected outputs.
Think of it like a recipe card in your kitchen. A cooking recipe tells you what ingredients you need, what steps to follow, and what result to expect. You can make the dish multiple times and get consistent results. You can adjust ingredients to taste while following the same basic process.
A CRAFT Recipe works the same way. It defines what information you need to provide, what steps the AI should follow, and what output you should receive. You can run the recipe multiple times with different inputs and get consistent, predictable results.
RECIPES VS REGULAR PROMPTS
A regular prompt is a one-time message you send to an AI. You write it, send it, get a response, and move on. If you want similar results later, you need to remember what you wrote or find it in your chat history.
A recipe is different in several important ways.
Recipes are parameterized. Instead of writing everything from scratch, you fill in specific blanks. The recipe handles the structure, context, and instructions. You provide the details that change each time you use it.
Recipes are documented. Each recipe includes a description of what it does, what inputs it needs, and what outputs it produces. You know what to expect before you run it.
Recipes are versioned. When a recipe improves, the version number changes. You can track which version you used and update to newer versions when available.
Recipes are shareable. Because recipes have defined structure, you can share them with others. They can use your recipes without needing to understand how you built them.
ANATOMY OF A RECIPE
Every CRAFT Recipe contains several standard components.
The Recipe ID is a unique identifier that follows a specific pattern. It tells you which category the recipe belongs to and what version you are using. For example, RCP-004-001-002-TARGET-AUDIENCE-v1.00a identifies a recipe in category 004, subcategory 001, sequence 002, named TARGET-AUDIENCE, version 1.00a.
The Title describes what the recipe does in plain language. Something like “Target Audience Analyzer” or “Elevator Pitch Builder” tells you immediately what to expect.
The Description provides more detail about the recipe’s purpose, what problems it solves, and what outcomes it produces.
The Category indicates which cookbook the recipe belongs to and what domain it addresses. Core recipes handle fundamental tasks. Brand recipes address branding and identity. Content recipes focus on writing and creation.
The Difficulty rating tells you how complex the recipe is. Beginner recipes are straightforward. Intermediate recipes require more context or produce more complex outputs. Advanced recipes involve multiple steps or sophisticated analysis.
The Parameters section defines what inputs the recipe needs. Some parameters are required. Others are optional with default values. Each parameter has a type, description, and often examples of valid inputs.
The Prompt Template contains the actual instructions the AI follows when you run the recipe. This is the heart of the recipe, structured to produce consistent results.
HOW TO USE A RECIPE
Using a recipe involves three basic steps.
First, you identify the recipe you need. Browse available cookbooks, read recipe descriptions, and find one that matches your goal.
Second, you provide the required parameters. Look at what the recipe needs and prepare your inputs. Required parameters must be provided. Optional parameters can be skipped if the defaults work for you.
Third, you execute the recipe. This typically means including the recipe in your CRAFT session and providing your parameters using the comment system. The AI reads the recipe and follows its instructions.
When execution completes, you receive structured output. The recipe defines what that output looks like, so you know what to expect.
RECIPE PARAMETERS EXPLAINED
Parameters are the variables that change each time you run a recipe. They let you customize the recipe for your specific situation without rewriting the entire prompt.
Required parameters must be provided for the recipe to work. If you skip a required parameter, the recipe cannot execute properly.
Optional parameters have default values. If you do not provide them, the recipe uses the default. If you want something different, you override the default with your own value.
Parameter types tell you what kind of input is expected. A string parameter expects text. A list parameter expects multiple items. A boolean parameter expects true or false.
Here is an example. A recipe for analyzing target audiences might have these parameters:
Required: business_context (string) – Description of your business and what you offer.
Required: depth_mode (string) – How thorough you want the analysis. Options are quick, standard, or comprehensive.
Optional: existing_research (string) – Any audience research you already have. Default is none.
Optional: include_anti_persona (boolean) – Whether to define who is not your audience. Default is false.
When you run this recipe, you must provide business_context and depth_mode. You can optionally provide existing_research or set include_anti_persona to true if you want those features.
RECIPE OUTPUT
Recipes produce structured output. Unlike freeform AI responses that vary each time, recipe output follows a defined format.
This consistency makes recipe output more useful. You know where to find specific information. You can copy output blocks for use elsewhere. You can compare output from different runs because the structure matches.
Many recipes produce summary blocks designed for downstream use. A target audience recipe might produce a Target Audience Profile Block that feeds directly into a value proposition recipe. This chaining is intentional and enables multi-recipe workflows.
FINDING THE RIGHT RECIPE
Recipes are organized into cookbooks by domain. When looking for a recipe, start with the relevant cookbook.
The Core Cookbook contains foundational recipes that apply across domains. Session initialization, handoff creation, and general-purpose utilities live here.
Specialized cookbooks focus on specific domains. A Brand Identity Cookbook contains recipes for brand development. A Content Cookbook contains recipes for writing and creation.
Within each cookbook, recipes are organized by purpose. Browse the recipe list, read descriptions, and identify which recipe matches what you need to accomplish.
COMMON QUESTIONS
Q: Can I modify recipes? A: Yes. Recipes are text that you control. You can adjust parameters, modify instructions, or create variations. Save modifications as new recipes with updated version numbers.
Q: What if a recipe does not produce what I need? A: First, check your parameters. Incorrect inputs produce incorrect outputs. If parameters are correct and output is still wrong, the recipe may not match your use case. Look for a different recipe or consider modifying this one.
Q: Do I need to understand how recipes work internally? A: Not necessarily. You can use recipes effectively by understanding what they do and what parameters they need. Understanding internal structure helps if you want to modify recipes or create your own.
Q: How do recipes relate to cookbooks? A: Cookbooks are collections of related recipes. A cookbook organizes recipes by domain or purpose. You might use multiple recipes from the same cookbook for a complete workflow.