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," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." 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.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and positioning.
Identify:
| 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 |
Low-cost ways to find and reach users who are already expressing need. Use when Product Hunt, directories, or forums are not enough.
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) |
| 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.
| 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.
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.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
日本語の概要は準備中です。原文の説明を表示しています。