Workflow cheat sheet

One page for making content. Every part of a piece, the skill that refines it, and the tool behind it. Nothing new lives here: it is the twelve-step workflow and your skills, gathered in one place so making content is a checklist, not a memory test. When this page and a source file disagree, the source file wins.

The three layers

The system is three stacked things. Once this clicks, the rest of the page is just detail.

1. The path. The order things happen in, from 02 Skills/Workflow.md (twelve steps) and docs/creating-content.md (six stages). It never changes.
2. The skills. What Claude runs for you and files in the right place: idea-capture, script-writer, caption-writer, series-page, comment-response.
3. The craft systems. The source of truth each skill reads before writing, in 02 Skills/ (the Hook Engine, the Playbook, Structures, the voice rules). You rarely open these. The skills pull from them so every output obeys them.

The rule going forward: you name the part, Claude runs the skill, the skill reads the craft system. You never start from a blank page.

The map: every part to its skill

How to get a hook

There is no standalone hook skill, and that is on purpose. You get hooks two ways.

• As part of a script. script-writer always hands you at least three hook options at the top, already run through the Hook Engine's four-point test. This is the normal route.
• On its own. Say "give me ten hooks for this idea" and Claude runs the three hook docs directly: Hook Converter turns a rough note into options, Hook Engine pressure-tests each first line, Hook Library holds worked examples and the patterns it will refuse. Use this for a filmed clip that just needs a first line, or to test a hook before committing to a full script.

The everyday flow

The whole thing, the way you would actually run a week.

1. Capture. Drop the raw line: "idea: that rebrand changed nothing but the logo." idea-capture lands it in the inbox with its own page.
2. Shape. Open the Idea Studio, click through problem, intent, pillar, series, structure, format, then copy the hand-off brief.
3. Write. Paste the brief and say "write the script." script-writer files it in docs/scripts/ with the right frontmatter.
4. Surround. "Caption this." caption-writer appends three caption angles under the script.
5. Publish. npm run docs:build, then commit the source and the built site.
6. Record and ship. Batch and film per the Weekend Batch system, edit per the Editing Guidelines.
7. Reply and watch. Comments come in, use "reply to this" or /reply. A piece that pops off can earn a page: "promote this to a series" runs series-page.

The full toolset

Everything you need, in four lists.

Skills (Claude runs these):

• idea-capture, script-writer, caption-writer, series-page, comment-response
• /reply, /reply-improve, /reply-learn for the comment engine

Craft systems (source of truth, in 02 Skills/):

• Hook Engine, Hook Converter, Hook Library
• Structures, Story Structures
• Performance Playbook, Post Image Text Engine, Breakdown Framework
• Weekend Batch, Editing Guidelines
• Comment Response Engine, Comment Voice Bank

Strategy source of truth (in docs/foundation/):

• person.md, the five problems
• job.md, the intents and the weekly recipe
• content-pillars.md, the four lanes
• formats.md, the containers
• series.md, the bar a series clears
• the game plan and the cheatsheet for voice

The brain and the commands:

• PROJECT-INSTRUCTIONS.md governs all content and voice law
• the Idea Studio shapes an idea into a brief
• npm run docs:build publishes, and a git commit saves the source and the built site

Where the full detail lives

This is the quick reference. The full path is 02 Skills/Workflow.md and docs/creating-content.md, the craft is in the 02 Skills/ systems, and the strategy is in docs/foundation/. When a summary here disagrees with one of those, the source wins.