RCP-CWK-050 Cookbook Cheatsheet Generator

Generates a human-friendly cheatsheet file from a CRAFT cookbook

Each entry carries a standard 5-field header plus a body rendered at three detail levels: Brief (1 sentence), Simple (2–3 sentences, default), and Detailed (1–2 paragraphs). Supports single-cookbook or ALL-cookbooks mode, four output formats (txt, md, docx, html), and auto-revises stale entries when source recipe versions advance.

Cookbook Cheatsheet Generator

Cowork | Platform Bridges | Difficulty: Intermediate | Time: 5–15 min
Tags: Introduced in Beta, Platform Bridges, Cheatsheet, Human Discoverability, Cookbook, Cowork

TL;DR

What It Does
Generates a human-friendly cheatsheet file from a CRAFT cookbook. Each entry carries a standard 5-field header plus a body rendered at three detail levels: Brief (1 sentence), Simple (2–3 sentences, default), and Detailed (1–2 paragraphs). Supports single-cookbook or ALL-cookbooks mode, four output formats (txt, md, docx, html), and auto-revises stale entries when source recipe versions advance.
How It Works
Eight steps. (0) Validate parameters. (1) Load source cookbook — read, hash, parse. (2) Detect drift — compare per-recipe versions, short-circuit if hash unchanged. (3) Render entries — standard header + Brief/Simple/Detailed body. (4) Write output per mode (auto/report/both). (5) Render alternate formats (md, docx, html). (6) Version and hash — embed metadata in cheatsheet header. (7) Report — cookbooks processed, entries rendered, stale entries fixed.
What To Expect
One or more cheatsheet files in the output directory, each a navigable digest of every recipe in the source cookbook. Stale entries are auto-revised. A drift report is produced when mode=“report” or “both.”
Best Results When You
Run after cookbook updates to keep cheatsheets current. Use level=“all” for the comprehensive version. Start with format=“txt” for canonical output.
Typical Time
5–15 minutes depending on cookbook size and number of formats.
Difficulty
Intermediate — the recipe handles cookbook parsing, multi-level rendering, drift detection, and multi-format output.

How To Start

This recipe solves the human-discoverability gap. AI personas have CWK-018/019 and the recipe index, but human users need a browseable surface. The cheatsheet is a derived artifact — the source-of-truth is always the cookbook. Run it after cookbook updates or on demand for a refreshed navigable reference.

STEP 1Configure the Generation

Choose the cookbook, detail level, output format, and stale-entry handling mode.
Available parameters
  • cookbook_id · string · required
    Cookbook to generate a cheatsheet for. Options: CORE, COWORK, CWK-ADM-VOL1..VOL8, ADMIN, BRAND-ID, STUDIO, ALL. Legacy ADMIN excluded from ALL unless include_legacy=true.
  • level · string · optional · default: “all” · options: brief | simple | detailed | all
    Detail level. “all” renders all three levels in one file.
  • format · string · optional · default: “txt” · options: txt | md | docx | html | all
    Output format. “txt” is the CRAFT canonical plaintext. “all” produces every format.
  • mode · string · optional · default: “auto” · options: auto | report | both
    Stale-entry handling. “auto” overwrites stale entries. “report” emits drift report only. “both” does both.
  • dry_run · boolean · optional · default: false
    Validate everything but write nothing. Preview to stdout.
  • include_legacy · boolean · optional · default: false
    When cookbook_id=ALL, include legacy ADMIN cookbook. Default false (R-8 gate).
  • force · boolean · optional · default: false
    Regenerate even if source hash unchanged.
  • output_dir · string · optional · default: “cheatsheets/”
    Destination directory for cheatsheet files.
Invocations
Generate Cowork cheatsheet
#H->AI::Directive: (Execute CWK-050 with cookbook_id="COWORK")
All cookbooks, all formats
#H->AI::Directive: (Execute CWK-050 with cookbook_id="ALL", format="all")
Drift report only
#H->AI::Directive: (Execute CWK-050 with cookbook_id="COWORK", mode="report")

Usage Examples

EXAMPLE 1Standard single-cookbook generation

User
Generate a cheatsheet for the Cowork cookbook.
Cat
Cookbook Cheatsheet Generator — cookbook_id: COWORK. Loading and parsing. 48 recipes found. Drift: 3 stale entries. Rendering all levels (Brief/Simple/Detailed). Writing cheatsheets/CFT-FWK-CHEATSH-COWORK.txt. Version: v1.03a. 48 entries rendered, 3 stale revised. Done.

EXAMPLE 2Drift report only

User
Check which cheatsheet entries are stale.
Cat
Cookbook Cheatsheet Generator — mode: report. COWORK cookbook hash changed since v1.02a. Drift: CWK-050 v1.00a → v1.01a (STALE). 1 stale entry, 47 current. Drift report written: cheatsheets/CFT-FWK-CHEATSH-COWORK-DRIFT-REPORT.txt.

EXAMPLE 3All cookbooks, force regeneration

User
Regenerate all cheatsheets from scratch.
Cat
Cookbook Cheatsheet Generator — ALL cookbooks, force=true. Processing 12 active cookbooks. CORE: 22 recipes. COWORK: 48. CWK-ADM-VOL1–VOL8: 58 across 8 volumes. Total: 128 entries, 12 cheatsheet files in cheatsheets/. All rendered fresh. Generation complete.

How AI Reads This Recipe

When this recipe is triggered, the AI generates human-friendly cheatsheets from CRAFT cookbooks. The AI should:
  1. Validate parameters. Verify cookbook_id is valid. If ALL, enumerate active cookbooks via filesystem discovery. Exclude legacy ADMIN unless include_legacy=true. Verify output_dir. Check format=html pipeline availability.
  2. Load source cookbook. Read the cookbook file. Compute sha256. Parse into recipe model (id, title, version, category, status, purpose, quick_reference, body_text). If parse fails, abort this cookbook and continue.
  3. Detect drift. Compare per-recipe versions against existing cheatsheet. Identify stale entries. If source hash unchanged and force=false, short-circuit.
  4. Render entries. For each recipe: emit standard 5-field header. Render Brief (1 sentence), Simple (2–3 sentences), and/or Detailed (1–2 paragraphs) body per selected level. Insert “BODY GENERATION DEFERRED” stub if generation fails.
  5. Write output per mode. Auto: write cheatsheet, overwrite stale. Report: drift report only. Both: write both. Dry-run: suppress all writes.
  6. Render alternate formats. Markdown per template notes. Docx via docx skill. HTML via CWK-ADM-040 pipeline (skip if unavailable).
  7. Version and hash. Compute cheatsheet version (first gen = v1.00a). Embed header block with version, timestamp, source path, sha256, recipe count, generator ID.
  8. Report. Run summary: cookbooks processed, entries rendered, stale entries revised, files produced, failures.

When To Use This Recipe

Use this recipe after any cookbook update to keep human-facing cheatsheets current, on demand when you need a navigable recipe reference, or as part of a documentation refresh. Drift detection means you can run frequently without regenerating unchanged entries.
Do Not Use When
You need the full recipe source (use CWK-018 Recipe Loader). For AI-to-AI recipe lookup (use CWK-019 Cross-Cookbook Scanner). For recipe index management (use CWK-ADM-003 Recipe Indexer).

Recipe FAQ

What’s the difference between Brief, Simple, and Detailed levels?
Brief is a single sentence (“Use this recipe to…”). Simple is 2–3 sentences with a “When to use” one-liner (the default for human users). Detailed is 1–2 paragraphs with When-to-use, Prerequisites, and Related recipes sections. Level “all” renders all three in one file.
How does drift detection work?
The recipe compares per-recipe version strings between the existing cheatsheet and the current cookbook. Stale entries are re-rendered. A sha256 hash of the entire cookbook is also checked — if unchanged and force=false, the recipe short-circuits.
What formats are supported?
Four formats: txt (CRAFT canonical plaintext, always generated first), md (Markdown), docx (via the docx skill), and html (via CWK-ADM-040 pipeline with CRAFTFramework.ai branding). Use format=“all” to produce all four.
Is the cheatsheet the source of truth?
No. The cookbook is always the source of truth. The cheatsheet is a derived artifact regenerated from the cookbook on demand. If there’s a discrepancy, the cookbook wins.
What are orchestrator-class recipes?
Eight recipes (CWK-001, 007, 021, 029, 034, 036, 046, 050) that coordinate other recipes or serve as entry points. At the Detailed level, these get an additional “CRAFT prompt-building guide” section per spec v1.01a I-13.

Version History

v1.01a — 2026-04-08
Revised from v1.00a. Adopts spec v1.01a and template v2 contract: I-4a standard header + I-4b execution block at every level, I-10 field tiering, I-11 CRAFT directive form, I-12 interactive prompts, I-13 orchestrator-class prompt-building guide. Schema-first field order (Option B per OQ-7). Parameterized examples synthesized from parameter schema (OQ-9). Validated at H014.
v1.00a — 2026-04-08
Initial creation at P061-H012. Three detail levels (Brief/Simple/Detailed), four output formats, drift detection with hash-aware short-circuit, ALL-cookbooks mode with legacy gate (R-8).

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