# Plan Product Hunt Launches

Product Hunt launches require precise timing, clear positioning, and strong visuals. This skill gives teams a structured checklist for listing copy, gallery assets, comments, research, and launch day execution.

## Install

```bash
npx skillstore add halt-catch-fire/product-hunt-launch
```

## Metadata

- Status: approved
- Slug: halt-catch-fire-product-hunt-launch
- Skillstore revision: r1
- Version status: missing
- Tree hash: 78825be7e9cf5a2d502e020210d67db454cf725cab150eeed9d4205c7776f795
- Author: halt-catch-fire
- GitHub username: halt-catch-fire
- License: MIT
- Repository: https://github.com/halt-catch-fire/skills/tree/main/guides/product/product-hunt-launch/
- Ref: a06681402992ceae98ba04d54cfd4ab004862696
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/halt-catch-fire-product-hunt-launch
- Manifest: https://skillstore.pages.dev/api/skills/halt-catch-fire-product-hunt-launch/manifest

## Capabilities

- Summarizes Product Hunt listing requirements, including tagline length, gallery limits, topics, makers, and product links.
- Recommends gallery image order, dimensions, and content themes for launch pages.
- Provides tagline formulas and examples for clear product positioning.
- Outlines launch timing, maker comment structure, and engagement actions for launch day.
- Suggests research prompts and related belt app commands for launch preparation.

## Use Cases

- Prepare a Startup Launch: Create a Product Hunt listing plan with tagline, gallery sequence, maker comment, and launch day timeline.
- Package a Side Project: Turn a small product into a clearer launch story with concise positioning and practical asset guidance.
- Coordinate Launch Operations: Use the checklist to assign copy, visuals, support replies, social posts, and post-launch follow-up tasks.

## Prompt Templates

### Draft a Basic Launch Plan

```
Help me plan a Product Hunt launch for [product name]. The product helps [audience] solve [problem]. Create a tagline, gallery outline, maker comment draft, and launch day checklist.
```

### Improve Listing Positioning

```
Review this Product Hunt listing draft: [paste draft]. Improve the tagline, short description, topic choices, and first gallery image concept while keeping the message clear.
```

### Build Gallery Strategy

```
Create a five-image Product Hunt gallery plan for [product]. Include the goal of each image, the visible product state, and a concise generation prompt for each image.
```

### Run a Launch Readiness Audit

```
Audit my Product Hunt launch plan for [product]. Check timing, tagline, gallery order, maker comment, outreach plan, engagement rules, and post-launch follow-up. List risks and fixes.
```

## Limitations

- It does not submit products to Product Hunt or manage an account.
- It cannot guarantee ranking, upvotes, press coverage, or community response.
- Generated image prompts and research commands may need review for brand accuracy.
- Product Hunt rules and interface details may change after the skill content was written.

## Best Practices

- Start with a clear audience and outcome before writing the tagline or gallery prompts.
- Show real product value in the first gallery image because it appears across Product Hunt surfaces.
- Prepare replies, social posts, and follow-up tasks before launch day begins.

## Anti Patterns

- Do not use vague superlatives or buzzwords that hide what the product does.
- Do not ask people for upvotes because it can violate Product Hunt rules.
- Do not rely on generic gallery images that fail to show the actual product workflow.

## Security Audit

- Audited at: 2026-07-06T16:52:43.866\+00:00
- Summary: The skill is a Markdown Product Hunt launch guide with visible belt CLI examples and documentation links. The static findings are Markdown backticks, fenced examples, ordinary links, and launch-planning wording rather than hidden execution, malware behavior, prompt injection, or data exfiltration.

## Stats

- Views: 0
- Downloads: 5
- Favorites: 0
- Popularity score: 0