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 directory-submission.
What this skill does
# 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
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.