The whole catalogue

Write 20 opening lines for Threads posts on the topic "{topic}".

Audience: {who}
My role: {who you are to them — practitioner, seller, observer}

Hard limits:
— No line longer than 90 characters. That is what shows in the feed before someone taps "more"; anything past it goes unread if the first part didn't land.
— No "Did you know that", "Top 5 ways", "Here's a roundup" — these read as templates and get scrolled past.
— No caps lock, no emoji chains.

Give 4 groups of 5:
1. Personal experience with a specific number or timeframe.
2. Disagreement with received wisdom in the niche.
3. An observation the reader recognises in themselves.
4. An open question they have something to answer from their own experience.

After each line, in brackets, say what reply it is built for. If the only possible reply is "agreed" — rewrite it: that hook collects likes, not conversation.

Write a Threads post on the topic "{topic}" designed to pull replies.

What I know about it: {your experience, facts, numbers}
Audience: {who}
What I want to hear in the replies: {e.g. how other people solve this}

Rules:
— No longer than 500 characters, that is the platform limit. 300 is better.
— The first 90 characters must work as a standalone hook; the rest is what people unfold themselves.
— End on a question the reader already has an answer to from their own experience. Not "what do you think?" but something specific: their case, their number, their choice.
— Leave a place in the text where the reader can disagree. A post everyone agrees with gives nobody anything to say.

Don't do this:
— "Tell me in the comments!" — a direct ask works worse than a question people simply have something to say to.
— Don't invent provocation for the sake of an argument. A fight collects replies once, and then people unfollow.

Give 3 versions of the post and, under each, what kind of reply it is most likely to collect.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Help me put a strong opinion into a Threads post.

Topic: {what about}
What I actually think: {your position, a rough draft is fine}
What it's based on: {experience, numbers, cases}

I want a post some readers will disagree with — and want to explain why. But not at the cost of my reputation.

Do this:
1. State my position in one sentence under 90 characters, so it is clear exactly what there is to argue with.
2. Assemble a post under 500 characters: the position, one piece of grounding from my own experience, and an admission of where I am wrong. That last part is mandatory — an opinion with no stated limits reads as posturing.
3. Write the three strongest objections that will come, and an honest answer to each.
4. Check the resulting post against this list and give a verdict on every point:
   — Would I repeat this under my own name a year from now?
   — Is this an argument about the work, or a swipe at people?
   — Do I have grounds beyond irritation?
   — If someone else had written this, would I reply on the merits or scroll past?

If even one point fails, say so plainly and suggest how to reframe it.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Put together my Threads profile: bio and pinned post.

What I do: {occupation}
What I'll be writing about: {2–3 topics}
Who for: {audience}
How I differ from others in this niche: {experience, numbers, point of view}
What someone gets by following: {specifically}

People arrive at the profile from the recommendation feed and decide in a couple of seconds. The bio is 150 characters, and that is all you get.

Give me:
1. Five bio options under 150 characters. Each must make clear what the profile is about and why you specifically. No "coffee and travel lover", no list of credentials.
2. For each option — who it suits and who it doesn't.
3. A pinned post under 500 characters: who you are, what will be here, and one example of your usefulness inside the text itself — not a promise, but something useful right away.
4. Three topics for the first posts that will make good on the bio's promise. If the bio promises breakdowns and the first posts are about breakfast, people unfollow.

Separately, tell me if my answers don't show any difference from a hundred similar profiles — and what to put up front in that case.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a Threads author. Break a story into a chain of posts.

What happened: {the episode in your own words}
How it ended: {the outcome}
What follows from it for the reader: {the value}
How many posts: {usually 4–7}

Deliver:
1. The first post is a scene, not an introduction: a specific moment, time and place. No "let me tell you a story".
2. One turn per post, each ending with a reason to read on.
3. The moment it went wrong — without it the story does not work.
4. The last post is a conclusion that applies to the reader, not a moral about yourself.
5. Three options for the first post.
6. What to cut if the story runs longer than six posts.

First-post test: if it could sit on top of someone else's story, it is weak.

You are a Threads author. Build a text carousel.

Topic: {what about}
Main claim: {what you want to prove}
For whom: {audience}
Number of posts: {5–8}

Requirements:
1. The first post is the claim itself: short and arguable, but honest.
2. Each following post is one argument or example, no longer than three lines.
3. No post that could be skipped without loss.
4. The second to last is an objection against yourself, with the answer.
5. The last is what the reader should do about it today.
6. Three versions of the first post at different sharpness: soft, medium, sharp.

The self-objection is mandatory: a chain where the author doubts nothing reads as an advert.

You are a Threads author. Come up with question posts.

Account topic: {what you write about}
Audience: {who reads}
What you want to learn: {if you have a goal}

Give ten questions in three groups:
1. Experience questions — people answer because they have something to tell.
2. Either-or questions — answered in one word, low barrier.
3. Confession questions — answered because everyone has done it.

For each:
4. The question itself, up to two lines.
5. Your own answer as the first reply — without it, answering feels awkward.
6. A note on what answers you will get and what to do with them afterwards.

Separately: three questions nobody will answer, and why — too general, too personal, or too much work.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are a Threads growth strategist. Explain how to comment.

Your topic: {what you are about}
Whom to comment under: {types of accounts}
Your experience: {what you can usefully add}

Deliver:
1. Five kinds of comment that work: an addition, a counter-example, careful disagreement, a question of substance, a short story.
2. For each, a two-to-three-line sample on your topic.
3. What does not work: empty agreement, emoji, "great post", self-promotion.
4. How to write disagreement so it reads as conversation rather than argument.
5. How many comments a day make sense and why more is worse.
6. How to tell in two weeks that it is working: two signs.

A comment must be useful to the readers of the post, not to its author: only then do people follow it to your profile.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You do social strategy. Pick profile topics for Threads.

What you write about: {topics over the last month}
Who you write for: {audience}
What you sell or do: {if anything}
What the profile says now: {as it is}

Deliver:
1. Three to five topics you should be found under. Not what interests you, but what strangers will look for you under.
2. How each topic overlaps with what you actually post. A topic with no posts works against you: arrivals leave.
3. What to remove: the too broad ("marketing") and the too narrow that nobody searches.
4. How this fits the first line of the bio. Topic and bio must agree, or the profile reads as somebody else's.
5. Three opening posts per topic, so an arrival sees this place is about that.
6. When to check and what to look at: the share of non-followers in your reach.

Topics are not hashtags. They are a claim about which feed you belong in, and the claim is backed by posts, not words.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You write on Threads. Adapt a trending format to your subject.

The format: {describe it — city lists, five jobs, unpopular opinion, whatever}
Your subject: {what you write about}
Audience: {who reads}
Your last month of posts: {examples}

Deliver:
1. What works mechanically in the format: enumeration, recognition, disagreement, nostalgia. Copy the mechanism, not the words.
2. Three versions for your subject. Each must stay yours: if the format would fit any account, it adds nothing to yours.
3. What to drop in the transfer: whatever was funny only in the original.
4. The first line of each version. The feed shows that and half of the second.
5. What to reply in the comments so the discussion continues. For list formats this is the main thing: people come to add their own.
6. When not to take the format: if your subject offers no recognition, an enumeration reads as a list.

Do not take a format after day seven. By then the feed is tired of it and your post reads as an echo.

You write short. Build a list post.

Subject: {what about}
What you enumerate: {mistakes, tools, rules, observations}
How many items: {number}
Audience: {who reads}

Build:
1. A headline with a number and a promise. The number sets the length — the reader knows what they are getting into.
2. One line per item. Two sentences per item turns it into an article, and articles do not get read in a feed.
3. Order: the most surprising first, the most useful second. The last item is remembered, but they have to reach it.
4. One item worth arguing with. Without it there are no comments.
5. A last line inviting additions: "what would you add". A list without one ends rather than continues.
6. What to cut: items everyone has, and items you have not tried yourself.

Five to seven items. Ten does not get finished; three looks like a draft of something larger.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You edit social. Build a post with an image.

What the post says: {the substance}
The image: {screenshot, photo, chart, cover}
Audience: {who reads}

Deliver:
1. Whether an image belongs here at all. On Threads text works on its own, and a spare image pulls attention off the first line — say plainly if it is better without.
2. What must be visible in the preview. Feed images are small: small type on them is never read.
3. How text and image connect: the text does not narrate the picture, it adds what is not in it.
4. Screenshots: what to crop and what to redact. Personal data, other people's names, spare interface.
5. Charts: one idea, axes labelled in words, one highlighted point. A chart with no conclusion in the caption goes unread.
6. The first line of the post — it still decides. An image will not save a weak first line, and a strong one works without an image.

Do not add a picture "so people notice". They will notice and scroll: the feed has too many images and too few reasons to stop.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You write on Threads. Run a question round.

Subject: {what you cover}
Followers: {number}
What has been asked in comments: {examples}
How many you will answer: {number}

Deliver:
1. How to invite questions. Not "ask me anything" — a narrow frame produces more questions than a wide one. People do not know what to ask an open door.
2. What to do with few followers: where else to get questions — a month of comments, your inbox, search on your subject.
3. How to select: questions interesting to more than the asker. Answer the rest privately.
4. Answer format: one post per question, not a ten-part thread. Each answer lives its own life in the feed.
5. What a good answer looks like: the question on line one, the answer on line two, detail after.
6. What to do with an awkward question: answer plainly or say you will not — but do not ignore it in public.
7. How this becomes a week of posts, and what to do with questions that return every month.

A repeating question is not boredom, it is a signal: the answer exists nowhere. That answer belongs pinned.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You are an editor. Decide whether a text is one post or a thread.

The text: {paste}
Subject: {what it is}
What the reader should take away: {one thought}

Work through:
1. How many thoughts are in it. One thought is one post, always. A thread caused by length rather than by count reads as padded.
2. If there are several: are they sequential. A thread works when point two makes no sense without point one. If the points are independent, that is a list in one post.
3. How to compress to one screen: what to cut. Usually the preamble, the repetitions, and explaining what was already clear.
4. If a thread is warranted: how to build the first post. It must work alone — most people read only that.
5. How to end each node so people continue.
6. The maximum number of nodes. After the fifth almost nobody follows, and a second thread the next day works better.
7. What a thread costs: discussion smears across the nodes and the comments stay empty.

The default is one post. A thread has to be justified, not chosen by habit.

You are an editor. Prepare a repost of old material.

Best posts: {paste several}
How long ago: {timeframe}
Followers then and now: {numbers}
What has changed since: {in the subject, for you}

Deliver:
1. Which posts are worth repeating: those whose idea has not aged while the audience grew. A post everyone saw is not worth repeating.
2. What to change first: a new opening line, always. The same run-up over the same text is recognised and scrolled past.
3. Three ways to repost: with a new occasion, with a correction, with an admission. The last works best: "a year ago I wrote this, now I think otherwise".
4. What to do with numbers and examples: outdated ones must be refreshed, or the repost reads as carelessness.
5. How long to wait. Under three months is too soon.
6. How many such posts to keep in reserve and how to pick them without trawling the archive by hand.
7. What not to do: repost verbatim, repost more than monthly, repost what caused a fight.

A good repost is not a copy but a continuation. It adds what you did not know a year ago.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.

You analyse social. Diagnose a drop in reach.

Before and after: {numbers over two or three weeks}
What you posted those days: {topics and formats}
What you did differently: {if anything}
Followers: {number}

Check in order:
1. How many days the drop has lasted. Two days is not a drop, it is two days. Reacting before a week means fixing something that is not there.
2. What changed on your side: posted less often, stopped replying, changed subject, started adding links.
3. Outbound links: almost everywhere they suppress reach. Check whether the start coincides with their appearance.
4. Format: whether you drifted into one type of post. Feeds tire of sameness faster than of bad.
5. The calendar: holidays, summer, major events. They move numbers more than your work does.
6. What to do this week: one change, not five. With five you will not know which worked.
7. What not to do: delete posts, double your posting rate, buy anything, change subject.

A two or three week dip is normal, not a fault. The problem starts when it lasts a month with your work unchanged.

Role: {specialist}, {years} years in {niche}.
Task: prepare {deliverable} for {audience}.

Context:
— channel: {channel}
— goal: {goal}
— constraints: {constraints}

Answer format:
1. {first block}
2. {second block}
3. {third block}

Tone: {tone}. Length: {length}.