Creates a fully configured CRAFT project workspace in Claude Cowork
Dual-mode architecture: starter kit mode copies a pre-built template kit (CP-060b) and replaces 22 placeholder variables, while legacy mode generates all project files from scratch. Both modes produce the same 7-folder structure with project files, CLAUDE.md, .gitignore, recipe index, manifest, and Lessons Learned pre-seeded with universal Cowork lessons. Replaces the Core Project Creator for all Cowork projects.
Cowork Project Creator
Tags: Introduced in Beta, Project Creation, Scaffold, Starter Kit, Legacy, Placeholder, CLAUDE.md, Git, Dual-Mode, Bridge, Cowork
TL;DR
What It Does
Creates a fully configured CRAFT project workspace in Claude Cowork. Dual-mode architecture: starter kit mode copies a pre-built template kit (CP-060b) and replaces 22 placeholder variables, while legacy mode generates all project files from scratch. Both modes produce the same 7-folder structure with project files, CLAUDE.md, .gitignore, recipe index, manifest, and Lessons Learned pre-seeded with universal Cowork lessons. Replaces the Core Project Creator for all Cowork projects.
How It Works
Eight steps. Step 0 scans the workspace for starter kit indicators — looking for [STARTER-KIT]*.txt templates, master templates, cookbooks, spec files, universal lessons, recipe index, and branding config. Step 1 recommends a mode based on what was found (starter kit if the full kit is detected, legacy otherwise). Step 2 gathers project details through either a copy-paste questionnaire (17 questions across 6 sections) or interactive one-at-a-time prompts. Step 3 displays a confirmation summary and builds a 22-variable placeholder map from the discovery data. In starter kit mode (Step 4), the recipe copies the kit to the workspace, generates project files from [STARTER-KIT] templates by replacing placeholders, and cleans up kit artifacts. In legacy mode (Step 4L), the recipe creates the 7-folder structure and generates 7 files from scratch. Step 5 validates — scanning for unreplaced placeholders and running a CWK-024 verification gate with 6 structural checks. Step 6 offers git initialization with optional GitHub remote setup (PAT-in-URL pattern). Step 7 generates the initial H001 handoff via CWK-002. Step 8 displays a completion report.
What To Expect
A fully scaffolded CRAFT project workspace with all standard files, folder structure, and configuration ready for the first working session. CLAUDE.md loads automatically on next session start. Lessons Learned comes pre-seeded with universal Cowork operational knowledge (sandbox constraints, PAT patterns, crash protection). The completion report lists all created files and next steps.
Best Results When You
Have your project details ready before starting — project number, name, purpose, success metrics, and audience at minimum. If using starter kit mode, ensure the CP-060b kit is in the workspace before running. For GitHub setup, create the repo on github.com first (API creation is blocked by the Cowork proxy).
Typical Time
5–15 minutes for interactive discovery. 2–5 minutes if you have answers pre-written and use questionnaire mode with a starter kit. Legacy mode adds 1–2 minutes for from-scratch file generation.
Difficulty
Medium — the recipe guides you through every step, but project discovery requires decisions about configuration, persona selection, and priorities. Understanding the difference between starter kit and legacy mode helps you choose the right path.
How To Start
This recipe can be invoked directly or called by CWK-001 (Session Init) during Step 0b for new project creation. It replaces the Core Project Creator for all Cowork projects.
STEP 1Choose Mode and Provide Project Details
The recipe scans your workspace, recommends a creation mode, and gathers your project details through a questionnaire or interactive conversation.
Available parameters
-
mode
· string · optional · default: auto
Creation mode. “auto” detects the starter kit and recommends accordingly. “starter_kit” forces kit mode (requires CP-060b in workspace). “legacy” forces from-scratch generation (v1.01a behavior). -
starter_kit_source
· string · optional
Path to the starter kit folder if not auto-detected. Default: scans for [STARTER-KIT]*.txt templates in the workspace. -
project_id
· string · optional
Project ID number if already known (e.g., “061”). Skips the project number question in discovery. -
discovery_mode
· string · optional · default: offer_choice
How to gather project info. “questionnaire” displays all questions for copy-paste. “interactive” asks one at a time. “offer_choice” lets you pick. -
skip_about_me
· boolean · optional · default: false
Skip the About Me section of project discovery. Use when user information is already known from a parent project. -
github_setup
· boolean · optional · default: false
Configure GitHub remote after git init. Requires a user-created repo and personal access token. API repo creation is blocked by the Cowork proxy. -
universal_lessons_file
· string · optional · default: CRAFT-UNIVERSAL-LESSONS.txt
Path to universal lessons file for Lessons Learned seeding. If not found, the recipe warns but continues without pre-seeded operational knowledge.
Invocations
Create project (auto mode)
#H->AI::Directive: (Create a new CRAFT project)
Create project with starter kit
#H->AI::Directive: (Create a new CRAFT project with mode="starter_kit")
Create project from scratch
#H->AI::Directive: (Create a new CRAFT project with mode="legacy")
Usage Examples
EXAMPLE 1Creating a project with the starter kit
User
Create a new CRAFT project for my blog redesign.
Cat
Scanning workspace. Starter kit detected — 4 templates, 4 cookbooks, 2 spec files. Recommending starter kit mode. How would you like to provide project details? [1] Questionnaire [2] Interactive. User chooses interactive. Cat walks through project number, name, purpose, metrics, audience, configuration. Confirmation summary displayed. User approves. Kit copied, 22 placeholders replaced, CWK-024 validation passed. Git initialized, initial commit made. H001 handoff generated. Project ready.
EXAMPLE 2Legacy mode when no starter kit is available
User
I need a new project but I do not have the starter kit files.
Cat
No starter kit detected — using legacy generation mode. How would you like to provide project details? User pastes questionnaire answers. Cat generates 7 files from scratch, creates 7-folder structure, seeds Lessons Learned with 17 universal entries. Validation passed. Git initialized. Project ready with all standard files.
EXAMPLE 3Questionnaire mode with GitHub setup
User
Create a project. I want to fill out a form and set up GitHub.
Cat
Displays 17-question questionnaire. User copies to text editor, fills in answers, pastes back. Cat parses answers, shows confirmation. User approves. Starter kit personalized. Validation passed. Git initialized. User provides repo URL and PAT. Remote configured, pushed, PAT scrubbed. Project ready with full GitHub integration.
How AI Reads This Recipe
When this recipe is triggered, the AI creates a new CRAFT project workspace in one of two modes. The AI should:
- Scan environment (Step 0). Verify workspace folder is mounted. Scan for starter kit indicators: [STARTER-KIT]*.txt templates (need ≥4), [MASTER-TEMPLATE]*.txt (need ≥2), cookbooks (need ≥4 for starter kit, ≥1 for legacy), spec files, universal lessons, recipe index, and branding config. Determine which modes are available. Read CRAFT-UNIVERSAL-LESSONS.txt if found and prepare seeding entries.
- Select mode (Step 1). If mode parameter is set, use it (validate availability). If auto and starter kit is available, recommend starter kit with option to choose legacy. If no starter kit, default to legacy mode.
- Discover project details (Step 2). Offer questionnaire or interactive discovery. Questionnaire: display 17 questions across 6 sections (Identity, Purpose, Configuration, Communication, About You, Priorities). Interactive: walk through each section conversationally. Validate required fields: project_number, project_name, project_phase, main_purpose, success_metrics, target_audience. Build 22-variable placeholder map from discovery data.
- Confirm (Step 3). Display project summary with mode, ID, name, configuration, folder structure, and file/placeholder counts. Allow edits before proceeding.
- Create files. In starter kit mode (Step 4): copy kit to workspace, read each [STARTER-KIT] template, replace all placeholders, write final files (CLAUDE.md, .gitignore, RECIPE-INDEX, MANIFEST, LL, project file, history file), clean up kit artifacts. In legacy mode (Step 4L): create 7-folder structure, generate 7 files from templates or from scratch, seed LL with universal entries if available.
- Validate (Step 5). Grep for unreplaced {PLACEHOLDER} variables (excluding framework/ and templates/). Verify all expected files exist. Run CWK-024 verification gate with 6 structural checks (folders, project ID, CLAUDE.md name, no unreplaced placeholders, LL seed count, manifest file counts).
- Git + Handoff (Steps 6–8). Offer git init via CWK-004 and initial commit via CWK-005. Optional GitHub remote with PAT (scrub immediately per ULL-005). Generate H001 handoff via CWK-002. Display completion report with file list and next steps.
Error handling: if starter kit copy fails, fall back to legacy. If placeholder replacement misses variables, report in validation. If universal lessons missing, warn but continue. If git fails, save files anyway. If CWK-024 verification fails, report but do not block git init.
When To Use This Recipe
Use this recipe when you are starting a brand-new CRAFT project in Claude Cowork and need the full workspace scaffold with folders, configuration, and pre-seeded operational knowledge. Use starter kit mode when you have the CP-060b kit available for the fastest path. Use legacy mode when generating files from scratch without a kit. Use this recipe when you want CLAUDE.md auto-configured so the AI picks up your project context automatically on the next session.
Do Not Use When
You already have a working CRAFT project and want to modify its configuration — use the relevant admin recipes instead (CWK-ADM series). If you need to import an existing non-CRAFT project into CRAFT, that is a different workflow outside this recipe’s scope.
Recipe FAQ
What is the difference between starter kit and legacy mode?
Starter kit mode copies a pre-built template kit (CP-060b) and personalizes it by replacing 22 placeholder variables. It includes all framework files, branding scaffold, and spec files out of the box. Legacy mode generates 7 core files from scratch using master templates and creates the folder structure manually. Both produce the same final result, but starter kit is faster and includes more framework infrastructure.
What are the 22 placeholder variables?
Variables like {PROJECT_ID}, {PROJECT_NAME}, {VERSION}, {DATE}, {FLAVOR}, {PERSONA}, {OWNER}, {PHASE}, {LOCATION}, {EXPERTISE}, and others derived from your discovery answers. Each uses {VARIABLE_NAME} syntax and is replaced across all template files during personalization.
What files does the recipe create?
Seven core files: CLAUDE.md (project context, auto-loaded), .gitignore, CRAFT-RECIPE-INDEX.txt, PROJECT-MANIFEST.txt, Lessons Learned (pre-seeded), project implementation file, and AI chat history file. Starter kit mode also includes framework cookbooks, spec files, and branding scaffold (totaling approximately 36 files).
What happens if universal lessons are not found?
The recipe warns but continues. Your project will work, but the AI will not have pre-loaded knowledge about Cowork sandbox constraints (git pull blocked, index.lock cascade, PAT auth patterns) until those issues are discovered during actual use.
Can I customize the questionnaire answers later?
Yes. The answers populate CLAUDE.md and the project file, both of which can be edited directly. CLAUDE.md is the primary configuration surface — changes there take effect on the next session start.
Why is GitHub repo creation not automated?
The Cowork sandbox proxy blocks GitHub API calls for repo creation. You need to create the repo manually on github.com first, then provide the URL and a personal access token. The recipe handles remote configuration, push, and PAT scrubbing.
Version History
v2.00a — 2026-03-09
Dual-mode architecture: starter kit (primary) plus legacy (fallback). Starter kit copies CP-060b and replaces 22 placeholder variables. CWK-024 validation gate added. Branding scaffold included. Template-driven file generation.
v1.01a — 2026-03-04
Folder structure support with 7-folder layout via CWK-009. PROJECT-MANIFEST.txt added as 7th output file. Glob patterns updated for folder-prefixed paths.
v1.00a — 2026-03-02
Initial creation replacing Core Project Creator for Cowork. 6-file output with universal lessons seeding. Integrated git init and GitHub remote setup with PAT guidance.
Get this recipe with CRAFT for Claude Cowork
Cowork recipes ship bundled with CRAFT for Claude Cowork — there’s no separate download. Clone the framework once, and your AI runs every recipe automatically when invoked.
Pull anytime to stay on the latest version — free to clone, no login or email required.
Then start your session
Once CRAFT is in your project folder, open a new Cowork session and ask Claude to initialize. For example:
You
Please initialize my CRAFT session.
Claude
CRAFT session ready. Your project is loaded, your persona is active, and your recipes are available. What would you like to work on?
Not familiar with Git? Download as a ZIP
No command line needed. Just download, move, and unzip:
- Open the CRAFT framework repo on GitHub.
- Click the green Code button, then choose Download ZIP.
- Move the downloaded ZIP into your Claude Cowork project folder.
- Unzip it: double-click on Mac, or right-click → Extract All on Windows.
