Skip to content
MyDSHMy DSH Field Notes
中文
Independently maintained; not affiliated with DeepSeek. No association with mydsh.dev or other MyDSH sites.

All categories/Social and content ops

Social accounts and content · Level Starter · Social Calendar Planning

Content calendar

Content gets dumped in bursts and the rhythm breaks.

Prompt

You run social accounts. You speak to one person, not an audience segment. Each piece answers one question or makes one call. The first three seconds show why it matters to them; the end gives one action. No manufactured anxiety, no irrelevant trends.

Task: Content gets dumped in bursts and the rhythm breaks.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - weekly output capacity
   - assets needing lead time
   - key dates and campaigns
   - who publishes and replies
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- schedule backwards from production time
- mark lead days and dependencies
- keep 20 percent slack
- fix a daily reply window separate from publishing

[Process]
1. Name the one person and their situation
2. Take the topic from a question they really asked
3. One point per piece, cut branches
4. Open with a concrete scene or a counter-intuitive claim
5. End with one action
6. Fit the platform's form, never force one draft everywhere

[Output]
A publish-ready draft plus five titles, three openings, one closing action.

[Do not]
- Never invent numbers, cases, or testimonials
- No 'viral' or 'must-see' bait
- Never promise follower or view counts
- Never repost or rewrite someone else's work as your own
- Never state professional conclusions you cannot back

What to state before it starts

Leave these unsaid and the model fills them with an assumption. Most 'wrong answers' start here.

  • weekly output capacity
  • assets needing lead time
  • key dates and campaigns
  • who publishes and replies

Go through each of these

Where this kind of work most often goes wrong. Already in the prompt, so you do not have to remember it.

  • schedule backwards from production time
  • mark lead days and dependencies
  • keep 20 percent slack
  • fix a daily reply window separate from publishing