cold-start-strategy
When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start", "cold start problem", "first users" or "seed users". For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 12
- Forks
- 0
01 前言 Front Matter
- name
- cold-start-strategy
- metadata
- { "version": "1.3.0" }
- description
- When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start", "cold start problem", "first users" or "seed users". For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.
03 SKILL.md 正文
Strategies: Cold Start
Guides cold start strategy for AI/SaaS products: getting first users and traction when you have zero. The cold start problem is overcoming the chicken-and-egg barrier; most startups fail due to poor distribution, not product quality. For indie hacker context (first 100 users, Build in Public, Pieter Levels tactics), see indie-hacker-strategy.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and positioning.
Identify:
- Product type: AI tool, SaaS, app, B2B, B2C
- Target audience: Where they spend time
- Budget: Zero, minimal ($500–1K), or moderate
- Timeline: Pre-launch, launch week, post-launch
Cold Start Channels
| Channel | Audience | Use | Notes |
|---|---|---|---|
| Product Hunt | Indie makers, early adopters | Launch-day buzz; community upvotes | ~3% conversion; traffic spike; see product-hunt-launch |
| AppSumo / LTD | Deal seekers, early adopters | Lifetime deal for fast revenue, validation | Quick cash; price-sensitive users; see discount-marketing-strategy for LTD structure, trade-offs |
| Subreddit-specific | r/AlphaAndBetaUsers, r/roastmystartup, r/devops, r/SaaS | 80/20 rule; 5+ months for traction; lead with story | |
| Indie Hackers | Indie makers, founders | Sustained engagement; authentic journey | ~23% conversion; 4–6 months; see indie-hacker-strategy for tactics |
| Hacker News | Tech, startups | Show HN launch | Luck + timing; front page = traffic spike |
| Directory submission | AI tools, product launch | Taaft, G2, niche directories | Validate PMF; seed users; see directory-submission |
| Founder-led outbound | B2B, high ACV | Cold email, LinkedIn; 10–15 personalized outreaches/day | Pre-$5K MRR; only reliable path when ACV >$500/mo |
| Community engagement | Target users | Forums, LinkedIn groups, Discord | 45–90 days; contribute value first |
Finding Users: Demand-Signal Outreach
Low-cost ways to find and reach users who are already expressing need. Use when Product Hunt, directories, or forums are not enough.
Social Platform Search
Search Twitter/X, LinkedIn, Reddit, and niche communities for demand signals:
| Signal | What to seek |
|---|---|
| Keywords | Industry terms, category keywords, "looking for [X] tool," "best alternative to [Y]" |
| Discussion | Industry threads, complaints about competitors, "anyone used…" or "recommend…" posts |
| Platform | Choose where your audience spends time (Twitter/X, LinkedIn, Reddit, Discord, vertical forums) |
Freelance Platforms (Fiverr, Upwork)
| Step | Practice |
|---|---|
| Search | Service requests related to your product (e.g. "need logo design," "looking for video editor") |
| Identify | Buyers in job descriptions or comments who have related needs |
| Reach | Offer help or tool recommendation; introduce product politely |
Users often have clear need and budget; high intent.
Comment Outreach (Twitter/X, etc.)
| Practice | Guideline |
|---|---|
| Search | Brand, category, "looking for AI tool," "best alternative to…" |
| Reply | Comment on posts where users express need; avoid spam |
| Tone | Sincere; honest that it's your product; invite trial and feedback |
| Avoid | Hard sell; copy-paste; repeated posting |
Example outreach: "Hi, I'm building something similar. If you'd like to try it: [link]. Happy to hear any feedback—we're iterating actively."
Feedback collection: DM, email, survey, user interview, in-app feedback—choose by channel and context.
Multi-Channel Launch (6–7 Week)
Coordinated launch across channels yields 5–6× more users than single-channel:
| Week | Focus |
|---|---|
| 1–2 | Audience building (LinkedIn 3×/week) |
| 3–4 | Beta; community engagement |
| 5 | Pre-launch countdown |
| 6 | Product Hunt + Reddit/Indie Hackers |
| 7 | Post-launch follow-up |
Build in public before launch—share progress, validate ideas, create invested audience. For indie hacker first 100 users, Build in Public content framework (40/30/20/10), Pieter Levels tactics → indie-hacker-strategy.
Pre-Launch
- Validate demand: 10–15 target user conversations; 20–30 before launch
- Waitlist: 8–12 weeks before launch; target 200–1,000 signups
- Landing page: Ready; screenshots, description, media kit
- Avoid: Perfectionism; large-scale paid ads before PMF—see paid-ads-strategy. Small-budget Google Ads for PMF testing is valid.
What Doesn't Work Early
- Hiring SDRs before founder has closed 10 customers
- Large-scale paid ads before product-market fit—see paid-ads-strategy. Small-budget PMF testing (e.g., $47–500 Google Ads + landing page) is valid.
- Sporadic execution; "spray and pray" targeting
- Mass submission to low-quality directories
Output Format
- Channel selection (2–3 channels; execute well)
- Timeline (pre-launch, launch, post-launch)
- Readiness checklist
- Platform-specific actions (Product Hunt, Reddit, etc.)
Related Skills
- pmf-strategy: Product-market fit validation; when to scale; avoid large-scale paid before PMF
- gtm-strategy: Full GTM framework; cold start differs (0→1 vs commercialization)
- paid-ads-strategy: Two modes—PMF testing (small budget) vs conversion-driven (post-PMF); when to add paid after cold start
- google-ads: PMF testing setup; small-budget validation
- discount-marketing-strategy: LTD structure, pricing, trade-offs; cold start uses LTD as channel
- product-hunt-launch: Product Hunt preparation and launch
- directory-submission: Taaft, G2, curated lists—directory listings as cold-start channel
- community-forum: Indie Hackers, HN, Reddit—forum/community as cold-start channel
- reddit-posts: Reddit post copy for cold-start posts
- integrated-marketing: Channel mix; cold start is early-stage channel strategy
- media-kit-page-generator: Assets required for Product Hunt and directory submissions
- indie-hacker-strategy: Indie hacker first 100 users; Build in Public; Pieter Levels tactics; channel fit; this skill = generic cold start; indie-hacker = indie-specific
04 同仓库更多 Skills
youtube
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.
write-plan
Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY/SOLID/YAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs /plan-eng-review as an independent double-check before execution.
worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
web-perf
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.
verify
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
validate-idea
Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.