From ph-complete
Crafts engaging, personalized responses to Product Hunt launch comments including praise, questions, feedback, and negativity to boost engagement and visibility.
npx claudepluginhub yoanbernabeu/producthunt-skills --plugin ph-completeThis skill uses the workspace's default tool permissions.
This skill helps you respond to Product Hunt comments effectively, maintaining engagement and building community throughout your launch.
Crafts Product Hunt-compliant messages for launch emails, social posts, supporter outreach, and responses that avoid upvote requests to prevent penalties.
Optimizes Product Hunt launches with tagline specs, gallery image strategies and prompts, maker comments, and launch day tactics for products, startups, and side projects.
Guides Product Hunt launches for SaaS, dev tools, AI products: 30-day prep plans, submission fields (tagline, gallery, first comment), timing, engagement strategies.
Share bugs, ideas, or general feedback.
This skill helps you respond to Product Hunt comments effectively, maintaining engagement and building community throughout your launch.
Aim to respond to every comment within 9 minutes during peak hours. This:
Comment: "Great product! Love it!"
Response Strategy:
Template:
Thanks so much, [Name]! 🙏
Really appreciate you checking it out. What brought you
to [Product]? Would love to know what problem you're
hoping to solve with it!
Comment: "This solves exactly the problem I've been having with [specific issue]. The [feature] is brilliant!"
Response Strategy:
Template:
[Name], this made my day! That [specific issue] was exactly
why we built [feature] — we experienced the same pain.
Fun fact: [related insight about the feature/decision]
If you have any ideas for making it even better, I'm all ears!
Comment: "Does this work with [tool/platform]?"
Response Strategy:
Templates:
If Yes:
Yes! We integrate with [tool] — you can connect it in
Settings → Integrations → [Tool].
Here's a quick guide: [link if available]
Let me know if you hit any snags!
If No (but planned):
Not yet, but it's on our roadmap! [Tool] integration is
something we've heard a lot about.
Mind if I add you to our notify list for when it ships?
Your use case would really help us prioritize.
If No (not planned):
We don't currently integrate with [tool]. Our focus right
now is on [current priority].
That said, we have an API that some users have used to
connect with [tool]. Happy to share details if useful!
Comment: "What's the tech stack? How does [specific feature] work?"
Response Strategy:
Template:
Great question! Here's the quick version:
Stack: [Languages/frameworks]
[Feature]: [Brief technical explanation]
We chose [approach] because [reasoning].
Happy to dive deeper if you're curious about any specific part!
Comment: "Looks good, but the [aspect] seems lacking. Would be better if [suggestion]."
Response Strategy:
Template:
Really appreciate this feedback, [Name].
You're right that [aspect] could be stronger. We've been
debating [related decision] and your point about
[suggestion] is exactly the kind of input that helps.
Quick question: how would you ideally want [aspect] to work?
Any examples you've seen that do it well?
Comment: "This is just another [category]. Nothing new here."
Response Strategy:
Template:
Fair point on first look! There are definitely a lot of
[category] tools out there.
Where we focus differently is [key differentiator]. For
example, [specific example].
Might not be for everyone, but for folks who struggle with
[specific pain point], we've seen it make a real difference.
Appreciate you taking the time to check it out!
Comment: "Tried signing up but got an error."
Response Strategy:
Template:
So sorry about that, [Name]! That's definitely not the
experience we want.
Would you mind sharing:
• What browser/device you were using?
• What the error message said?
DM me at [contact] if easier — I'll personally make sure
you get set up.
Working on this right now. 🔧
Comment: "How is this different from [Competitor]?"
Response Strategy:
Template:
Great question! [Competitor] is solid — respect what
they've built.
Main differences:
• We focus on [your focus] vs their [their focus]
• [Specific feature/approach you do differently]
• [Pricing/philosophy difference if relevant]
Best way to know is to try both! Happy to help you
evaluate based on your specific needs.
Comment: "What's the pricing? Is there a free tier?"
Response Strategy:
Template:
Happy to break it down!
Free tier: [What's included]
Paid plans: Starting at $[X]/mo for [what you get]
For Product Hunt: We're doing [special offer] for the
launch — [details].
Worth noting: [Key value point that justifies price]
Any specific features you're looking for?
Response Strategy:
Template:
Thanks for stopping by! Feel free to DM if you have
questions about [Product]. 👋
Have a library of response starting points, but always personalize for each comment.
If using a tool, set up text expansion for common phrases.
Group similar questions and address at once while personalizing each.
Assign comment types to different team members.
When conversations develop:
If similar questions appear:
Great question! I touched on this in my reply to [Name]
above — [brief summary]. But specifically for your case,
[additional info].
COMMENT RESPONSE FOR: [Product Name]
ORIGINAL COMMENT:
"[Comment text]"
— @[username]
COMMENT TYPE: [Type from list above]
RESPONSE:
[Your crafted response]
RESPONSE INCLUDES:
✓ Name personalization
✓ Specific answer
✓ Value add
✓ Engagement hook