Cindy Zhu.
Free guides
Marketing & content Claude

The daily posting system: Notion idea bank + Claude setup

Hey, it's Cindy ๐ŸŒฑ You commented SYSTEM, so here is the whole thing: the Notion idea bank (every property and view, so you can build it in about ten minutes).
btw the waitlist for AI System Club is now open! If you're keen on using AI to automate your content, video editing, job search, business or build AI agents, feel free to sign up (only if you want to hehe). Ps. the waitlist gets first dibs:)
the shape of it

Four pieces, one loop

Every piece has one job, and each one hands off to the next. If posting feels impossible right now, it is almost always because one of these four is missing and you are doing that part manually, from scratch, on the day.

1. Capture One home for every idea. A screenshot, a comment, a shower thought, all landing in a single Notion database you can search later.
2. Draft One Claude project loaded with your voice, your audience and your hook formulas, so drafting stops starting from a blank page.
3. Batch One sitting where ten ideas become ten scripts. Task switching is the thing that actually drains you, not the writing.
4. Schedule A week queued in advance in a free scheduler, so publishing happens whether or not you feel like it that morning.

piece one

Build the idea bank in Notion

The point of the idea bank is not tidiness, it is that batch day has something to pull from. Ten half-formed ideas in one place beat one perfect idea you cannot find. Build it once with these exact fields.

  1. ๐Ÿง  Create the database. In Notion, open a new page, type /database and pick Table view. Name it Idea bank. Full walkthrough in Notion's create a database help page.
  2. ๐Ÿ’ก Add these properties. Keep the names exactly as below so the Claude prompts later line up with them. Property types are explained in Notion's database properties guide.
  3. ๐ŸŒฑ Add four views. Views are the difference between a dumping ground and a system. Set them up with filters and sorts, described below.
  4. ๐Ÿ‘ฉโ€๐Ÿ’ป Put it on your phone home screen. Open the database in the Notion mobile app, tap the three dots, and add it to your home screen. Capture only works if it takes under ten seconds.

The properties to create:

  • Idea (title). One line, written as the thing you would actually say out loud, not a topic. "Nobody tells you the first 3 seconds are the whole video" beats "hooks".
  • Status (select): Raw, Ready to draft, Drafted, Filmed, Posted. Five options, no more.
  • Pillar (select): your three to five content buckets. Mine are along the lines of AI at work, making money with AI, and building in public.
  • Format (select): Reel, Carousel, Text post, Long form.
  • Hook angle (select): Contrarian, How to, Listicle, Story, Reaction. This is the field that stops every post sounding identical.
  • Source (URL). Where the idea came from: the reel you saved, the article, the comment thread. Future you will want it.
  • Spark (text). Two or three sentences on why this is interesting. Without this, half your raw ideas are unreadable a month later.
  • Score (number, 1 to 5). How strongly you believe in it. Filled in on batch day, not at capture.
  • Created (created time). Automatic. Useful for spotting ideas that have been sitting for months.

The four views:

Inbox Table view, filtered to Status is Raw, sorted by Created descending. This is the only view you see when capturing on your phone.
Batch queue Table view, filtered to Status is Ready to draft, sorted by Score descending. This is the list you open on batch day, and nothing else.
By pillar Board view grouped by Pillar. One glance tells you which bucket you have starved this month, which is usually the reason your feed feels lopsided.
Posted archive Table view, filtered to Status is Posted. Your own swipe file. When something performs, you already have the idea, hook angle and source in one row.
๐Ÿ’ก Capture rule that makes this work: when you save something on Instagram or read something good, add the row immediately with Status Raw and one line in Spark. Sorting, scoring and pillar tagging happen later, in one pass, on batch day. Deciding at capture time is what kills the habit.

piece two

The Claude project that drafts in your voice

A project in Claude is a workspace with its own instructions and its own knowledge base, so it starts every chat already knowing who you are and who you are talking to. Projects are available on every plan, and free accounts can create up to five of them (Claude help centre, what are projects). One is all you need here.

  1. ๐ŸŒฑ Create the project. In Claude, open Projects in the left sidebar, choose New project, and name it Content engine.
  2. ๐Ÿ’ก Paste the project instructions. Open the project, find Instructions, and paste the block below. These load into every chat you start inside the project.
  3. ๐Ÿง  Add three knowledge files. Add them to the project knowledge as text or uploaded files: voice.md, audience.md and hook-formulas.md. What goes in each one is spelled out below.
  4. ๐Ÿ‘ฉโ€๐Ÿ’ป Feed it real examples. Paste in five to ten of your own posts, captions or voice notes and ask Claude to update voice.md from them. Your actual writing teaches it more than any description of your tone.
๐Ÿง  project instructions, paste into Claude
You are my content writing partner for short-form video and social posts. You always write in my voice, using the voice, audience and hook-formula files in this project's knowledge as your source of truth, and you re-read them before drafting anything.

House rules, every time: write in sentence case, never use em dashes, never open with "in today's world" or "let's dive in", and never explain a concept the audience already knows. Assume they know the basics and are here for the layer underneath. Keep sentences short enough to say out loud in one breath, because most of this gets read to camera.

When I give you an idea, do not draft immediately. First tell me the single clearest promise the post is making, name which hook formula fits it best, and ask me at most two questions if something material is missing. Then draft. Every script needs a hook line that works with the sound off, one concrete example or number, and a close that names one specific action.

Always give me the draft as plain text with no headings or bullet points unless I ask, because I read it off a screen while filming. Flag anything you are unsure is true rather than smoothing over it, and tell me when an idea is too thin to be worth filming instead of writing it anyway.

What goes in each knowledge file. Write these once, spend twenty minutes on them, and every draft after that gets better:

  • voice.md: five things you always do and five you never do, your typical sentence length, the words you actually use, three phrases that sound nothing like you, and two or three full posts of yours pasted in as reference.
  • audience.md: who they are, what they already know, the five problems they have in their own words, what they have already tried that did not work, and what they secretly want the outcome to prove about them.
  • hook-formulas.md: your six to eight repeatable openers with one real example of each. Contrarian ("you do not need X, you need Y"), how to with the outcome named, numbered listicle, the mistake, the before and after, the thing nobody tells you, and the question you get asked constantly.
๐ŸŒฑ If you have never written a voice document, do not start from a blank page. Paste ten of your own posts into Claude and ask it to write voice.md for you, describing your patterns back to you. Then edit the parts it got wrong. That edit pass is where the file becomes accurate.

piece three

Batch day: ten ideas, one sitting

Batching is the piece people skip, and it is the one that makes the whole system survivable. One session per week, ninety minutes, same time every week. Open the Batch queue view, take the top ten, and run them through the project in a single thread so context builds instead of resetting.

  1. ๐Ÿง  Score and promote first (10 minutes). Go through the Inbox view, give each row a Score, tag its Pillar and Hook angle, and flip the good ones to Ready to draft. Delete anything you would not defend. This pass is fast because you are only judging, not writing.
  2. ๐Ÿ’ก Draft ten in one thread (45 minutes). Paste the batch prompt below with your ten ideas. Working in one thread means Claude can see the previous nine and stop repeating the same structure.
  3. ๐Ÿ‘ฉโ€๐Ÿ’ป Read every draft out loud (20 minutes). Anything you stumble over gets rewritten by you, not by Claude. This is the step that keeps it sounding like a person.
  4. ๐ŸŒฑ Update the rows (5 minutes). Paste each finished script into its Notion row and set Status to Drafted. Batch day ends with ten rows ready to film, not ten open tabs.
๐Ÿ’ก the batch prompt
Here are 10 ideas from my idea bank. For each one I am pasting the idea line, the pillar, the hook angle I want, and my spark note explaining why it is interesting.

Work through them one at a time in this same thread, and before each draft show me the promise of the post in one sentence so I can stop you early if it is off. Draft each as a 45 to 60 second spoken script, roughly 130 to 160 words, using my voice file. Every script needs: a first line that lands the promise in under three seconds and makes sense with the sound off, one specific example, number or named tool rather than a general claim, and a closing line that names one action.

Keep the ten deliberately different from each other. Vary the structure, do not open two scripts the same way, and do not reuse the same example twice across the batch. If an idea is too thin to carry a whole script, say so and tell me what extra detail or proof would make it work, instead of padding it.

After all ten, give me a short list: which two you think are strongest and why, and which one I should film first.
๐Ÿ’ก The failure mode to watch for: accepting all ten drafts as written. Claude is drafting from your files, not from your week, so the specific detail that makes a post yours is the part you add. Budget your editing energy for the first line and the example, and let the middle be close enough.

piece four

Queue a week ahead, for free

The last piece removes you from the publishing moment entirely. Both of these have real free plans, with real limits worth knowing before you pick.

Metricool free One brand, up to 20 scheduled posts a month, 30 days of analytics, and five competitor profiles you can track. The free plan covers your networks apart from LinkedIn and X. Best pick if you want scheduling and analytics in one place.
Buffer free Up to three channels, 10 scheduled posts per channel with the slots refilling as posts go out, a visual calendar and 30 days of basic insights. Best pick if you post across three platforms and mostly want a clean queue.
  1. ๐ŸŒฑ Connect one platform first. Start with the platform you actually post on most. Adding four at once is how the queue ends up half empty and ignored.
  2. ๐Ÿ’ก Set fixed slots, not custom times. Pick the same two or three slots every day and load into them. Choosing a time per post is a small decision that quietly stops you posting.
  3. ๐Ÿ‘ฉโ€๐Ÿ’ป Load a full week on batch day. Queue the week straight after your editing pass, while the captions are still fresh in your head.
  4. ๐Ÿง  Use reminder posting where you have to. Some formats cannot be auto-published by any third-party tool, so the scheduler pings your phone at the slot and you tap post. Still worth it: the decision was already made.

the week, in practice

What this actually looks like

Every day, 10 seconds Capture whatever you notice into the idea bank as Raw. No sorting, no judging, no writing.
Batch day, 90 minutes Score, promote, draft ten in the Claude project, read them out loud, update the rows.
Film day, 60 minutes Film the drafted rows back to back. Same lighting, same setup, one sitting.
Queue day, 20 minutes Edit, caption, load the week into the scheduler, set the rows to Posted as they go out.
๐ŸŒฑ Build it in this order, one piece a week: idea bank first, then the Claude project, then your first batch day, then the scheduler. All four at once is a project. One a week is a habit, and by week four you are posting daily without deciding to.
the waitlist is now open

AI System Club is launching soon

Build AI systems with me through recorded lessons you can follow at your own pace. Join the waitlist for first access and the founding price.

btw this list gets first dibs
the moment doors open :)