Steal this workflow
By the end of this lesson your engine will have a permanent home, a Claude Project with your instructions pasted in, and a weekly rhythm on your calendar: Monday batch, daily publish, Sunday numbers.
Seven concepts is a good Tuesday. An engine is what makes it happen every week, and the difference is not talent; it is a rhythm you stop renegotiating with yourself.
The weekly rhythm
Three fixed appointments. Move the days if life demands it, but never make them a daily decision:
- Monday, 45 minutes: batch. Bring one idea, run the seven-posts prompt, draft the posts one at a time. You leave with the week made.
- Every day, 10 minutes: publish. One post goes out. No creating, no deciding; the work happened Monday. Copy, tweak, post, close the app.
- Sunday, 10 minutes: numbers. Paste your views and comments into the same chat and ask what won. That answer becomes next Monday's idea.
Daily publishing fails when every day is a blank page; it holds when every day is ten minutes of shipping finished work.
Give the engine one home
Right now your niche lives in one chat and your concepts in another; next week you would re-explain yourself from zero. Fix that with a Claude Project: on claude.ai or in the Claude app, open Projects and create one called "Content engine". Projects work on free accounts; every chat started inside one reads your instructions first, so Claude knows your niche and rules without being told again.
Paste this into the project's instructions, filled in:
You are the engine behind my weekly content. One idea in, a publishable week out.
WHO I AM
- Niche: [paste your niche sentence]
- Platform: [your one platform]
- Audience: [who watches, in one line]
HOW WE WORK
- Monday is batch day. I bring ONE idea; you turn it into 7 post concepts using these angles: story, contrarian, how-to, list, mistake, result, question. Then we draft them one at a time, on my go.
- Never invent facts, statistics, or personal stories. Mark story slots [YOUR STORY HERE] and factual claims [VERIFY].
- Give me exactly what I ask for, numbered. No unrequested extras.
- If you need something I have not told you, ask; never assume.
- On Sunday I paste my numbers. Using only what I paste, tell me which post won, which angle it was, and what that suggests for next Monday's idea. If the numbers are too thin to call, say so instead of forcing a pattern.No Projects on your account? Same text, different container: send that block as the first message of one chat and keep the whole week (batch, drafts, numbers) in it.
You should see
Start a new chat inside the project and send: "What are we doing Monday?" The answer should describe batch day in terms of your niche and your platform, without you re-explaining anything.
Check it
- A project (or one dedicated chat) named something like "Content engine" exists and holds the instructions
- The three placeholders are filled with your real niche, platform, and audience
- The test question came back specific to you, not a generic explanation of content batching
- Monday batch, daily publish, and Sunday numbers are real entries in your calendar app, with times
If you see
If the test answer was generic, the instructions are not being read: you probably started the chat from the home screen instead of inside the project. If Monday arrives and you have no idea, that is already handled: ask the engine "give me 5 idea options for this week based on my niche, one line each, no drafts yet", pick one, run the batch.
You now have the whole machine: a niche, the multiplying prompt, a home that remembers you, three appointments. Still missing: a voice, the difference between posts people scroll past and posts that could only be yours. That is module 2.
What you just learned
- The rhythm is three fixed appointments: Monday batch (45 min), daily publish (10 min), Sunday numbers (10 min).
- Daily publishing survives because creation is separated from shipping.
- A Claude Project holds your niche and rules so every chat starts already knowing you; one ongoing chat is the fallback.
- Sunday's numbers feed Monday's idea; the loop closes and the engine runs on its own output.
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
Module 1 recap