ReplyKit
  • How it works
  • Radar
  • Pricing
  • FAQ
Web appAdd to Chrome →

Tweet ideas

See all →
  • April Fools
  • Christmas
  • New Year
  • Valentine's Day
  • Halloween
  • Thanksgiving
  • Black Friday
  • Mother's Day
  • Father's Day
  • Birthday
  • Monday motivation
  • Friday
  • Good morning
  • Weekend
  • Summer
  • Product launch
  • Follower milestone
  • Hiring
  • Build in public
  • Founder
  • Funny
  • Motivational
  • Back to school
  • Earth Day
  • Work from home
  • New Year's resolutions
  • Year in review
  • Winter
  • Cyber Monday
  • New Year's Eve
  • Super Bowl
  • International Women's Day
  • St. Patrick's Day
  • Easter
  • Good night
  • Coffee
  • Gym
  • Relatable

Reply playbooks

See all →
  • SaaS
  • Startups
  • AI
  • Crypto
  • Marketing
  • Coding
  • Design
  • Product management
  • Data science
  • Sales
  • Fitness
  • Nutrition
  • Personal finance
  • Investing
  • Real estate
  • E-commerce
  • Freelancing
  • Content creators
  • Writing
  • Productivity
  • Career
  • Education
  • Gaming
  • Photography
  • Parenting
ReplyKit

Finds the posts worth replying to and drafts three replies in your voice. You post them yourself, always.

Product

  • Chrome Web Store
  • Mobile web app
  • Pricing
  • FAQ
  • Changelog

Resources

  • X reply generator
  • LinkedIn comment generator
  • Reddit reply generator
  • Guides
  • Tweet ideas
  • Reply playbooks
  • Compare
  • Blog

Company

  • Privacy policy
  • contact@replykit.eu
  • @FredericTheTall
  • Built by Frédéric Legrand

© 2026 ReplyKit · Paris

Not affiliated with X, LinkedIn or Reddit

ReplyKit on PeerPushReplyKit - Featured on Startup FameFeatured on Wall of ToolsListed on Beast Launches

Guide · 9 min read

Updated 21 Nov 2026

How to write a good post on X (Twitter), with examples

How to write a good post (tweet) on X: one idea, a first line that stops the scroll, a simple structure, before-and-after rewrites and an editing checklist.

Author

Frédéric Legrand builds ReplyKit on the side of a day job shipping computer-use agents. @FredericTheTall

In this guide

  1. What makes a post good
  2. Start with one idea
  3. The first line decides everything
  4. A simple structure
  5. Before and after: three rewrites
  6. Make it easy to read
  7. A checklist before you post
  8. Mistakes that sink good ideas
  9. Getting better at it

What makes a post good

A good post on X does one job for one reader. It teaches them something, makes them laugh, says what they were thinking, or gives them something to answer. Posts that try to do two jobs at once usually do neither.

So before you write, finish this sentence: after reading this, someone should... Know one thing they did not know. Disagree with you. Try a tool. Tell their own story. If you cannot finish the sentence, you do not have a post yet, you have a topic.

Start with one idea

A standard post has 280 characters, and the good ones rarely need all of them. That is room for one idea and one reason to believe it. The fastest way to improve a weak post is to cut it down to its strongest sentence and build back from there.

Good ideas for posts are usually small and specific. Not "marketing is changing" but the one thing you changed in your onboarding email last week and what happened. Places to find them:

  • Something you did. A result, a mistake, a decision and why you made it.
  • Something you noticed. A pattern in your work that nobody seems to say out loud.
  • Something you disagree with. Common advice in your field that did not hold up for you.
  • Something you keep explaining. The answer you have given three times this month is a post.
  • Something you said in a reply. A reply that got a reaction is a tested idea. Rewrite it as a post.

The first line decides everything

People scroll fast. They read the first line and decide whether to read the second. Put the point there. Do not warm up, do not announce what you are about to say, and do not start with context only you care about.

First lines that work tend to take one of these shapes:

  • The result. "I stopped sending weekly status reports. Nobody noticed for two months."
  • The clear opinion. "Most landing pages do not have a copy problem. They have a too-many-choices problem."
  • The specific observation. "Every bug report that says 'it doesn't work' was written by someone in a hurry, not someone careless."
  • The useful promise. "The three questions I ask before taking on any freelance client:"

These are invented examples. Notice what they share: a reader knows right away what the post is about and has a reason to keep reading. If your first line could sit on top of any post ("Some thoughts on productivity"), rewrite it.

A simple structure

Most good short posts have three parts, and each one can be a single line:

  • The point. Your claim, result or observation, said plainly.
  • The proof. One detail that makes it believable: what you did, what you saw, a real number, a named tool.
  • The turn. What follows from it: the lesson, the exception, or a question the reader can answer.

You do not need all three every time. A sharp observation can stand alone. But when a post feels flat, it is usually missing the proof: it makes a claim and gives no reason to believe it.

Before and after: three rewrites

Three invented drafts, each fixed with one change.

  • Too vague. Before: "Consistency is the key to growing online." After: "I posted every weekday for three months. The posts I almost deleted did better than the ones I polished for an hour." The fix: replace the general truth with what happened to you.
  • Buried point. Before: "So I've been thinking a lot lately about how we run meetings, and after trying a few things I realized that most of them could be shorter." After: "We cut every recurring meeting to 15 minutes. Two of them turned out not to need to exist." The fix: delete the warm-up and open with the result.
  • No room to respond. Before: "Here are my thoughts on remote work. It has pros and cons." After: "Remote work did not make my team less productive. It made bad managers easier to spot. What changed on your team?" The fix: take a side people can agree or argue with, then ask.

Make it easy to read

  • Write the way you talk. If you would not say a sentence out loud to a colleague, rewrite it.
  • Short sentences. One thought per line when the post has more than two sentences.
  • Plain words. A stranger outside your field should understand it in one read.
  • Skip hashtags unless people in your niche really follow one. Most good posts use none.
  • Add an image only when it shows something the words cannot: a chart, a screenshot, a before and after.
  • Put links in a reply under the post, so the post itself keeps people reading.

A checklist before you post

Read the draft once on your phone, then check:

  • Is there exactly one idea?
  • Does the first line make sense to someone who sees nothing else?
  • Is there one specific detail: a name, a number you can stand behind, something that happened?
  • Can you cut the first sentence? The last one? Any word?
  • Would you stop scrolling for it if someone else had written it?
  • Is there something a reader could reply with?

Mistakes that sink good ideas

  • Throat-clearing. "I've been thinking about...", "Unpopular opinion, but...". Start with the opinion.
  • Writing for everyone. A post aimed at one kind of reader gets shared by that reader. A post aimed at everyone gets scrolled past.
  • Borrowed wisdom. General advice anyone could have written. Your own example is the part nobody else has.
  • Engagement bait. "Like if you agree" earns a cheap reaction and teaches readers to ignore you.
  • Sounding like a press release. Buzzwords and polish read as an ad, or as AI. People reply to people.
  • Posting and leaving. The first replies are where a post gets its second wind. Stay and answer them.

Getting better at it

Nobody writes a good post every time. The people who seem to are posting often and paying attention. Once a week, look at which of your posts got replies and profile visits, not only likes, and ask what those posts had in common. Then write more like them.

When an idea needs more than one post, turn it into a thread. And if a blank composer is what stops you, ReplyKit can draft an original post on your topics in your own voice, or tidy a rough draft you wrote, so you start from something you can edit.

Frequently asked questions

How long should a post on X be?

As short as the idea allows. Standard posts can be up to 280 characters, and many good ones use far fewer. If you need more room, a thread or a long post (available to Premium accounts) is better than squeezing.

Should I use hashtags in my posts?

Usually not. Use one only when people in your niche actively follow it, such as an event or a community tag. A row of hashtags makes a post look like an ad.

How often should I post on X?

Often enough to learn what works, at a pace you can keep up. For most people that is one good post a day or a few a week, plus replies on other people's posts.

Is a post the same as a tweet?

Yes. X renamed tweets to posts in 2023, and many people still say tweet. The same advice applies to both words.

Can I use AI to write my posts?

Yes, as a first draft. Give it your own idea and details, then edit until it sounds like you. Posts written entirely by AI on a generic topic tend to read alike, and readers notice.

Read next

  • How to write an X thread people finish
  • How to go viral on X
  • How to make AI replies not sound like AI
  • How to grow on X (Twitter) in 2026: a step-by-step guide
  • Tweet ideas for every occasion

Built by · One person

ReplyKit is a solo project. Tell me what you need.

There is no company behind this, just one developer who reads every message. If ReplyKit does not fit how you work, a feature, a platform, a different style of reply, say so. Requests from users decide what ships next.

Prefer email? contact@replykit.eu

Goes to my phone as a Telegram message, not into a queue.

← All guidesAdd to Chrome, free →