Write an X Thread
Write an X/Twitter thread where the hook opens a real curiosity gap, every post stands alone, and the payoff matches the promise.
Write an X thread from my raw material below.
What I know / what happened: [THE INSIGHT, RESULT, OR STORY, real specifics: numbers, names of tools, timeframes, the exact mistake]
Why I'm credible on this: [YOUR EXPERIENCE OR RESULT]
Goal: [FOLLOWERS / REPLIES / CLICKS TO A LINK]
Structure:
1. **Hook (post 1)**: this decides ~90% of the thread's reach. It must do three jobs at once: make a specific claim, promise concrete value, and open a loop the thread genuinely closes. Use the strongest number or most surprising fact from my material. No hashtags, no links, no "a thread 🧵" announcement.
2. **Posts 2-7**: one idea per post, each short enough to breathe (aim well under the 280 limit). Every post must work as a standalone screenshot AND pull the reader to the next one. Advance, don't pad: if two posts say the same thing differently, merge them.
3. **Final post**: close the loop the hook opened, land the single takeaway, then ONE CTA matching my goal (follow for X / reply with Y / the link: links only here, never earlier).
Write 3 hook options first, labeled by mechanism: (a) contrarian claim, (b) specific-number result, (c) transformation ("X to Y in Z"). Then write the full thread using the strongest one.
Rules: short lines, concrete nouns, zero throat-clearing. Use only my material, where a claim needs a number I didn't give, write [NEEDS: what] instead of inventing it. The test for the hook: if the thread can't cash the promise, the hook is clickbait. Rewrite the hook, not the facts.How to use
The hook decides almost everything: creators consistently report mediocre threads with great hooks outperforming great threads with generic hooks by 100x. Pick between the three hook options by asking which one your material can actually pay off. 5-10 posts is the sweet spot; if the model gives you 12, cut the two weakest.
More writing prompts
Rewrite the text below in plain language for [AUDIENCE, e.g. "patients with no medical background" / "customers reading a policy update" / "new hires on day one"]. Target reading level: [e.g. "8th grade" / "as simple as the content allows"]. How to rewrite: - Lead with what the reader must DO or what happens to them. Background comes af
Plain Language Rewrite
Rewrite dense policy, legal, medical, or technical text at a target reading level without losing a single obligation or number.
Write a comparison article for the query: [e.g. "Notion vs Obsidian" / "best Mailchimp alternatives"]. Options to compare: [LIST 2-8 OPTIONS] Who is searching this: [READER + WHAT THEY ARE TRYING TO DECIDE] My relationship to these products: [e.g. "I make one of them" / "I use two of them daily" / "none, I am researching"] Facts I can su
Comparison Article
Write an honest X vs Y or best alternatives article: real differentiators, a decision table, and a clear pick for each type of reader.
Build an FAQ page for [PRODUCT/SERVICE/TOPIC]. Real questions people ask me: """ [PASTE SUPPORT TICKETS, SALES CALL NOTES, SEARCH QUERIES, OR COMMENTS. RAW IS FINE.] """ Facts I can state as true: [PRICING, POLICIES, LIMITS, TIMELINES] Do this: 1. **Cluster** the raw questions into distinct questions people actually ask. Merge duplicat
FAQ Page From Real Questions
Turn support tickets and sales objections into an FAQ page that answers in the first sentence and is structured for AI search engines.