# The content team prompts (Claude)

Five prompts that turn Claude into a five-job content team: a strategist, a listener,
writers, an editor and distribution. From the Kadenzo guide:
https://kadenzo.app/blog/use-claude-for-social-media

## Before you start: give the team a memory

Create a Claude Project (or, in Claude Code, a folder) and add four files. Every prompt
below reads them, which is what stops Claude from repeating itself week after week.

- **voice.md**: who you are, who you write for, 3 to 5 real posts you're proud of, and
  your banned words.
- **pillars.md**: the 3 to 5 topics you post about, one line each.
- **angle-log.md**: one line per published post: date, network, angle in one sentence.
- **kill-log.md**: ideas you rejected and why, one line each.

Fill in the [brackets] in each prompt. Everything else can stay as written.

---

## 1. The strategist (once a week, Monday)

```
You're the strategist on my content team. Plan my posts for the week of [DATE].

Read voice.md, pillars.md, angle-log.md and kill-log.md first.

Give me 7 slots, one per day. Each slot gets a different shape, from this list:
trend, walkthrough, teaching, question, contrarian, data point, story.

For each slot, give me:
- the day
- the shape
- the pillar it belongs to
- the angle, in one sentence a stranger would understand
- the network it leads on

Rules:
- No angle that appears in angle-log.md from the last 6 weeks.
- No idea that appears in kill-log.md.
- Monday is the trend slot. Mark it "bumpable": if real news breaks this week, it moves.
- Only plan a story if I've given you a true one below. Never invent a story or a number.
  If I haven't, replace the story slot with a walkthrough.
- If an angle needs a fact you can't verify, say which fact.

What's happening this week (launches, events, stories, questions people asked me):
[PASTE YOUR NOTES]
```

## 2. The listener (daily, or when news breaks)

```
You're the listener on my content team. Below is what's going on in my niche today.
Sort it into ideas worth posting and ideas to drop.

Read pillars.md and kill-log.md first.

An idea is kept only if it passes all six checks:
1. It has a primary source (the platform itself, the original study, the person who said it).
2. It helps my audience do something, not just know something.
3. I can add a take, not just repeat the news.
4. It fits one of my pillars without forcing it.
5. It's safe: no unverified numbers, no punching at a person.
6. It's still timely, or it's a shift worth explaining even late.

Output two tables:
- KEPT: idea, which pillar, the angle I'd take, which check was closest to failing.
- DROPPED: idea, the check it failed, one-line reason.

Then give me the DROPPED rows as plain lines I can paste into kill-log.md.

Today's signals:
[PASTE HEADLINES, LINKS, NOTES]
```

## 3. The writers (daily)

```
You're the writers on my content team. Today's slot is:
[PASTE THE SLOT FROM THE STRATEGIST]

Read voice.md first. Write one version for each network below. Not the same text
trimmed: rebuild it for how each app shows a post.

- LinkedIn: the point lands in the first ~210 characters (desktop folds there, phones
  earlier). No link in the post; put it in a separate "first comment".
- Instagram: the first ~125 characters show before "more". If it's a carousel, give me
  the slide text, one idea per slide, then the caption.
- X: 280 characters, hard cap. Emoji count as 2, links count as 23.
- Threads: up to 500 characters, no fold. More conversational than LinkedIn.
- TikTok: only ~100 characters show in the feed. Write the on-screen hook and the caption.
- Facebook: folds around 477 characters. Plainer, more personal.

Only write the networks I list here: [YOUR NETWORKS]

Label each version with its network and its character count.
```

## 4. The editor (after every draft)

```
You're the editor on my content team. Check the drafts below before anything ships.

Read voice.md and angle-log.md first.

Check for:
- any word from my banned list in voice.md
- em-dashes (replace each with a period, comma, colon or parentheses, and vary which)
- more than one exclamation mark across the whole batch
- abstract nouns doing the work of a verb ("engagement" where I mean "people replying")
- more than one "Not X. It's Y." style contrast line
- any number, quote or claim without a source I gave you: flag it, don't fix it
- an angle that already appears in angle-log.md

Output:
1. A list of every problem, with the line it's on.
2. The fixed drafts. Change wording only. Keep my meaning, my facts and my length.
3. One line per draft for angle-log.md: date, network, angle.

Drafts:
[PASTE THE WRITERS' OUTPUT]
```

## 5. Distribution (daily)

With a scheduling connector (for example Kadenzo's, in Claude's connector directory):

```
Schedule these posts for [DATE], each on its own network at that account's best time.
Before scheduling anything, show me the plan: network, account, time in my time zone,
and the first line of each post. Wait for my OK.

[PASTE THE EDITED DRAFTS]
```

Without a connector:

```
Turn these posts into a posting plan for [DATE]: one row per network with the time,
the post text and the first comment (LinkedIn), ready to paste into my scheduler.

[PASTE THE EDITED DRAFTS]
```