RCP-CWK-040 Brand Kit Builder

Walks you through a guided Q&A session to populate your project’s brand configuration file

Walks you through a guided Q&A session to populate your project’s brand configuration file (branding/BRAND-CONFIG.txt). Covers brand fundamentals (name, tagline, mission, voice, personality), visual identity (colors, fonts, logo), and content guidelines (tone, terminology, audience). Creates a structured brand profile that other recipes can reference for consistent branding across your project.

Brand Kit Builder

Cowork | Bridge | Difficulty: Beginner | Time: 10–15 min
Tags: Introduced in Beta, Bridge, Branding, Brand Kit, Configuration, Q&A, Beginner, Cowork

TL;DR

What It Does
Walks you through a guided Q&A session to populate your project’s brand configuration file (branding/BRAND-CONFIG.txt). Covers brand fundamentals (name, tagline, mission, voice, personality), visual identity (colors, fonts, logo), and content guidelines (tone, terminology, audience). Creates a structured brand profile that other recipes can reference for consistent branding across your project.
How It Works
Six steps. (0) Pre-flight check — verifies the branding/ folder exists and reads any existing BRAND-CONFIG.txt state. (1) Mode setup — standalone mode with 8–14 core questions. (2) Brand discovery Q&A — walks through three sections: fundamentals (5 questions), visual identity (6 questions), and content guidelines (3 questions). You can answer normally, skip sections, or finalize early. (3) Populate BRAND-CONFIG.txt — maps your answers to config fields and writes them. (4) Asset inventory — optionally register brand assets like logos and style guides. (5) Verification gate — reads back the config, reports field coverage, and asks for confirmation. (6) Git checkpoint via CWK-005.
What To Expect
An interactive Q&A session where Cat asks about your brand, section by section. After answering, your branding/BRAND-CONFIG.txt is populated with up to 14 fields plus an optional asset inventory. A verification report shows how many fields were filled and which sections are complete.
Best Results When You
Have your brand basics in mind before starting — name, colors, fonts. Even rough answers work; you can refine later by re-running with specific sections. If you already have a detailed brand identity process, consider the BRAND-ID cookbook archive for intensive brand work.
Typical Time
10–15 minutes for a full run through all sections. Partial runs (targeting specific sections) take 5–10 minutes.
Difficulty
Beginner — no technical knowledge required. The recipe asks plain-language questions and handles all file operations. Ideal for early project setup.

How To Start

This recipe is the entry point for brand configuration in CRAFT projects. Run it early in project setup to establish branding fundamentals that other recipes can reference for consistent output. The branding/ folder must exist first — run CWK-009 (Cowork Project Folder Setup) if it doesn’t. For intensive brand identity work beyond these core questions, the BRAND-ID cookbook is available as an external add-on archive.

STEP 1Start Brand Kit Builder

Optionally specify which sections to populate and whether to skip the git checkpoint.
Available parameters
  • mode · string · optional · default: standalone
    Standalone mode uses 8–14 built-in core questions. For intensive branding, see the BRAND-ID archive.
  • sections · list · optional · default: all
    Sections to populate: all, fundamentals, visual, content, assets. Allows partial runs to target specific areas.
  • skip_git · boolean · optional · default: false
    Skip the git checkpoint at Step 6 if true.
Invocations
Full brand kit — all sections
#H->AI::Directive: (Execute CWK-040)
Visual identity only
#H->AI::Directive: (Execute CWK-040 with sections=["visual"])
Skip git checkpoint
#H->AI::Directive: (Execute CWK-040 with skip_git=true)

Usage Examples

EXAMPLE 1Full brand kit build from scratch

User
Let’s set up the brand kit for this project.
Cat
Brand Kit Builder — standalone mode. branding/ folder found. BRAND-CONFIG.txt exists with 0/14 fields populated. Starting brand discovery. Section 1: Brand Fundamentals. What is your brand name? [User answers all questions across 3 sections] Writing brand configuration. Updated 14 fields. Verification: 14/14 fields, 3/3 sections complete. Git checkpoint complete. Brand Kit Builder done.

EXAMPLE 2Partial run — visual identity only

User
I just need to update the visual identity section — we changed our colors.
Cat
Brand Kit Builder — standalone mode. BRAND-CONFIG.txt: 14/14 fields populated. Some fields already populated. Overwrite existing values, or only fill empty fields? [User: overwrite for visual section] Section 2: Visual Identity. Primary brand color? [User provides updated values] Updated 6 fields. Verification: 14/14 fields, 3/3 sections. Visual identity refreshed. Git checkpoint complete.

EXAMPLE 3Missing branding folder

User
Build the brand kit.
Cat
branding/ folder not found. Run CWK-009 (Cowork Project Folder Setup) to create the 7-folder structure, then return here.

How AI Reads This Recipe

When this recipe is triggered, the AI guides a brand discovery Q&A session and populates the project’s brand configuration file. The AI should:
  1. Pre-flight check. Verify branding/ folder exists — if missing, direct user to CWK-009 and stop. Read branding/BRAND-CONFIG.txt. If missing, create scaffold. If partially populated, report current state and ask whether to overwrite or only fill empty fields. Store pre-state for verification diff.
  2. Mode setup. Set standalone mode (8–14 core questions). Report mode to user.
  3. Brand discovery Q&A. Walk through targeted sections. Fundamentals: brand name, tagline, mission statement, brand voice, personality traits (5 questions). Visual identity: primary color, secondary color, accent color, primary font, secondary font, logo file path (6 questions). Content guidelines: tone of voice, terminology preferences, audience description (3 questions). Allow “skip” and “done” commands.
  4. Populate BRAND-CONFIG.txt. Map answers to the 14 config fields. Respect overwrite mode — skip populated fields if user chose “only fill empty.” Report count of updated fields.
  5. Asset inventory (optional). If “assets” section targeted, ask about brand assets. Accept one-per-line format (filename | description | date). Write to Section 4 of BRAND-CONFIG.txt.
  6. Verification gate. Re-read BRAND-CONFIG.txt. Count populated fields, complete sections, new fields this run. Present verification report. Ask user to confirm or request revisions.
  7. Git checkpoint. Unless skip_git is true, execute CWK-005 with branding/BRAND-CONFIG.txt. Note BRAND-ID cookbook archive availability for intensive brand work.

When To Use This Recipe

Use this recipe when setting up a new project and need to establish brand fundamentals, when you want to formalize your project’s visual identity and content guidelines in a structured config file, or when other recipes need brand information and branding/BRAND-CONFIG.txt is empty.
Do Not Use When
You need intensive brand identity work covering competitive positioning, audience personas, campaign architecture, and content strategy — use the BRAND-ID cookbook archive instead (framework/archive/BRAND-ID-ARCHIVE.txt). For one-off visual asset creation without brand configuration, work directly with your design tools.

Recipe FAQ

What is the BRAND-ID cookbook archive?
An optional add-on with 16 specialized recipes for intensive brand identity work — covering brand foundation (context, audience, pain points, value props, competitive positioning, elevator pitch, profile synthesis) and campaign architecture (campaigns, messaging, content pillars, channels, timelines, content calendar, social posts, blog planning, performance analysis). CWK-040 handles the core brand configuration; BRAND-ID goes much deeper.
Can I run this recipe multiple times?
Yes. On subsequent runs, it detects already-populated fields and asks whether to overwrite or only fill empty ones. You can target specific sections with the sections parameter to update just what changed.
What happens if I skip a section?
Fields in that section remain unchanged (empty if new, or preserving existing values). You can come back and fill them later with a partial run targeting that section.
Do other recipes read BRAND-CONFIG.txt?
Yes — recipes that generate content, create templates, or produce branded output can reference branding/BRAND-CONFIG.txt for consistent colors, fonts, tone, and terminology. The file is the single source of truth for project branding.
What if I don’t know my brand colors yet?
Skip the visual identity section and come back when you’ve decided. Or provide rough answers — you can always re-run with sections=["visual"] to update later. The recipe is designed for iterative refinement.

Version History

v1.00a — 2026-02-17
Initial creation per H048 CWK-021 analysis (R-3, Tier 2 branding). Standalone mode with 8–14 core questions across fundamentals, visual identity, and content guidelines. BRAND-CONFIG.txt population with verification gate. Optional asset inventory. BRAND-ID cookbook referenced as external add-on for intensive work.

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?

What is CRAFT for Claude Cowork?

Not familiar with Git? Download as a ZIP

No command line needed. Just download, move, and unzip:

  1. Open the CRAFT framework repo on GitHub.
  2. Click the green Code button, then choose Download ZIP.
  3. Move the downloaded ZIP into your Claude Cowork project folder.
  4. Unzip it: double-click on Mac, or right-click → Extract All on Windows.

Similar Posts