product hunt launch

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 dir

claude

المهارة نفسها

# 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

**Read project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, use Sections 1–4, 5, 6, 8, 9 for submission content.

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)

## Related Skills

- **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

كيف تثبتها

Claude Code / Claude Desktop

1. Create a folder named after the skill inside your skills directory:
   - Claude Code: `~/.claude/skills/<skill-name>/`
   - A project-local skill: `<project>/.claude/skills/<skill-name>/`
2. Save the text below as `SKILL.md` in that folder, keeping the
   `---` frontmatter block at the top — the `name` and `description`
   fields are what make the skill discoverable.
3. Restart Claude Code, or run `/skills` to confirm it is listed.

The skill loads only when its `description` matches what you are doing,
so a precise description matters more than a long body.

هل نجحت معك؟

من أين جاءت

kostja94 MIT الأصل

2025 kostja94