Doc Summary
Understand why CRAFT uses cooking terminology and how this metaphor makes AI frameworks accessible to everyone.
Reading time: About 3 minutes Skill level: Beginner
WHAT YOU WILL LEARN
After reading this article, you will understand why CRAFT chose the cooking metaphor, how each cooking term maps to an AI concept, and why this approach makes the framework easier to learn and use.
WHY COOKING
CRAFT could have used programming terminology. It could have called things modules, functions, libraries, and packages. Many AI tools do exactly that.
The problem is that programming language creates barriers. When someone encounters terms like instantiation, polymorphism, or dependency injection, they either already know what these mean or they feel excluded. Technical terminology signals that a tool is for developers, even when it does not need to be.
Cooking is different. Nearly everyone has followed a recipe. Most people understand what a cookbook is. The concept of ingredients that combine to create something is universal. You do not need special training to grasp these ideas.
This accessibility is strategic, not simplistic. CRAFT handles sophisticated AI workflows. The cooking metaphor makes that sophistication approachable without dumbing it down.
THE COMPLETE MAPPING
Every CRAFT term has a cooking equivalent. Understanding this mapping helps you navigate the framework intuitively.
Recipe equals recipe card. A CRAFT Recipe is a set of instructions with defined inputs and expected outputs. Just like a cooking recipe tells you what ingredients to gather and what steps to follow, a CRAFT Recipe tells you what parameters to provide and what process to execute. The result is consistent and repeatable.
Cookbook equals cookbook collection. A CRAFT cookbook gathers related recipes by theme. A baking cookbook collects baking recipes. A Brand Identity Cookbook collects brand development recipes. The organization helps you find what you need quickly.
Ingredient equals pantry staple. CRAFT ingredients are reusable components you reach for across many recipes. Personas, Profiles, and other elements work like olive oil, salt, or stock in your kitchen. You define them once and use them repeatedly.
Persona equals chef’s specialty and style. When you activate a persona, you shape how the AI approaches its work. A chef trained in French cuisine cooks differently than one trained in Japanese cuisine. A persona trained for strategic branding responds differently than one trained for technical documentation.
Profile equals dietary preferences and restrictions. A Profile provides context that shapes how the AI tailors its output. Just as knowing someone is vegetarian changes what you cook for them, knowing a user’s professional background or an organization’s brand voice changes how the AI responds.
Project equals your kitchen setup. Your CRAFT project is your personal workspace with your tools arranged your way. Your preferences, your ongoing work, your context. When you enter your kitchen, everything is where you expect it.
Multi-recipe workflow equals multi-course meal. When you prepare a dinner party menu, each course builds on the previous preparation. The appetizer timing affects the main course. The main course flavors guide the dessert. A workflow connects recipes the same way, with each step building on what came before.
Handoff equals notes for the next shift. In a restaurant kitchen, the departing shift leaves notes for the arriving shift. What is prepped, what needs attention, what is the priority. CRAFT handoffs do the same thing between AI sessions, enabling seamless continuity.
Framework Specification equals culinary school fundamentals. Before you cook professionally, you learn foundational techniques. Knife skills, heat control, flavor balancing. The Framework Specification teaches the AI the foundational rules of CRAFT.
Core Cookbook equals classic recipe collection. Every kitchen has go-to recipes that work reliably. The Core Cookbook provides essential recipes that every CRAFT user needs, regardless of their specific domain.
WHY THIS MATTERS
The metaphor is not decoration. It serves three practical purposes.
First, faster learning. When you already understand the source concept, you learn the target concept faster. Everyone knows what a recipe is. Transferring that understanding to CRAFT recipes takes seconds, not hours.
Second, better memory. Concrete metaphors stick better than abstract definitions. You will remember that a cookbook collects related recipes more easily than you would remember that a category-organized prompt template repository aggregates thematically related parameterized instruction sets.
Third, easier communication. When you explain CRAFT to others, the cooking metaphor gives you familiar language. Instead of technical jargon that requires translation, you use terms everyone already knows.
A NOTE ON SOPHISTICATION
Some people wonder if the cooking metaphor makes CRAFT seem less serious or capable. The opposite is true.
Professional kitchens produce extraordinary results using exactly this vocabulary. Michelin-starred restaurants run on recipes, ingredients, and coordinated workflows. The terminology does not limit what is possible.
CRAFT works the same way. The accessible metaphor opens the door. The framework’s depth handles whatever complexity you bring through that door.