Doc Summary
Learn how CRAFT files and recipes are named so you can read, organize, and create properly identified components.
Reading time: About 4 minutes Skill level: Beginner
WHAT YOU WILL LEARN
After reading this article, you will understand how CRAFT files are named, how recipe IDs are structured, and how version numbers work. This knowledge helps you navigate CRAFT files and understand what you are looking at when you encounter them.
WHY NAMING MATTERS
Consistent naming serves several purposes. It tells you what a file contains before you open it. It identifies which project a file belongs to. It shows which version you have. It enables tools and people to find things quickly.
CRAFT uses predictable patterns so you always know what you are looking at. Once you learn the patterns, any CRAFT file becomes immediately recognizable.
THE FOUR FILE TYPES
CRAFT uses four types of files, each with its own naming pattern.
Framework Specification
Pattern: CFT-FWK-SPEC-vMMYYaX.txt
Example: CFT-FWK-SPEC-v1125a1.txt
Breakdown:
- CFT identifies this as a CRAFT file
- FWK indicates framework level (not project-specific)
- SPEC identifies this as the specification file
- v1125a1 is the version (November 2025, revision a1)
- .txt is the file extension
This file contains the authoritative rules and protocols for CRAFT. There is typically one current version that everyone uses.
Core Cookbook
Pattern: CFT-FWK-COOKBK-CORE-vMMDDaX.txt
Example: CFT-FWK-COOKBK-CORE-v1125d3.txt
Breakdown:
- CFT-FWK indicates framework level
- COOKBK identifies this as a cookbook
- CORE specifies which cookbook (the foundational one)
- v1125d3 is the version (November 2025, revision d3)
Specialized cookbooks replace CORE with their domain: BRAND-ID for branding, CONTENT-AND-PROMO for content creation.
Project File
Pattern: CFT-PROJ-CP-XXX_PROJECT-NAME-vMMDDaX.txt
Example: CFT-PROJ-CP-045_BRANDING-AND-MESSAGING-v1118a1.txt
Breakdown:
- CFT-PROJ indicates this is a project file
- CP stands for CRAFT Project
- XXX is a three-digit project number (045)
- PROJECT-NAME is uppercase with hyphens (BRANDING-AND-MESSAGING)
- v1125a1 is the version (November 2025, revision a1)
The project number helps you track multiple projects. The name tells you what the project is about.
Chat History File
Pattern: CFT-PROJ-CP-XXX_AI-CHAT-HISTORY-vMMDDaX.txt
Example: CFT-PROJ-CP-045_AI-CHAT-HISTORY-v1225b2.txt
Breakdown:
- CFT-PROJ-CP-XXX matches the associated project file
- AI-CHAT-HISTORY identifies the file type
- Version tracks updates to this continuity record
The project number links this file to its corresponding project file. They work as a pair.
VERSION NUMBERING
CRAFT uses a date-based version pattern: vMMDDaX
MM is the two-digit month (01-12) DD is the two-digit year (01-99) a is a letter indicating the revision series (a, b, c, etc.) X is a number within that series (1, 2, 3, etc.)
Examples:
- v1125a1 means November 2025, first version of the a series
- v1125a2 means November 2025, second version of the a series
- v1125b1 means November 2025, first version of the b series (new revision series)
- v1225b2 means December 2025, second version of the b series
This pattern lets you quickly see when a file was created or updated and how many revisions it has gone through.
RECIPE ID FORMAT
Recipes use a different identification system that encodes their location and version.
Pattern: RCP-XXX-YYY-ZZZ-NAME-vMAJOR.MINORpatch
Example: RCP-004-001-002-TARGET-AUDIENCE-v1.00a
Breakdown:
- RCP is the fixed prefix identifying CRAFT recipes
- XXX is the category number (004 = Brand Identity Cookbook)
- YYY is the subcategory number (001 = Foundation subcategory)
- ZZZ is the sequence number within that subcategory (002)
- NAME is a descriptive name in uppercase (TARGET-AUDIENCE)
- vMAJOR.MINORpatch is semantic versioning (v1.00a)
This structure tells you exactly where to find the recipe. RCP-004-001-002 means: category 004, subcategory 001, sequence 002.
CATEGORY NUMBERS
Each cookbook has a reserved category number.
CAT-001: Core Cookbook (foundational recipes) CAT-002: Content and Promo Cookbook CAT-004: Brand Identity Cookbook
When you see a recipe ID starting with RCP-001, you know it belongs to the Core Cookbook. RCP-004 recipes belong to the Brand Identity Cookbook.
HANDOFF NUMBERING
Handoffs within the Chat History file use sequential numbering.
Pattern: H followed by a three-digit number
Examples: H001, H002, H003, H013
The most recent handoff has the highest number. When you open a Chat History file, look for the highest-numbered handoff to find the latest session context.
Handoffs are organized in reverse chronological order within the file, so the most recent appears first.
PRACTICAL TIPS
When creating new project files, pick an unused three-digit project number. Check your existing projects to avoid duplicates.
When updating files, increment the version appropriately. Small changes might go from v1125a1 to v1125a2. Larger revisions might start a new series at v1125b1.
Project names should be uppercase, use hyphens instead of spaces, and describe the project clearly. BRANDING-AND-MESSAGING is better than PROJECT1 or MISC.
Keep your project file and chat history file versions in sync when possible. They are a pair and should evolve together.
COMMON QUESTIONS
Q: What if I make a mistake in naming? A: Rename the file to fix it. CRAFT reads the content, so correcting the filename does not break anything. Just maintain consistency going forward.
Q: Do I have to use these exact patterns? A: For compatibility with CRAFT documentation and community sharing, yes. The patterns ensure everyone can understand and work with each other’s files.
Q: What do the category numbers mean beyond identification? A: They organize recipes into logical groups and help the system route requests to appropriate recipes. The number itself is arbitrary but consistent.