An AI Writes My Daily X Post. Here's the One Rule It Can Never Break

2 min read Tools: Claude Code, Typefully

Contents
  1. Limits
  2. Never in a post
  3. The mix
  4. Voice
  5. What the report looks like

Every weekday at about 18:50 Dhaka time a scheduled Claude Code routine reads my brain repo, writes one X post and one spare, files them in the repo, and schedules the post for 22:00. I have the evening to stop or edit it. Most days I do nothing.

The part worth sharing is the protocol it runs under. The voice rules are mine; the “never” list is what keeps it safe to automate.

Limits

- Use only facts on [stated] or [record] lines in this repo. Never invent a number,
  a user count, revenue, a launch, a customer, a quote or a story.
- Check a product's status in the repo on the day. "Live" only if the repo says live.
  "In review" stays "in review" until the repo says approved.
- Never copy another person's post. The format can be borrowed, the words cannot.
- One post a day. Schedule, never "publish now". Never reply, quote, follow or DM.
- If a post would need a fact the repo does not back, do not schedule it.
  Leave a draft and say why.

Never in a post

- My employer, its products, my colleagues, or anything from my day job
  beyond "I have a full-time engineering job".
- Clients and their projects, by name or by description.
- Money: income, spending, what I put into any business.
- Family, health, religion, politics.

The mix

TypeWhat it isHow often
Build logOne thing I did on my own products in the last few days, and what happenedMost days
How IOne thing I did and how, from my own record. Narrow and practicalWhen the journal is quiet
QuestionOne real question to other builders about something I am working throughAbout once a week
ProductOne of my apps, what it does, for whomAt most one in five
ConnectWho I am, what I build, who I want to meetAt most once a month

Voice

- Mine, cleaned up: plain, short, direct. One idea per sentence.
- First line carries the post. No warm-up.
- 280 characters or fewer unless the story needs more. Line breaks between thoughts.
- At most one emoji. At most one hashtag, usually none. No links unless it is a product post.
- No hype words, no "game changer", no thread bait, no advice I have not lived.
- Honest about small numbers. A small true number beats a big vague claim.

What the report looks like

Each run ends with: whether the post is scheduled and for when, how many free publishes are left this month, the post in full, the spare, and one question for me whose answer would make tomorrow’s post better. One question only. If I answer, the answer gets filed in the journal and tomorrow’s post is better.

The whole thing costs me about five minutes a day, and the account has a voice that is mine on days I have nothing to say.