← ClaudeAtlas

ph-launchlisted

Plan and run a Product Hunt launch end to end — a phased T-30 to T+7 prep plan, an hour-by-hour launch-day runbook, listing craft (tagline, gallery, description), the pinned maker first-comment, and hunter outreach. Use when the user wants to launch on Product Hunt, asks for a Product Hunt launch checklist or plan, wants to know the best day to launch, how to get upvotes on Product Hunt (without breaking the rules), how to find or whether they need a hunter, how to write their tagline or first comment, what the gallery/screenshot specs are, a launch-day plan or timeline, how to launch their startup or SaaS, or "I'm launching on Product Hunt next week, what do I do".
whatsuppiyush/product-hunt-claude-skill · ★ 0 · AI & Automation · score 76
Install: claude install-skill whatsuppiyush/product-hunt-claude-skill
# PH Launch Plan and run a Product Hunt launch the way the launches that actually rank do it: as a four-week process, not a single day of luck. This skill turns a launch date into a concrete plan, drafts the copy that converts, schedules the day hour by hour, and keeps the user on the right side of Product Hunt's rules. Everything here works with **no account, no API key, and no payment.** The value is the methodology in `references/` plus the fill-in templates and full checklist in `data/`. ## The one idea everything is built on A Product Hunt rank is **relative** to that day's field and is mostly decided **before** launch day. It is capped by how many real, reachable people you can activate in the first hours — not by how good the product is or how polished the gallery looks. So the whole plan front-loads **distribution** (email list, communities you genuinely belong to, a Coming Soon page collecting followers) and treats assets as the smaller task they are. If the user cannot name the specific people who will show up in the first hour, they are not ready to pick a date — help them build that list first. Never fabricate a Product Hunt statistic, a rank, an upvote count, or a rule. Ground every number in `references/`/`data/` or a live check you actually performed, and clearly say when a figure is a rough benchmark rather than a promise. ## What this skill is good at 1. **A personalized plan** — take a launch date, work backward to T-30, and produce a week-by-week