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.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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:
| 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 |
| 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 |
| 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.
| Outcome | Upvotes | Placement |
|---|---|---|
| Poor | 50–100 | — |
| Average | 200–400 | Top 10 |
| Good | 500–800 | Top 5 |
| Great | 800+ | Product of the Day |
| 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 |
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
日本語の概要は準備中です。原文の説明を表示しています。