ph-comment-responder

name	ph-comment-responder
description	Respond effectively to Product Hunt comments during launch. Use this skill to craft engaging responses, handle different types of comments, and maintain momentum through active engagement.

Product Hunt Comment Responder

This skill helps you respond to Product Hunt comments effectively, maintaining engagement and building community throughout your launch.

When to Use This Skill

• Responding to comments on launch day
• Handling different types of feedback
• Maintaining consistent response quality
• Managing negative comments
• Encouraging deeper discussions

Why Comments Matter

Algorithm Impact

• Comments signal engagement
• Response rate affects visibility
• Discussion depth matters
• Quality > Quantity

Community Impact

• Builds trust with potential users
• Shows you're active and care
• Encourages others to comment
• Creates social proof

Response Guidelines

The 9-Minute Rule

Aim to respond to every comment within 9 minutes during peak hours. This:

• Shows you're present
• Keeps conversation flowing
• Impresses observers
• Maintains momentum

Response Principles

1. Be Genuine - No copy-paste generic responses
2. Add Value - Provide useful information
3. Stay Positive - Even with criticism
4. Ask Questions - Keep conversation going
5. Be Concise - Respect everyone's time

Comment Types & Responses

Type 1: Simple Praise

Comment: "Great product! Love it!"

Response Strategy:

• Thank them genuinely
• Ask a follow-up question
• Personalize if possible

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!

---

Type 2: Detailed Praise

Comment: "This solves exactly the problem I've been having with [specific issue]. The [feature] is brilliant!"

Response Strategy:

• Acknowledge their specific points
• Share relevant context
• Invite deeper engagement

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!

---

Type 3: Question About Features

Comment: "Does this work with [tool/platform]?"

Response Strategy:

• Direct, clear answer
• If yes: explain how
• If no: share roadmap or workaround
• If maybe: be honest

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!

---

Type 4: Technical Question

Comment: "What's the tech stack? How does [specific feature] work?"

Response Strategy:

• Be open and detailed
• Show technical credibility
• Invite deeper discussion

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!

---

Type 5: Constructive Criticism

Comment: "Looks good, but the [aspect] seems lacking. Would be better if [suggestion]."

Response Strategy:

• Thank them sincerely
• Acknowledge their point
• Share your thinking
• Ask for more detail

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?

---

Type 6: Negative Criticism

Comment: "This is just another [category]. Nothing new here."

Response Strategy:

• Stay calm and professional
• Acknowledge their perspective
• Share your differentiation
• Don't be defensive

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!

---

Type 7: Bug Report / Issue

Comment: "Tried signing up but got an error."

Response Strategy:

• Apologize immediately
• Get details to fix
• Show urgency
• Follow up

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. 🔧

---

Type 8: Competitor Comparison

Comment: "How is this different from [Competitor]?"

Response Strategy:

• Be respectful of competitor
• Focus on your strengths
• Don't badmouth
• Be specific

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.

---

Type 9: Pricing Question

Comment: "What's the pricing? Is there a free tier?"

Response Strategy:

• Be clear and upfront
• Highlight value
• Mention any PH offer

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?

---

Type 10: Off-Topic / Spam

Response Strategy:

• Brief, polite redirect
• Don't engage with trolls
• Report if truly spam

Template:

Thanks for stopping by! Feel free to DM if you have
questions about [Product]. 👋

Response Quality Checklist

Every Response Should:

• Address commenter by name
• Directly answer their point
• Add value or information
• End with engagement hook (question/invitation)
• Match appropriate tone
• Be typo-free

Red Flags (Don't Do):

• ❌ Copy-paste same response
• ❌ Ignore the specific comment
• ❌ Be defensive
• ❌ Use excessive emojis
• ❌ Make promises you can't keep
• ❌ Get into arguments

Efficiency Tips

Prepare Templates (But Customize)

Have a library of response starting points, but always personalize for each comment.

Use Keyboard Shortcuts

If using a tool, set up text expansion for common phrases.

Batch Similar Comments

Group similar questions and address at once while personalizing each.

Tag Team with Co-Makers

Assign comment types to different team members.

Engagement Patterns

Comment Threading

When conversations develop:

• Keep replying to maintain thread
• Tag relevant team members
• Ask follow-up questions
• Circle back with updates

Cross-Referencing

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].

Output Format

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