product-hunt-launch-plan
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseProduct Hunt Launch Plan
Product Hunt上线计划
Purpose
目标
Generate a comprehensive, personalized Product Hunt launch plan with actionable steps from A-Z to help the user rank #1 Product of the Day.
生成一份涵盖从A到Z可执行步骤的全面、个性化Product Hunt上线计划,帮助用户拿下当日最佳产品(#1)的排名。
Execution Logic
执行逻辑
Check $ARGUMENTS first to determine execution mode:
首先检查$ARGUMENTS以确定执行模式:
If $ARGUMENTS is empty or not provided:
若$ARGUMENTS为空或未提供:
Respond with:
"product-hunt-launch-plan loaded. I'll create a personalized Product Hunt launch strategy to help you rank #1. Let me gather some information about your product first."
Then proceed to the Discovery Questions phase.
回复内容如下:
"已加载product-hunt-launch-plan。我将为您制定一份个性化的Product Hunt上线策略,助力您拿下#1排名。请先提供一些关于您产品的信息。"
之后进入“调研问题”阶段。
If $ARGUMENTS contains content:
若$ARGUMENTS包含内容:
Use the provided content as initial context, but still proceed through Discovery Questions to fill any gaps.
将提供的内容作为初始背景信息,但仍需通过调研问题填补信息缺口。
Task Execution
任务执行
When user engages with this skill:
当用户使用此技能时:
1. MANDATORY: Read Reference Files FIRST
1. 强制要求:首先读取参考文件
BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP
Before doing ANYTHING else, you MUST use the Read tool to read the reference file:
Read: ./references/ultimate_product_hunt_launch_guide.mdWhat you will find:
- Complete 3-phase launch strategy (Before, During, After)
- Timing and day selection guidance
- Asset requirements and examples
- Support list building strategies
- Launch day timeline hour-by-hour
- Hidden gems and pro tips from makers who ranked #1
- 20+ alternative launch platforms
DO NOT PROCEED to Step 2 until you have read this file and have the complete guide in context.
阻塞性要求——请勿跳过此步骤
在进行任何其他操作之前,您必须使用Read工具读取以下参考文件:
Read: ./references/ultimate_product_hunt_launch_guide.md您将在文件中获取:
- 完整的三阶段上线策略(上线前、上线中、上线后)
- 时间与日期选择指南
- 物料要求及示例
- 支持者名单构建策略
- 上线当日的逐小时时间线
- 拿下#1排名的创作者分享的隐藏技巧和专业建议
- 20+个备选上线平台
在读取该文件并掌握完整指南内容之前,请勿进入步骤2。
2. Check for Business Context
2. 检查业务背景
Check if exists in the project root.
FOUNDER_CONTEXT.md- If it exists: Read it and extract all relevant product information (product name, description, target audience, unique value proposition, current traction, audience size).
- If it doesn't exist: You will gather this information through Discovery Questions.
检查项目根目录下是否存在文件。
FOUNDER_CONTEXT.md- 若存在: 读取该文件并提取所有相关产品信息(产品名称、描述、目标受众、独特价值主张、当前用户吸引力、受众规模)。
- 若不存在: 通过调研问题收集这些信息。
3. Discovery Questions (MANDATORY)
3. 调研问题(强制要求)
Ask up to 10 targeted questions to personalize the launch plan.
Present questions using the AskUserQuestion tool or conversationally. Gather:
-
Product Basics
- What is your product name and one-line description?
- What problem does it solve and for whom?
-
Current State
- What's your current launch date (or target timeframe)?
- Do you have a Product Hunt account? Is it active/warmed?
-
Audience & Reach
- How large is your email list?
- What's your Twitter/X following size?
- Are you active in any communities (Indie Hackers, Discord, Slack)?
-
Assets Readiness
- Do you have product screenshots/demo video ready?
- Do you have a landing page live?
-
Support Network
- Do you have founder friends who could support the launch?
- Have you supported other Product Hunt launches before?
-
Goals & Constraints
- What's your primary goal? (users, awareness, investors, validation)
- Any constraints? (budget, time, team size)
Adapt questions based on FOUNDER_CONTEXT.md if available. Skip questions already answered there.
提出最多10个针对性问题,以实现上线计划的个性化。
使用AskUserQuestion工具或自然对话形式提出问题,收集以下信息:
-
产品基础信息
- 您的产品名称和一句话描述是什么?
- 它解决了什么问题,面向哪些用户?
-
当前状态
- 您当前的上线日期(或目标时间范围)是什么?
- 您是否拥有Product Hunt账户?该账户是否活跃/已预热?
-
受众与触达范围
- 您的邮件列表规模有多大?
- 您的Twitter/X粉丝数量是多少?
- 您是否活跃于任何社区(如Indie Hackers、Discord、Slack)?
-
物料准备情况
- 您是否已准备好产品截图/演示视频?
- 您的落地页是否已上线?
-
支持网络
- 您是否有创始人朋友可以支持此次上线?
- 您是否曾支持过其他Product Hunt产品的上线?
-
目标与限制条件
- 您的首要目标是什么?(用户增长、品牌曝光、吸引投资者、产品验证)
- 是否存在任何限制条件?(预算、时间、团队规模)
若存在FOUNDER_CONTEXT.md文件,请根据其内容调整问题。 跳过已在文件中得到解答的问题。
4. Analyze & Personalize
4. 分析与个性化定制
Based on gathered information, assess:
- Support Strength: Weak (<100 supporters), Moderate (100-300), Strong (300-500+)
- Asset Readiness: Not ready, Partially ready, Fully ready
- Timeline: Rushed (<2 weeks), Tight (2-4 weeks), Ideal (4+ weeks)
- Audience Reach: Limited, Moderate, Strong
Use this assessment to customize recommendations.
根据收集到的信息,进行以下评估:
- 支持力度: 弱(<100位支持者)、中等(100-300位)、强(300-500+位)
- 物料准备情况: 未准备好、部分准备好、完全准备好
- 时间线: 仓促(<2周)、紧张(2-4周)、理想(4+周)
- 受众触达范围: 有限、中等、广泛
基于此评估定制推荐方案。
5. Generate Personalized Launch Plan
5. 生成个性化上线计划
Create a comprehensive plan with:
Section 1: Executive Summary
- Product overview (from their input)
- Launch date recommendation
- Predicted ranking potential based on their current assets
- Key success factors for THEIR specific situation
Section 2: Pre-Launch Phase (customize timeline based on their date)
- Week-by-week action items
- Specific community recommendations based on their niche
- Asset creation checklist tailored to what they're missing
- Support list building strategy based on their current reach
Section 3: Launch Week Preparation
- Day-by-day countdown
- Specific outreach templates personalized for their product
- Social media post drafts
- Email copy suggestions
Section 4: Launch Day Battle Plan
- Hour-by-hour timeline in their timezone
- Specific platforms to post on based on their product type
- Engagement scripts for comments
- Monitoring setup
Section 5: Post-Launch Strategy
- Follow-up actions
- How to leverage results (even if not #1)
- Badge/social proof implementation
Section 6: Hidden Gems & Pro Tips
Include 5-10 advanced tactics from the reference guide, selected based on relevance to their situation.
Section 7: Alternative Launch Platforms
List the 20+ platforms from the reference guide, prioritized based on their product type (dev tool, SaaS, AI product, etc.).
创建一份包含以下内容的全面计划:
第1部分:执行摘要
- 产品概述(基于用户输入)
- 推荐上线日期
- 根据当前物料情况预测排名潜力
- 针对其具体情况的关键成功因素
第2部分:上线前阶段(根据其目标日期定制时间线)
- 每周行动项
- 基于其细分领域的特定社区推荐
- 针对缺失物料的定制化物料创建清单
- 基于当前触达范围的支持者名单构建策略
第3部分:上线周准备工作
- 逐日倒计时安排
- 针对其产品定制的特定外联模板
- 社交媒体帖子草稿
- 邮件文案建议
第4部分:上线当日作战计划
- 对应其时区的逐小时时间线
- 基于其产品类型的特定发布平台
- 评论互动脚本
- 监控设置
第5部分:上线后策略
- 跟进行动
- 如何利用上线结果(即使未拿到#1排名)
- 徽章/社交证明的落地
第6部分:隐藏技巧与专业建议
从参考指南中选取5-10个与其情况相关的高级策略。
第7部分:备选上线平台
列出参考指南中的20+个平台,并根据其产品类型(开发工具、SaaS、AI产品等)进行优先级排序。
6. Format and Verify
6. 格式化与验证
- Structure output according to Output Format section
- Complete Quality Checklist self-verification before presenting
- 按照输出格式部分的要求构建输出内容
- 在呈现计划前完成质量检查表的自我验证
Writing Rules
写作规则
Hard constraints. No interpretation.
硬性约束,无灵活解释空间。
Core Rules
核心规则
- Be specific and actionable — no vague advice like "build community"
- Include exact timelines, numbers, and examples
- Personalize every recommendation to THEIR product
- Reference their product name throughout the plan
- Include templates they can copy/paste
- Prioritize actions by impact
- 内容需具体且可执行——避免“构建社区”这类模糊建议
- 包含精确的时间线、数字和示例
- 每一项推荐都需针对其产品进行个性化定制
- 计划全程提及他们的产品名称
- 提供可直接复制粘贴的模板
- 按影响力优先级排列行动项
Personalization Rules
个性化规则
- If small audience (<500): Focus on community building and reciprocity tactics
- If large audience (5000+): Focus on coordinated launch and momentum strategies
- If dev tool: Emphasize Hacker News, DevHunt, GitHub community
- If AI product: Include AI-specific directories
- If B2B SaaS: Focus on LinkedIn, professional communities
- If consumer app: Focus on Twitter/X, visual assets
- 若受众规模较小(<500):重点关注社区构建与互惠策略
- 若受众规模较大(5000+):重点关注协同上线与势头维护策略
- 若为开发工具:强调Hacker News、DevHunt、GitHub社区
- 若为AI产品:纳入AI专属目录平台
- 若为B2B SaaS:重点关注LinkedIn及专业社区
- 若为消费类应用:重点关注Twitter/X及视觉物料
Honesty Rules
诚信规则
- Be realistic about their chances based on their current situation
- If timeline is too tight, say so and suggest rescheduling
- If assets are weak, prioritize fixing that first
- Don't promise #1 if their support base is too small
- 根据其当前情况如实评估排名可能性
- 若时间线过于仓促,需明确说明并建议重新安排日期
- 若物料准备不足,优先建议完善物料
- 若其支持基础过小,不得承诺能拿到#1排名
Output Format
输出格式
markdown
undefinedmarkdown
undefinedProduct Hunt Launch Plan: [Product Name]
Product Hunt Launch Plan: [Product Name]
Executive Summary
Executive Summary
Product: [Name] - [One-liner]
Recommended Launch Date: [Date] ([Day of week])
Launch Time: 12:01 AM PST
Ranking Potential: [Assessment based on their situation]
Critical Success Factor: [The ONE thing they must nail]
Product: [Name] - [One-liner]
Recommended Launch Date: [Date] ([Day of week])
Launch Time: 12:01 AM PST
Ranking Potential: [Assessment based on their situation]
Critical Success Factor: [The ONE thing they must nail]
Phase 1: Pre-Launch ([X] weeks out)
Phase 1: Pre-Launch ([X] weeks out)
Week [X]: [Focus Area]
Week [X]: [Focus Area]
- Action item 1
- Action item 2 ...
- Action item 1
- Action item 2 ...
Week [X-1]: [Focus Area]
Week [X-1]: [Focus Area]
...
...
Phase 2: Launch Week
Phase 2: Launch Week
Day -7 to -1: Final Preparations
Day -7 to -1: Final Preparations
...
...
Launch Day: Hour-by-Hour Battle Plan
Launch Day: Hour-by-Hour Battle Plan
[Time in their timezone] - [Action]
...
[Time in their timezone] - [Action]
...
Phase 3: Post-Launch
Phase 3: Post-Launch
Day 1-3: Immediate Actions
Day 1-3: Immediate Actions
...
...
Week 1: Capitalize on Results
Week 1: Capitalize on Results
...
...
Your Personalized Tips
Your Personalized Tips
Based on your situation, focus on these advanced tactics:
- [Tip Name]: [Specific advice for their situation] ...
Based on your situation, focus on these advanced tactics:
- [Tip Name]: [Specific advice for their situation] ...
Alternative Launch Platforms (Prioritized for [Product Type])
Alternative Launch Platforms (Prioritized for [Product Type])
Launch This Week (Alongside Product Hunt)
Launch This Week (Alongside Product Hunt)
| Platform | Why It Fits You |
|---|---|
| ... |
| Platform | Why It Fits You |
|---|---|
| ... |
Launch Next Week
Launch Next Week
...
...
Ready-to-Use Templates
Ready-to-Use Templates
Supporter DM Template
Supporter DM Template
[Personalized template with their product details]
[Personalized template with their product details]
Launch Day Tweet Thread
Launch Day Tweet Thread
[Draft thread they can customize]
[Draft thread they can customize]
Email to Subscribers
Email to Subscribers
[Draft email copy]
[Draft email copy]
Your Launch Checklist
Your Launch Checklist
Assets Needed
Assets Needed
- Item (Status: Ready/Needed) ...
- Item (Status: Ready/Needed) ...
Support List Target
Support List Target
- Category: [X] people (Current: [Y]) ...
---- Category: [X] people (Current: [Y]) ...
---References
参考资料
This file MUST be read using the Read tool before creating any launch plan (see Step 1):
| File | Purpose |
|---|---|
| Complete Product Hunt strategy from Tibo (Maker of the Year 2022), including 3-phase launch process, hidden gems, pro tips, and 20+ alternative platforms |
Why this matters: This guide contains battle-tested strategies from someone who has ranked #1 multiple times. The tactics, timing, and templates are proven to work — not theoretical advice.
在创建任何上线计划之前,必须使用Read工具读取以下文件(见步骤1):
| 文件 | 用途 |
|---|---|
| 由2022年度创作者Tibo提供的完整Product Hunt策略,包含三阶段上线流程、隐藏技巧、专业建议以及20+个备选上线平台 |
重要性说明: 本指南包含多次拿下#1排名的创作者经过实战检验的策略。其中的技巧、时间安排和模板均已被证实有效,而非理论性建议。
Quality Checklist (Self-Verification)
质量检查表(自我验证)
Before finalizing output, verify ALL of the following:
在最终确定输出内容前,需验证以下所有项:
Pre-Execution Check
执行前检查
- I read before creating the plan
./references/ultimate_product_hunt_launch_guide.md - I checked for and read if it exists
FOUNDER_CONTEXT.md - I have the complete guide content in context
- 在创建计划前已读取
./references/ultimate_product_hunt_launch_guide.md - 已检查是否存在,若存在则已读取
FOUNDER_CONTEXT.md - 已掌握完整的指南内容背景
Discovery Check
调研检查
- I asked targeted questions to understand their specific situation
- I know their product, audience size, timeline, and assets status
- I adapted my questions based on available context
- 已提出针对性问题以了解其具体情况
- 已掌握其产品、受众规模、时间线及物料准备状态
- 已根据可用背景调整问题
Personalization Check
个性化检查
- Every section references THEIR product by name
- Recommendations match their audience size and reach
- Timeline is realistic for their launch date
- Platform recommendations match their product type
- Templates include their specific product details
- 每个部分都提及了他们的产品名称
- 推荐内容与其受众规模和触达范围匹配
- 时间线与其上线日期相符且现实可行
- 平台推荐与其产品类型匹配
- 模板包含其产品的具体细节
Completeness Check
完整性检查
- All 3 phases covered (Before, During, After)
- Hour-by-hour launch day timeline included
- Hidden gems/pro tips section included
- Alternative platforms listed and prioritized
- Ready-to-use templates provided
- Checklist with current status included
- 已覆盖全部三个阶段(上线前、上线中、上线后)
- 已包含上线当日的逐小时时间线
- 已包含隐藏技巧/专业建议部分
- 已列出备选平台并进行优先级排序
- 已提供可直接使用的模板
- 已包含带有当前状态的检查清单
Honesty Check
诚信检查
- Ranking assessment is realistic
- Weak areas are called out with solutions
- Timeline concerns are addressed
- No false promises of guaranteed #1
If ANY check fails → revise before presenting.
- 排名评估现实可行
- 已指出薄弱环节并提供解决方案
- 已解决时间线相关的问题
- 未做出保证拿到#1排名的虚假承诺
若任何一项检查未通过 → 需在呈现前进行修订。
Defaults & Assumptions
默认设置与假设
Use these unless the user overrides:
- Launch day: Tuesday, Wednesday, or Thursday (higher traffic)
- Launch time: 12:01 AM PST (Product Hunt reset time)
- Target ranking: Top 5 (requires ~500 engaged supporters)
- Preparation time: 4 weeks ideal minimum
- Primary goal: User acquisition and validation
- Hunter strategy: Self-hunt (60% of #1 products are self-hunted)
- Asset format: Static images prioritized over video (higher engagement)
Document any assumptions made in the Executive Summary.
除非用户另行指定,否则使用以下默认设置:
- 上线日期: 周二、周三或周四(流量更高)
- 上线时间: 太平洋标准时间(PST)凌晨12:01(Product Hunt重置时间)
- 目标排名: 前5(需要约500位活跃支持者)
- 准备时间: 理想最短时长为4周
- 首要目标: 用户获取与产品验证
- 猎人策略: 自主申请上线(60%的#1产品采用此方式)
- 物料格式: 优先使用静态图片而非视频(参与度更高)
在执行摘要中记录所有做出的假设。