
- Role
- Design + Engineering
- Timeline
- Ongoing · 2026
- Stack
- Next.js 16 · Tailwind 4 · OpenRouter · Zod
Shipping is the easy part. Writing four native launch posts at 11 PM is not.
Every platform has a different reader, a different format, a different etiquette. Copying one blurb everywhere signals that you didn't bother, and platforms penalise it.
Launch Kit solves the last-mile problem of launching: you've built the thing, now you need a Product Hunt tagline, a Show HN post that reads like a real technical intro, a subreddit-appropriate pitch, and an AppSumo deal description. They are four different documents for four different audiences. Launch Kit reads your README once and writes all four, natively, on your machine. Nothing leaves it.

Local-first was the constraint, not the feature.
The folder-analysis route reads files from disk. Shipping that on a public host means the server can be asked to read its own filesystem, so the route is disabled in production builds by default. The decision to run locally wasn't a privacy badge; it was the only safe architecture. As a side effect, there's no database to maintain, no account to create, and no API key to store anywhere but your own machine. The mock generator ships in the box so the full three-step flow works before you've touched an API key.




- Open
- MIT licensed
- 0
- Backend required
- 4
- Platforms, native posts
Launch Kit is a personal tool that escaped into a product. The scope is deliberately narrow: one README in, four launch documents out. The runs dashboard saves every session locally so you can pick up a launch mid-week without regenerating from scratch. The hosted version is gated on a GitHub star milestone, a deliberate choice to make the community the unlock rather than a paywall.