producthunt-launch-kit

Name: producthunt-launch-kit
Author: Varnan-Tech

20installs59forks

How to install producthunt-launch-kit?

varnan-tech/opendirectory/producthunt-launch-kit

$npx -y skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit

Installs into the current project.

Summary

Use when the user asks to prepare a Product Hunt launch or generate Product Hunt listing assets. Generates tagline variants under 60 chars, a 500-char description, a maker comment, launch-day tweet thread, LinkedIn post, and a 4-email launch sequence.

Files · 1

View on GitHub

SKILL.md

1	# Product Hunt Launch Kit
2
3	Generate every asset you need for a Product Hunt launch: listing copy, maker comment, and day-one social posts.
4
5	---
6
7	Critical rule: Product Hunt taglines are maximum 60 characters. Descriptions are maximum 500 characters. Never make factual claims that cannot be verified. Never mention competitor names. Never say "free" unless the product is permanently free (not just a trial).
8
9	---
10
11	## Step 1: Gather Product Details
12
13	You need:
14
15	- Product name
16	- What it does (technical description, one sentence)
17	- Primary use case and target user
18	- Key differentiator from existing tools
19	- Pricing: free, freemium, paid (starting price)
20	- Open source: yes/no
21	- Launch date (for scheduling context)
22	- Any credentials, launch discount, or promo code to offer
23	- 2-3 things that make it worth upvoting (honest reasons, not marketing)
24
25	If any of these are missing, ask in one message before proceeding.
26
27	Also check for project context files:
28
29	```bash
30	ls README.md 2>/dev/null && echo "README found"
31	ls package.json 2>/dev/null && echo "package.json found"
32	```
33
34	If README.md exists, read the first 80 lines to extract product description and key features before asking questions.
35
36	---
37
38	## Step 2: Gallery Strategy
39
40	Product Hunt requires screenshots. Most listings fail because of weak or missing gallery images. Plan these before writing copy.
41
42	Spec: 1270×760px, PNG or JPG, max 8 images. The first image is the hero: it appears in feeds and cards.
43
44	Five-position framework:
45
46	\| Position \| Purpose \| What to show \|
47	\|----------\|---------\|-------------\|
48	\| 1 (Hero) \| First impression in feeds \| Product in use, clean UI or terminal output, no text overlays \|
49	\| 2 (Feature demo) \| Show the core action \| The thing that makes the product click: the "aha" moment \|
50	\| 3 (Before/After) \| Show the problem being solved \| Split screen: messy/slow state vs. clean/fast state \|
51	\| 4 (Social proof) \| Build credibility \| A real quote, a stat, or a before/after metric from a real user \|
52	\| 5 (Technical differentiator) \| Address skeptics \| Architecture diagram, benchmark, or the unusual technical decision \|
53
54	If the product is a CLI tool or library, screenshots of terminal output work well. Annotate with arrows pointing to the important part.
55
56	Video (optional but high-impact): A 60-90 second demo. Under 2 minutes. No voiceover required: screen capture with captions works.
57
58	Tell the user: "Plan [N] gallery images before launch day. The hero image (position 1) is the most important. Here's what to capture for each position: [list above, customized for this product]."
59
60	---
61
62	## Step 3: Generate Tagline Variants
63
64	The tagline appears directly under the product name on Product Hunt. It is the most read copy on your listing.
65
66	Hard limits:
67	- Maximum 60 characters (including spaces)
68	- No period at the end
69	- No hashtags
70	- Do not start with the product name
71	- No superlatives: "best", "fastest", "easiest", "most powerful"
72	- No questions
73
74	Tagline formula: `[Action verb] + [what it does] + [key differentiator]`
75
76	Generate five tagline variants:
77
78	1. Outcome-first: What the user achieves ("Ship docs without leaving your codebase")
79	2. Problem-first: Names the pain that is solved ("No more copy-pasting between Figma and code")
80	3. Technical-angle: For developer tools, lead with the tech ("SQLite to shareable web app in one command")
81	4. Comparison-free alternative: Positions without naming competitors ("Git-native code review that works inside VS Code")
82	5. Plain-English: No jargon, widest possible audience ("Turns any RSS feed into a daily email digest")
83
84	After generating, count characters for each. Flag any that exceed 60 characters and revise.
85
86	---
87
88	## Step 4: Write the Listing Description
89
90	The description appears below the tagline. Maximum 500 characters. It displays in search results and link previews.
91
92	Structure:
93	- Sentence 1: What it does and who it's for (specific)
94	- Sentence 2: The key feature or technical approach that makes it work
95	- Sentence 3 (optional): Pricing or availability
96
97	Description rules:
98	- 280-500 characters (shorter is fine; longer is truncated in previews)
99	- Present tense throughout
100	- No hype adjectives
101	- No "I": write in third person or imperative ("Turns your...", "Connects to...", not "I built...")
102	- No links (they do not render)
103	- If open source, say so: "Open source and self-hostable."
104
105	---
106
107	## Step 5: Write the Maker Comment
108
109	The maker comment is the most important driver of Product Hunt success. It is your first reply to your own post, posted within 60 seconds of launch.
110
111	Hard limits:
112	- 300-400

People who liked this also viewed

6 picks

Type

producthunt-launch-kit

20installs59forks

View on GitHub

How to install producthunt-launch-kit?

varnan-tech/opendirectory/producthunt-launch-kit

$npx -y skills add Varnan-Tech/opendirectory --skill producthunt-launch-kit

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Product Hunt Launch Kit
2
3	Generate every asset you need for a Product Hunt launch: listing copy, maker comment, and day-one social posts.
4
5	---
6
7	Critical rule: Product Hunt taglines are maximum 60 characters. Descriptions are maximum 500 characters. Never make factual claims that cannot be verified. Never mention competitor names. Never say "free" unless the product is permanently free (not just a trial).
8
9	---
10
11	## Step 1: Gather Product Details
12
13	You need:
14
15	- Product name
16	- What it does (technical description, one sentence)
17	- Primary use case and target user
18	- Key differentiator from existing tools
19	- Pricing: free, freemium, paid (starting price)
20	- Open source: yes/no
21	- Launch date (for scheduling context)
22	- Any credentials, launch discount, or promo code to offer
23	- 2-3 things that make it worth upvoting (honest reasons, not marketing)
24
25	If any of these are missing, ask in one message before proceeding.
26
27	Also check for project context files:
28
29	```bash
30	ls README.md 2>/dev/null && echo "README found"
31	ls package.json 2>/dev/null && echo "package.json found"
32	```
33
34	If README.md exists, read the first 80 lines to extract product description and key features before asking questions.
35
36	---
37
38	## Step 2: Gallery Strategy
39
40	Product Hunt requires screenshots. Most listings fail because of weak or missing gallery images. Plan these before writing copy.
41
42	Spec: 1270×760px, PNG or JPG, max 8 images. The first image is the hero: it appears in feeds and cards.
43
44	Five-position framework:
45
46	\| Position \| Purpose \| What to show \|
47	\|----------\|---------\|-------------\|
48	\| 1 (Hero) \| First impression in feeds \| Product in use, clean UI or terminal output, no text overlays \|
49	\| 2 (Feature demo) \| Show the core action \| The thing that makes the product click: the "aha" moment \|
50	\| 3 (Before/After) \| Show the problem being solved \| Split screen: messy/slow state vs. clean/fast state \|
51	\| 4 (Social proof) \| Build credibility \| A real quote, a stat, or a before/after metric from a real user \|
52	\| 5 (Technical differentiator) \| Address skeptics \| Architecture diagram, benchmark, or the unusual technical decision \|
53
54	If the product is a CLI tool or library, screenshots of terminal output work well. Annotate with arrows pointing to the important part.
55
56	Video (optional but high-impact): A 60-90 second demo. Under 2 minutes. No voiceover required: screen capture with captions works.
57
58	Tell the user: "Plan [N] gallery images before launch day. The hero image (position 1) is the most important. Here's what to capture for each position: [list above, customized for this product]."
59
60	---
61
62	## Step 3: Generate Tagline Variants
63
64	The tagline appears directly under the product name on Product Hunt. It is the most read copy on your listing.
65
66	Hard limits:
67	- Maximum 60 characters (including spaces)
68	- No period at the end
69	- No hashtags
70	- Do not start with the product name
71	- No superlatives: "best", "fastest", "easiest", "most powerful"
72	- No questions
73
74	Tagline formula: `[Action verb] + [what it does] + [key differentiator]`
75
76	Generate five tagline variants:
77
78	1. Outcome-first: What the user achieves ("Ship docs without leaving your codebase")
79	2. Problem-first: Names the pain that is solved ("No more copy-pasting between Figma and code")
80	3. Technical-angle: For developer tools, lead with the tech ("SQLite to shareable web app in one command")
81	4. Comparison-free alternative: Positions without naming competitors ("Git-native code review that works inside VS Code")
82	5. Plain-English: No jargon, widest possible audience ("Turns any RSS feed into a daily email digest")
83
84	After generating, count characters for each. Flag any that exceed 60 characters and revise.
85
86	---
87
88	## Step 4: Write the Listing Description
89
90	The description appears below the tagline. Maximum 500 characters. It displays in search results and link previews.
91
92	Structure:
93	- Sentence 1: What it does and who it's for (specific)
94	- Sentence 2: The key feature or technical approach that makes it work
95	- Sentence 3 (optional): Pricing or availability
96
97	Description rules:
98	- 280-500 characters (shorter is fine; longer is truncated in previews)
99	- Present tense throughout
100	- No hype adjectives
101	- No "I": write in third person or imperative ("Turns your...", "Connects to...", not "I built...")
102	- No links (they do not render)
103	- If open source, say so: "Open source and self-hostable."
104
105	---
106
107	## Step 5: Write the Maker Comment
108
109	The maker comment is the most important driver of Product Hunt success. It is your first reply to your own post, posted within 60 seconds of launch.
110
111	Hard limits:
112	- 300-400

People who liked this also viewed

6 picks

Type