Product hunt launch skill

When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes).

by kostja94·MIT license·★ 1,006 Stars on the repo·GitHub ↗

Use now

Files of Product hunt launch

kostja94/main1 file shown
SKILL.md
Show the full text91 lines

Channels: Product Hunt Launch

Guides preparing and executing a Product Hunt launch. Product Hunt is a community-driven product discovery platform; only ~10% of submissions get featured on the homepage. Best for SaaS, developer tools, AI/ML products, and productivity software. Physical products and service businesses have limited success.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

Identify:

  1. Product type: SaaS, AI tool, app, Chrome extension
  2. Launch readiness: Landing page, screenshots, tagline, first comment
  3. Hunter: Self-hunt or Top Hunter (optional but helps)

30-Day Preparation Plan

Phase Days Actions
Teaser 30–21 Build "notify me" page; decide self-hunt vs hunter; engage in community
Supporters 20–11 Build list of 200+ (makers, industry contacts, followers, users)
Assets 10–3 Finalize tagline (≤60 chars), gallery images (1270×760), demo video (<2 min), maker comment, 3–5 topic tags; build awareness on X/LinkedIn 2–4 weeks before
Launch day 2–1 Clear calendar for 16+ hours; Product Hunt runs midnight–midnight Pacific

Product Hunt Fields

Field Spec
Tagline ≤60 chars; no emojis unless part of product name; catchy, benefit-focused
Gallery 1270×760 px recommended; readable, show product value
Demo video <2 minutes; optional but recommended
First comment Post immediately; story-driven, not feature list; significantly impacts engagement
Topic tags 3–5 relevant; match Product Hunt taxonomy

Launch Day Strategy

Practice Guideline
Timing Tuesday–Thursday; 12:01am Pacific works best
Narrative Create story (problem → solution), not feature list
Engagement Reply to every comment; thank supporters; answer questions
Avoid Begging for upvotes (risk of shadowban)

Principle: Product Hunt is a visibility amplifier and credibility boost—not primarily a customer acquisition channel.

Realistic Expectations

Outcome Upvotes Placement
Poor 50–100 —
Average 200–400 Top 10
Good 500–800 Top 5
Great 800+ Product of the Day

Beyond Listing

Offering Use When
Product Hunt Daily Newsletter feature; high-intent audience
Social promotion PH shares on X, LinkedIn; launch-day amplification
Featured placement Paid promotion options

Post-Launch

  • Continue engaging with new users
  • Thank-you emails to supporters
  • Ask for feedback
  • See directory-submission for other directories; cold-start-strategy for full launch plan

Output Format

  • Readiness checklist (tagline, gallery, first comment, topic tags)
  • First comment draft (story-driven)
  • Tagline options (≤60 chars)
  • 30-day timeline (if planning ahead)
  • directory-submission: Taaft, G2, curated lists; Product Hunt is one directory—see for multi-platform submission
  • cold-start-strategy: Full launch plan; Product Hunt as channel
  • indie-hacker-strategy: Indie hacker Product Hunt, first 100 users
  • media-kit-page-generator: Press kit, screenshots for launch
  • analytics-tracking: UTM for Product Hunt traffic attribution
1---
2name: product-hunt-launch
3description: When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.
4metadata:
5 version: 1.1.0
6---
7 
8# Channels: Product Hunt Launch
9 
10Guides preparing and executing a Product Hunt launch. Product Hunt is a community-driven product discovery platform; only ~10% of submissions get featured on the homepage. Best for SaaS, developer tools, AI/ML products, and productivity software. Physical products and service businesses have limited success.
11 
12**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.
13 
14## Initial Assessment
15 
16**Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
17 
18Identify:
191. **Product type**: SaaS, AI tool, app, Chrome extension
202. **Launch readiness**: Landing page, screenshots, tagline, first comment
213. **Hunter**: Self-hunt or Top Hunter (optional but helps)
22 
23## 30-Day Preparation Plan
24 
25| Phase | Days | Actions |
26|-------|------|---------|
27| **Teaser** | 30–21 | Build "notify me" page; decide self-hunt vs hunter; engage in community |
28| **Supporters** | 20–11 | Build list of 200+ (makers, industry contacts, followers, users) |
29| **Assets** | 10–3 | Finalize tagline (≤60 chars), gallery images (1270×760), demo video (<2 min), maker comment, 3–5 topic tags; build awareness on X/LinkedIn 2–4 weeks before |
30| **Launch day** | 2–1 | Clear calendar for 16+ hours; Product Hunt runs midnight–midnight Pacific |
31 
32## Product Hunt Fields
33 
34| Field | Spec |
35|-------|------|
36| **Tagline** | ≤60 chars; no emojis unless part of product name; catchy, benefit-focused |
37| **Gallery** | 1270×760 px recommended; readable, show product value |
38| **Demo video** | <2 minutes; optional but recommended |
39| **First comment** | Post immediately; story-driven, not feature list; significantly impacts engagement |
40| **Topic tags** | 3–5 relevant; match Product Hunt taxonomy |
41 
42## Launch Day Strategy
43 
44| Practice | Guideline |
45|----------|-----------|
46| **Timing** | Tuesday–Thursday; 12:01am Pacific works best |
47| **Narrative** | Create story (problem → solution), not feature list |
48| **Engagement** | Reply to every comment; thank supporters; answer questions |
49| **Avoid** | Begging for upvotes (risk of shadowban) |
50 
51**Principle**: Product Hunt is a visibility amplifier and credibility boost—not primarily a customer acquisition channel.
52 
53## Realistic Expectations
54 
55| Outcome | Upvotes | Placement |
56|---------|---------|-----------|
57| Poor | 50–100 | — |
58| Average | 200–400 | Top 10 |
59| Good | 500–800 | Top 5 |
60| Great | 800+ | Product of the Day |
61 
62## Beyond Listing
63 
64| Offering | Use When |
65|----------|----------|
66| **Product Hunt Daily** | Newsletter feature; high-intent audience |
67| **Social promotion** | PH shares on X, LinkedIn; launch-day amplification |
68| **Featured placement** | Paid promotion options |
69 
70## Post-Launch
71 
72- Continue engaging with new users
73- Thank-you emails to supporters
74- Ask for feedback
75- See **directory-submission** for other directories; **cold-start-strategy** for full launch plan
76 
77## Output Format
78 
79- **Readiness checklist** (tagline, gallery, first comment, topic tags)
80- **First comment** draft (story-driven)
81- **Tagline** options (≤60 chars)
82- **30-day timeline** (if planning ahead)
83 
84## Related Skills
85 
86- **directory-submission**: Taaft, G2, curated lists; Product Hunt is one directory—see for multi-platform submission
87- **cold-start-strategy**: Full launch plan; Product Hunt as channel
88- **indie-hacker-strategy**: Indie hacker Product Hunt, first 100 users
89- **media-kit-page-generator**: Press kit, screenshots for launch
90- **analytics-tracking**: UTM for Product Hunt traffic attribution
91 

Discussion

Alternatives

/bragTurn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag", "let's brag about this", "make a launch video", "turn this into a video", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed.Business & ops · MIT/brag-slimTurn a project directory or a website URL into a short, shareable launch video with music, motion, and share copy. One file, no bundled assets — built entirely by the model with the tools already on the machine. Use when someone says "/brag-slim", "let's /brag about this", "brag about <url>", "make a launch video", or wants to show off what they built. If the /brag skill is also installed, let /brag handle those phrases; it hands off here on Opus 5.5.Business & ops · MITBusiness motion filmPlan, build and quality-check a premium short commercial for a real business (roofing, property, ecommerce, B2B software) using AI-generated footage, code-built motion (HTML/GSAP), selective Three.js and an independent-critic "Gauntlet" loop. Use when asked to make a launch-style / SaaS-style video, business ad, explainer, sample reel or pitch video, or to review and improve one. Encodes motion principles distilled from 28 professional launch films, a quality bar, audio rules and a business-offer playbook.Business & ops · MITAI Product Launch PlaybookLaunch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.Business & ops · MIT