Module 1 recap
Two minutes to lock in the module: what your engine now is, and what gets built onto it next.
You started this module as someone who posts when inspiration shows up. You are ending it with a machine that does not need inspiration.
You know why the machine exists: consistent beats viral, because platforms reward reliability and ten weeks of posts produce a pattern you can learn from, where a lucky post is only a spike. You know its five stages: idea, formats, batch, publish, read numbers.
You made three things that persist. A niche sentence ("I make [topic] content for [audience] on [platform]") that feeds every prompt. A seven-angle week: story, contrarian, how-to, list, mistake, result, question, all grown from one idea in one prompt on free claude.ai. And a home: a Claude Project carrying your instructions, with Monday batch, daily publish, and Sunday numbers in your calendar.
Where this goes next
- Module 2, a voice that is yours. Right now the drafts sound like Claude. You will build a voice file from your own real writing, so every draft sounds like you on your best day.
- Module 3, batch day. The full Monday session: hooks that stop the scroll, sixty-second scripts, captions that carry.
- Modules 4 and 5 put a phone camera on the scripts and teach you to read Sunday's numbers without the dashboard trance.
What you just learned
- An engine is a loop, not a burst: idea, formats, batch, publish, read numbers, repeat weekly.
- One idea becomes seven posts through seven angles; the input problem is smaller than it looks.
- Guardrailed prompts (exact counts, [YOUR STORY HERE], ask before assuming) keep output usable.
- The rhythm is fixed appointments, and the Sunday reading feeds Monday's idea.
practice
Open Claude Cowork on your own computer and try this on real files. Each module ends with a checkpoint where you submit what you made.
Open in ClaudeNext
Find your voice