Hacker Times Pitch
A show HN post drafter app idea: a drafter for Show HN posts that read like builders wrote them. Weekend build with Next.js, Claude API and Tailwind, for indie makers preparing a show hn launch.
Why now
Show HN: what builders shipped this week is full of plain, first-person posts such as Hacker Times and HackerTV that drew hundreds of points. Ask HN threads on what builders are working on show many makers looking for feedback and visibility. From the signals of the week of 9 Nov 2026.
The spec
Paste your repo README and a short demo note, and it drafts a plain Show HN title and first comment in the tone that does well on the front page. It also flags hype words and missing details that commenters usually ask about.
Build time
WeekendBasic logic / CRUD · Level 2 of 5Audience
Indie makers preparing a Show HN launch.
Stack
- Next.js
- Claude API
- Tailwind
Fun factor
You get to see your own launch copy lose its buzzwords in seconds.
Core features
- README import with demo notes field
- Title options under 80 characters
- First comment draft with the why, how and limits
- Hype word and missing detail checklist
AI features
- Rewrites a README into a short first-person first comment that states what it does and what it does not do
- Predicts the three questions HN commenters will most likely ask and drafts answers
Stretch goals
- Save drafts and compare versions
- Check the post against the site's Show HN rules
- Post-launch reply helper for incoming comments
First version
A single page where you paste a README and get three title options and a first comment draft with a hype word check.
Build plan
4 milestones, in the order you would build them. Saved ideas get this plan with checkboxes and notes.
The build prompt
Paste this into ChatGPT, Claude, Codex, or Cursor, then build the first version before anything else.
# Build Hacker Times Pitch You are a senior full-stack engineer pairing with me on a side project. Build a working first version of the product described below. Read the whole brief before writing any code, then follow "How to work" at the end. ## The idea **Hacker Times Pitch.** Paste your repo README and a short demo note, and it drafts a plain Show HN title and first comment in the tone that does well on the front page. It also flags hype words and missing details that commenters usually ask about. **Why now:** Show HN: what builders shipped this week is full of plain, first-person posts such as Hacker Times and HackerTV that drew hundreds of points. Ask HN threads on what builders are working on show many makers looking for feedback and visibility. **Who it is for:** Indie makers preparing a Show HN launch **What makes it fun:** You get to see your own launch copy lose its buzzwords in seconds. ## Scope - **Build time:** Weekend. Size every decision to ship a working first version inside this window. - **Technical ambition:** Level 2 of 5, "Basic logic / CRUD". A few screens over a simple data model with create, read, update, and delete. One lightweight persistence layer, no heavy infrastructure. - **First version only.** Ship the core features below end to end. Stretch goals are listed so you can design around them, not build them. ## Core features (each must work end to end in the first version) 1. README import with demo notes field 2. Title options under 80 characters 3. First comment draft with the why, how and limits 4. Hype word and missing detail checklist ## AI features - Rewrites a README into a short first-person first comment that states what it does and what it does not do - Predicts the three questions HN commenters will most likely ask and drafts answers How to build them: - Put every model call behind one server-side module with a typed interface, so the provider can change without touching the UI. - Read API keys from environment variables only, and document each one in `.env.example`. - Write prompts as versioned constants with clear instructions and an example of the expected output; parse and validate responses before using them. - Handle timeouts, rate limits, and malformed output with a graceful fallback the user can understand. Stream responses where a wait would exceed a couple of seconds. - Never let a feature depend on the model being perfect. Show the result, let the user edit or retry. ## Stretch goals (later, not in the first version) - Save drafts and compare versions - Check the post against the site's Show HN rules - Post-launch reply helper for incoming comments Leave clean seams for these (a module boundary, a nullable column, a feature flag), but do not implement them unless I ask. ## Tech stack Use exactly: Next.js, Claude, Tailwind. Stay on current stable versions, follow each tool's official conventions, and add a library only when the standard library or the chosen stack cannot do the job cleanly. If part of this stack is a poor fit for a specific requirement, say so and propose the smallest change. ## Owner's notes Written by me, the project owner. Treat these as requirements and preferences that override the generated material above when they conflict. The first version should be exactly this, and no bigger: A single page where you paste a README and get three title options and a first comment draft with a hype word check. ## Build plan (with saved progress) 0 of 4 steps complete. Resume at step 1: Build the input form. Before you start it, check what is already implemented so you do not repeat finished work. 1. **Build the input form** [not started] Accept README text, a demo link and one line on who it is for. 2. **Generate title and comment** [not started] Prompt the model for three titles and a first comment in a plain tone. 3. **Add the checklist** [not started] Flag hype words, missing limits and missing demo links. 4. **Add copy and save** [not started] Copy to clipboard and keep drafts in local storage. ## Definition of done for the first version - [ ] README import with demo notes field works end to end, with real data, not a placeholder. - [ ] Title options under 80 characters works end to end, with real data, not a placeholder. - [ ] First comment draft with the why, how and limits works end to end, with real data, not a placeholder. - [ ] Hype word and missing detail checklist works end to end, with real data, not a placeholder. - [ ] Every screen handles loading, empty, and error states. - [ ] Typecheck, lint, and any tests pass, and the main user flow was exercised by hand. - [ ] A README explains setup, environment variables, and how to run it locally. ## Quality bar - Responsive from a phone to a desktop, keyboard-accessible, semantic HTML, visible focus states, labelled inputs, and sensible contrast. - Loading, empty, and error states for every screen that reads or writes data. Errors say what happened and what to do next. - Validate on the server, never trust the client, and keep secrets in environment variables with a committed `.env.example`. - Type-safe end to end. No `any` without a comment explaining why. - Small, readable modules named after what they do. No premature abstraction, no dead code, no TODOs left for later without a note. - Sensible defaults over settings. If a choice is not in this brief, pick the simplest option that keeps the product coherent and say what you chose. ## How to work 1. **Read, then restate.** Summarize the product in three sentences and list your assumptions. Ask only the questions that block implementation. For everything else, decide and note the decision. 2. **Plan before code.** List the files and modules you will create, in build order, mapped to the core features. If a build plan is included above, use it instead: resume at the first step not marked done and check what already exists before touching it. 3. **Set up.** If a project already exists, inspect its code, instructions, and conventions first and build on them. Otherwise scaffold the stack above with linting, formatting, a typecheck script, `.env.example`, and a README stub. 4. **Model the data first.** Define the types, schema, and any migrations before the UI, so the shape of the product is settled early. 5. **Build in vertical slices.** Finish one core feature end to end (data, logic, UI) before starting the next. Keep the app runnable after every slice and commit each slice with a message that says what changed and why. 6. **Then the interface.** Apply the quality bar above to each screen as it lands, not as a final pass. 7. **Verify.** Run typecheck, lint, and tests. Exercise the main user flow by hand. Check each item in the definition of done and each acceptance criterion. 8. **Report.** Tell me what works, what you tested and how, what is not done, every setup step I must complete myself, and the three most useful next steps. Never claim a service, test, or flow was verified when it was not. If you can edit and run the project, start implementing right after the short plan. If you cannot, give me concrete code and the exact commands to run for the next step. Rules: keep the product name and the scope as written, do not invent features, prefer boring and proven choices, and stop to ask me when a decision would be expensive to reverse.
How to use
- Copy the prompt above.
- Open ChatGPT, Claude, or your AI editor and paste it into a new conversation.
- Build milestone one, run it, then move to the next. Add stretch goals only after the first version works.
Want ideas built around you instead? Generate four from your own interests, time, and stack.
FAQ
Frequently asked questions
Answers on what Hacker Times Pitch is, how to build it, and where example ideas come from.
Similar to Hacker Times Pitch
More marketing ideas, then a few from other categories.
Ready to generate yours?
Four ideas per round, shaped by your interests, skill level, and how much time you have.