菜单
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Comprehensive UX audit using IxDF's 7 factors, 5 usability characteristics, and 5 interaction dimensions. Holistic evaluation with redesign proposals based on user-centered design principles.
Conduct enterprise-grade research with multi-source synthesis, citation tracking, and verification. Use when user needs comprehensive analysis requiring 10+ sources, verified claims, or comparison of approaches. Triggers include "deep research", "comprehensive analysis", "research report", "compare X vs Y", or "analyze trends". Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.
Web scraping with anti-bot bypass, content extraction, undocumented APIs and poison pill detection. Use when extracting content from websites, handling paywalls, implementing scraping cascades or processing social media. Covers requests, trafilatura, Playwright with stealth mode, yt-dlp and instaloader patterns.
Production-tested setup for Tailwind CSS v4 with shadcn/ui, Vite, and React. Use when: initializing React projects with Tailwind v4, setting up shadcn/ui, implementing dark mode, debugging CSS variable issues, fixing theme switching, migrating from Tailwind v3, or encountering color/theming problems. Covers: @theme inline pattern, CSS variable architecture, dark mode with ThemeProvider, component composition, vite.config setup, common v4 gotchas, and production-tested patterns. Keywords: Tailwind v4, shadcn/ui, @tailwindcss/vite, @theme inline, dark mode, CSS variables, hsl() wrapper, components.json, React theming, theme switching, colors not working, variables broken, theme not applying, @plugin directive, typography plugin, forms plugin, prose class, @tailwindcss/typography, @tailwindcss/forms
Use when reviewing code security, auditing dependencies for CVEs, checking configuration or secret security, assessing authentication and authorization patterns, identifying OWASP vulnerabilities (injection, XSS, CSRF), or addressing security concerns about implementations.
Use when evaluating business model viability, analyzing profitability per customer/product/transaction, validating startup metrics (CAC, LTV, payback period), making pricing decisions, assessing scalability, comparing business models, or when user mentions unit economics, CAC/LTV ratio, contribution margin, customer profitability, break-even analysis, or needs to determine if a business can be profitable at scale.
| name | ph-community-outreach |
| description | Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy. |
This skill helps you leverage online communities to amplify your Product Hunt launch while maintaining authenticity and following community guidelines.
General Startup/Product:
Tech/Development:
Specific Niches:
Product Hunt Specific:
Pre-Launch (2-4 weeks before):
Launch Day Post Template:
Title: I built [Product] to solve [specific problem] -
launching on Product Hunt today
Hey r/[subreddit]!
After [X months] of building, I'm finally launching
[Product] on Product Hunt today.
**The Problem:**
[2-3 sentences about the problem]
**What I Built:**
[2-3 sentences about your solution]
**What Makes It Different:**
[Your unique angle]
**Current Status:**
- [Key metric or milestone]
- [Another relevant detail]
**Looking For:**
- Honest feedback on the concept
- Suggestions for improvement
- [Specific question for community]
Product Hunt link: [URL]
Happy to answer any questions about the build,
the tech stack, or the journey!
Title: Just launched [Product] on Product Hunt -
here's what I learned building it
Hey IH community!
Today I launched [Product] on Product Hunt and wanted
to share the journey.
**📝 The Backstory**
[How you got the idea, why you built it]
**🔨 What I Built**
[Product] is [description]. It helps [audience]
[achieve outcome].
**📊 Key Numbers**
- Time to build: [X months]
- Lines of code: [X] (or tech stack)
- Beta users before launch: [X]
- Current MRR: [X or "pre-revenue"]
**💡 Lessons Learned**
1. [Key lesson]
2. [Key lesson]
3. [Key lesson]
**🎯 What's Next**
[Your roadmap or next steps]
**🙏 The Ask**
Would love feedback from this community:
- [Specific question]
- [Specific question]
Product Hunt: [Link]
Website: [Link]
AMA about the build!
Show HN Format:
Title: Show HN: [Product Name] – [Brief description]
[Link to product]
Then in comments, add context:
Hey HN! I built [Product] because [reason].
Technical details:
- Built with [tech stack]
- [Interesting technical challenge]
- [Performance/scale info]
I'd appreciate any feedback, especially on:
- [Technical question]
- [UX question]
Happy to discuss the implementation!
COMMUNITY OUTREACH PLAN FOR: [Product Name]
TARGET COMMUNITIES:
1. Reddit
Subreddits: [List with member counts]
Pre-launch activity: [Status]
Post timing: [When]
2. Indie Hackers
Groups: [Relevant groups]
Pre-launch activity: [Status]
Post timing: [When]
3. Hacker News
Suitable: [Yes/No and why]
Post timing: [When]
4. Other
[List other communities]
POSTING SCHEDULE:
- [Time]: [Platform] - [Subreddit/community]
- [Time]: [Platform] - [Subreddit/community]
- [Time]: [Platform] - [Subreddit/community]
PRE-LAUNCH CHECKLIST:
- [ ] [Community]: [X] comments, [X] karma
- [ ] [Community]: [Status]
- [ ] [Community]: [Status]
POST DRAFTS:
[Include customized drafts for each community]