View Categories

Getting Started with CRAFT Studio

Richard Ketelsen's avatar
Richard Ketelsen
Updated on December 9, 2025

4 min read

AI Doc Summarizer Doc Summary

Category: Installation & Setup
Type: Tutorial
Reading Time: 8 minutes
Skill Level: Intermediate

STUDIO

— “Your workshop. Your rules.”

This guide walks you through creating your first CRAFT Studio project. Unlike Foundations and Express, Studio requires initial setup — you’ll create project-specific files tailored to your work. The investment pays off in persistent context, custom configuration, and multi-session continuity.

Time to complete: 10-15 minutes

What is CRAFT Studio? #

Studio is the complete CRAFT environment for practitioners running defined projects. Where Express handles varied quick tasks, Studio excels at work that spans multiple sessions and benefits from persistent context.

Think of it as the difference between a food truck (Express) and your own kitchen (Studio). The food truck is fast and convenient. Your kitchen takes setup, but everything is arranged exactly how you want it.

When to Use Studio #

Studio is right for you when:

  • You’re working on a defined project (not random tasks)
  • The work will span multiple sessions over days or weeks
  • You want to store project-specific variables and context
  • You prefer choosing which persona assists you
  • You value organizational structure

If you’re doing quick, varied tasks — stick with Express. Studio’s setup overhead isn’t worth it for one-off work.

What You’ll Need #

  • An AI assistant that accepts file uploads
  • The two template files (Project and Chat History templates)
  • The two generic files (Framework Specification and Core Cookbook)
  • 10-15 minutes for initial setup
  • A defined project to work on

The Four Studio Files #

Studio uses four files — two generic and two project-specific:

File Type Purpose
Framework Specification Generic Core CRAFT protocols. Same file used across all versions.
Core Cookbook Generic All standard recipes. Same file used across all versions.
Project File Project-specific Your project configuration. Contains PROJECT_VARIABLES, persona preferences, and custom instructions.
Chat History Project-specific Your project continuity. Stores handoffs, decisions, and context that accumulate as your project progresses.

Setup: Creating Your First Project #

Step 1: Download the Files #

  1. Go to CRAFTFramework.ai/downloads
  2. Select “CRAFT Studio”
  3. Download the package containing:
    • Framework Specification (generic)
    • Core Cookbook (generic)
    • Project File Template
    • Chat History Template

Step 2: Create Your Project File #

Open the Project File Template and customize it:

1. RENAME THE FILE

Change: CFT-PROJ-CP-XXX_PROJECT-NAME-v*.txt
To: CFT-PROJ-CP-001_YOUR-PROJECT-NAME-v1225a1.txt

Example: CFT-PROJ-CP-001_WEBSITE-REDESIGN-v1225a1.txt

Component Meaning
CP-XXX Your project number (001, 002, etc.)
PROJECT-NAME Descriptive name (use hyphens, not spaces)
vMMYYaX Version (month, year, iteration)

2. SET PROJECT VARIABLES

Find the PROJECT_VARIABLES section and fill in your details:

PROJECT_VARIABLES = {
    "PROJECT_NAME": "Website Redesign",
    "PROJECT_DESCRIPTION": "Redesign company website for Q1 launch",
    "PROJECT_START_DATE": "2025-12-09",
    "PROJECT_OWNER": "Your Name",
    # Add any project-specific variables you need
}

3. CONFIGURE PERSONA PREFERENCES (optional)

If you want a specific persona as your default, set it in the PERSONA_PREFERENCES section. Otherwise, leave default for auto-selection.

Step 3: Create Your Chat History File #

Open the Chat History Template and customize it:

1. RENAME THE FILE

Change: CFT-PROJ-CP-XXX_AI-CHAT-HISTORY-*.txt
To: CFT-PROJ-CP-001_AI-CHAT-HISTORY-v1225a1.txt

Match the project number to your Project File.

2. UPDATE THE HEADER

Change the project reference at the top to match your project name.

3. LEAVE THE HANDOFF SECTIONS

The template includes placeholder handoff sections. These will be filled as you work.

Step 4: Start Your First Session #

  1. Open your AI assistant
  2. Start a new conversation
  3. Upload all four files:
    • CFT-FWK-SPEC-*.txt (generic)
    • CFT-FWK-COOKBK-CORE-*.txt (generic)
    • Your project file
    • Your chat history file
  4. Initialize the session:
Initialize CRAFT session for [Your Project Name]. This is a new project.

The AI will read your project configuration and confirm the setup.

Your First Studio Session #

What to Expect #

Studio sessions start with context awareness. The AI reads your PROJECT_VARIABLES and any existing handoffs before responding. This means:

  • It knows your project name and description
  • It remembers decisions from previous sessions
  • It understands your stated preferences
  • It can reference project-specific context

Working with Personas #

Studio gives you full persona control. You can:

Request a specific persona:

I'd like to work with Morgan on brand strategy today.

Let the system choose:

Who would be best for technical architecture review?

Switch mid-session:

Let's bring in the Code Mentor for this debugging section.

Creating Handoffs #

Studio handoffs are more detailed than Express. At session end:

Create a handoff for this session.

The handoff captures:

  • Session summary — what you accomplished
  • Key decisions — choices made and rationale
  • Current state — where things stand
  • Next steps — what to do next
  • Open questions — unresolved items

Your next session can read this handoff and continue seamlessly.

Studio Workflow #

A typical Studio project follows this pattern:

Phase Activities
Session 1: Setup Create project files → Define initial scope → Make early decisions → End with handoff
Session 2+: Execution Load handoff → Continue where you left off → Make progress → End with updated handoff
Final Session: Completion Review project state → Complete remaining work → Create final summary → Archive or close project

Tips for Studio Success #

Keep PROJECT_VARIABLES updated.
If key project details change, update your Project File. The AI only knows what’s in the files.

Write good handoffs.
The quality of your next session depends on the quality of your handoff. Be specific about what’s done and what’s next.

Use meaningful project numbers.
CP-001, CP-002, etc. help you track multiple projects. Some practitioners use categories: CP-1XX for client work, CP-2XX for internal projects.

Version your files.
The vMMYYaX format (v1225a1 = December 2025, iteration a1) helps track changes. Increment the iteration when you modify files.

Troubleshooting #

“The AI doesn’t remember our previous session.”
Make sure you uploaded the Chat History file with the latest handoff. Each session starts fresh — continuity comes from the handoff.

“My PROJECT_VARIABLES aren’t being used.”
Check that you saved the Project File after editing. Re-upload if needed.

“I want to switch projects mid-session.”
Create a handoff for the current project first, then start a new conversation with the other project’s files.

What’s Next #

You’re now running CRAFT Studio. As you progress:

Learn the system:

  • Understanding Projects — Deep dive into project structure
  • How to Use the Handoff System — Master session continuity
  • CRAFT Naming Conventions — File naming patterns

Expand your capabilities:

  • Understanding Recipes — Access the full recipe library
  • How to Create a Custom Persona — Build specialized AI personas

Reference:

  • CRAFT Glossary — Terminology reference
  • CRAFT FAQ — Common questions answered

Last Updated: December 2025