Threads die between tweet 1 and tweet 2. The hook either earns the next scroll or it doesn’t, and “interesting” isn’t enough — readers need the “wait, I have to see what’s next” feeling. These prompts force the through-line, then handle hook variants, recap arcs, contrarian takes, and the thread-to-blog conversion. For the full thread craft walk-through see AI X (Twitter) Thread Writing.
Best for
- Builders / founders on X
- Career / industry takes
- Niche-deep technical threads
- Recap threads after a project or experiment
- Newsletter writers cross-posting to X
- Thought-leadership accounts building inbound
1. 8-tweet thread skeleton
Topic: {topic}. My angle / claim: {one line}. Write a thread outline:
- Tweet 1 (hook): ≤220 chars, must contain a specific number or a contrarian phrase, ends with a reason to scroll
- Tweets 2-7 (each one beat): one idea per tweet, each ends with a 5-word setup for the next
- Tweet 8 (payoff + CTA): names the thing the reader should do or save
Output as a numbered list with character counts.2. Hook tweet only — 10 variants
For a thread about {topic}, write 10 hook tweet candidates ≤280 chars. Use a mix of these patterns, one per tweet:
- Contrarian claim
- Specific number ("I tested 47 of these")
- Personal admission ("I wasted 6 months doing this wrong")
- List promise ("12 things I learned shipping X")
- Scene-setting opener
- "Most people think X. Actually..."
- Single dramatic line
- Question with implied answer
- Stat that reframes the topic
- Direct address ("If you're a [role], read this")3. Recap thread of a 30-day project
I did {project} for 30 days. Write an 8-tweet recap thread:
- Hook with the most surprising data point
- What I tried (1 tweet)
- What worked (1 tweet, with metric)
- What didn't (1 tweet, with reason)
- Biggest surprise (1 tweet, with detail)
- What I'd do differently (1 tweet, opinion not hedge)
- Next experiment (1 tweet)
- CTA: link, repo, follow-for-update
Each tweet ≤270 chars. No emoji except where signal.4. Educational thread (how-to)
Teach {skill} in an 8-tweet thread:
- Tweet 1 hook: name the failure mode this skill prevents
- Tweets 2-7: each one micro-step, with a concrete example or screenshot suggestion
- Tweet 8: "save this thread, here's the order to do them in tomorrow"
Each tweet must stand on its own (readers screenshot mid-thread) AND pull forward.5. Contrarian-take thread
My take: {opinion}. Write a 7-tweet thread defending it:
- Tweet 1: lead with the claim, no hedging
- Tweets 2-5: 4 evidence tweets, each a different type (data, lived experience, second-order effect, counter to a common counter)
- Tweet 6: honest concession — name the strongest objection
- Tweet 7: decisive close that still owns the take
No "what do you think? let me know" ending.6. Story-arc thread
Story: {what happened — paste 2-3 sentence summary}. Write a 6-tweet narrative thread:
- Hook with the dramatic moment (in media res, not setup)
- Tweet 2: flashback to context (just enough)
- Tweets 3-5: chronological beats, each ends on tension
- Tweet 6: the principle I extracted (not the moral, the takeaway someone can use Monday)
Use specific sensory detail in at least 2 tweets.7. Curation thread
5 underrated {things} in {field}. Write a 7-tweet curation thread:
- Tweet 1 intro: why most lists in this field are bad
- Tweets 2-6: one item per tweet — name, link, one-line why it's underrated, one-line who it's for
- Tweet 7: my pick of the 5 + the reason, plus what I'd add if I had to extend
Each item tweet ≤220 chars to leave room for retweet commentary.8. Thread → blog conversion
Below is my best-performing thread. Convert into a 700-word blog post that:
- Restores context Twitter forced me to cut
- Adds a short intro that names who this is for
- Keeps the original hook as the H1 or opening line
- Expands each tweet into a section with its own subhead
- Ends with a CTA different from the thread's CTA (newsletter vs follow)
Preserve voice. Don't soften the takes.
{paste thread}9. Reply-as-thread hook
Below is a viral tweet I want to add to (not dunk on). Write a 5-tweet reply-thread that:
- Tweet 1: agrees with the premise but takes it one level deeper
- Tweet 2-4: my added angle, with one concrete example each
- Tweet 5: credit / tag the original author + my one-line stance
Keep ego out of tweet 1. The reply isn't about me yet.
{paste original tweet}10. Numbered listicle thread
{N} {things} for {audience}. Write a thread:
- Tweet 1: the list promise + a one-line credibility marker (why I'd know)
- Tweets 2-(N+1): one item per tweet, each containing: title, 1 sentence why, 1 sentence how to apply this week
- Final tweet: which item is the highest-leverage one if they only do one
Each tweet self-contained for screenshotting.11. Thread that earns saves
Topic: {topic}. Write a 6-tweet thread engineered for saves (not retweets). That means:
- Each tweet contains a referenceable artifact (template, list, framework, rule of thumb)
- Final tweet explicitly says "screenshot tweet 3 if you only save one"
- No quote-tweet-bait one-liners
- Information density beats personality
Output the thread + a one-line note on which tweet I should pin.12. Thread post-mortem
Below is a thread that underperformed. Diagnose specifically:
- Was the hook the problem? (rewrite it 3 ways)
- Did tweet 2 deliver on tweet 1's promise?
- Where did the reader most likely drop off?
- Is the CTA aligned with the thread's content?
- Posting time / day a likely factor?
Give me a rewrite plan, not generic advice.
{paste thread + engagement numbers if known}Common mistakes
- Hook that takes 280 chars to set up — leads with backstory instead of the claim
- No through-line — each tweet stands alone but doesn’t pull forward
- CTA mismatch (long technical thread that ends “follow for memes”)
- Padding mid-thread with filler tweets that don’t add a new beat
- Engagement-bait closer (“what do you think? comment below”) that signals low effort
Related
- Personal brand prompts
- Viral opening line prompts
- AI X (Twitter) Thread Writing: Hook, Arc, and Payoff
Tags: #Prompt #Social media #X thread