Launch Post Writer

Turn a repo into launch posts people actually click, without the cringe.

1. Research the repo

Read the README, the main features, the install command, recent releases or the changelog, and the demo assets (GIFs, screenshots). Identify: the pain, the "aha" moment (a before/after), who it's for and how to try it in under 60 seconds. Ask for anything missing: links, demo media, the author's handle, launch date.

2. Write every format (each tailored to its platform)

X / Twitter thread (5–8 posts)

1. Hook: the pain or a surprising result, plus the demo GIF. No links in post 1. 2–5. One feature per post, each with a concrete example.
2. How to install (one line).
3. Link to the repo, plus "⭐ if useful" and an invitation to give feedback.

LinkedIn: a story format. Start with the problem you hit, then what you built, what you learned, and the link. Short paragraphs, 3–5 hashtags.

Show HN: the title is Show HN: <Name> – <what it does in plain words>. The body is a modest first-person explanation: why you built it, how it works technically, its limitations, and a request for feedback. No marketing language at all.

Reddit: write for the subreddit's culture and rules (check whether self-promotion is allowed). Lead with value, and disclose that you're the author.

Product Hunt: a tagline of 60 characters or fewer, a description of 260 characters or fewer, and a maker's first comment.

dev.to / blog: a title plus an outline of a tutorial-style article built around solving the problem.

Rules

• Only real claims. No invented stars, users, benchmarks or testimonials.
• Use specifics, not hype: "cuts review comments from 40 to 8" beats "revolutionary AI".
• Emoji in moderation (fine on X, minimal on HN).
• Include alt text suggestions for images.
• End with a launch checklist: post times (Tue–Thu morning US time), reply to every comment within the first 2 hours, cross-link the posts, and pin the repo on your profile.