Communitygithub.com

冷启动难题

基于 Andrew Chen 的《冷启动难题》框架,启动并发展具有网络效应的产品。

冷启动难题 是什么?

该技能基于 Andrew Chen 的《冷启动难题》一书,为工程师和产品负责人提供了一套系统化的框架,用于启动和扩展那些依赖网络效应的产品——包括市场、社交应用、消息和协作工具。它解释了为什么网络效应最初是负债而非资产,并指导用户从构建一个最小的自给自足网络(原子网络)开始,解决“困难侧”的供给问题,然后用可复制的策略让相邻网络达到“引爆点”。框架涵盖五个阶段:冷启动、引爆点、逃逸速度、触及天花板和护城河。它支持 Claude Code、Cursor 等 AI 代理平台,提供从 0 到 10 的评分标准、具体的应用场景和伦理边界,帮助诊断增长瓶颈并制定行动计划。

兼容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/wondelai/skills/tree/HEAD/cold-start-problem

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

冷启动难题 是做什么的?

一个用于启动和扩展那些依赖网络效应生存或消亡的产品的框架——市场、社交应用、消息和协作工具——从 Andrew Chen 的《冷启动难题》中提炼而成。用它来启动那些在其他用户出现之前毫无价值的产品,逐个网络地安排增长,并驾驭五个阶段:冷启动、引爆点、逃逸速度、触及天花板和护城河。

核心原则

网络效应最初是负债,而非资产。 价值存在于用户之间的连接中,而在第一天,这种连接为零——让密集网络势不可挡的同一力量,也让空荡的网络毫无用处。你无法通过向整个市场发布来逃脱;你需要一次建立一个微小的、完整的、自给自足的网络,首先解决其困难侧,然后用一个可复制的策略让相邻的网络达到引爆点,直到整个市场跟随。

评分

目标:10/10。 根据以下原则,为网络化产品的发布计划和增长策略打分(0-10)。报告当前分数以及要达到 10/10 所需的具体改变。

  • 9-10: 有命名的原子网络,具有可衡量的神奇时刻,先解决了困难侧,有可复制的引爆策略,密度/流动性指标明确,有明确的天花板和护城河计划。
  • 7-8: 原子网络和困难侧焦点清晰,但引爆策略是临时的,或指标仍在追踪总数而非密度。
  • 5-6: 网络效应被承认,但发布目标是一个广泛的市场,并且两侧被平等对待。
  • 3-4: 通用的用户获取计划;网络思维仅限于“添加邀请并希望它传播”。
  • 0-2: 向所有人同时进行大爆炸式发布,追求虚荣注册量,没有困难侧策略,没有流动性衡量指标。

框架

1. 网络效应基础

核心概念: 网络化产品连接人与人——买家与卖家、创作者与观众、同事与同事——并随着合适的人加入而变得更有价值。网络效应有三种不同的形式:获取效应(网络自身吸引新用户)、参与效应(更多用户使每次会话更有价值)和经济效应(密度改善货币化和单位经济效益)。一个产品可能在其中一个方面很强,而在其他方面很弱。

为什么有效: 将“网络效应”视为一个单一的魔法属性,会掩盖增长的实际来源和中断点。梅特卡夫定律(价值随 n² 增长)过度简化了——它计算节点,而非活跃的、相关的连接,一百万个分散的用户可能还不如一个密集社区中的五千个用户有价值。每个大型网络实际上是一个网络的网络:Uber 是数百个城市级别的市场,Slack 是数百万个团队规模的网络。每个子网络的密度和质量胜过原始用户总数。

关键见解:

  • 三种效应是分离的:病毒式获取可能掩盖低迷的参与——下载量上升,但房间是空的。
  • 梅特卡夫定律计算节点;价值存在于活跃连接中——衡量密度,而非总数。
  • 反网络效应是真实存在的:在密集网络中加速增长的动态,在稀疏网络中会加速空虚。
  • 网络本身,而非功能集,才是护城河——竞争对手可以复制产品,但无法复制上面的人。
  • 总体指标会撒谎;按子网络(城市、团队、类别)细分每个指标以查看真实健康状况。

应用:

上下文应用示例
指标设计用密度衡量替换总数追踪每周活跃网络,而非注册用户
增长诊断将增长归因于三种效应病毒因子 vs. 会话频率 vs. 转化率,每个指标按网络细分
策略回顾将产品映射为网络的网络一个市场是每对城市-类别组成的一个网络

参见 references/case-studies.md 了解三个端到端的演练场景——一个 B2B 工具寻找其原子网络、一个服务市场在一个城市播种、一个社交应用从大爆炸式发布中恢复——当你需要完整的示例来建模计划时。

2. 冷启动:原子网络

核心概念: 原子网络是稳定且自给自足的最小网络——足够数量的合适人,使得产品交付其核心价值,并且该群体能自行回归。Slack 需要大约同一个团队内的三个用户,Zoom 需要两个,一个市场可能需要一个邮政编码或类别区域。选择一个网络,而不是一个市场,并为此小群体构建杀手级产品——即使它看起来小到没有规模。

为什么有效: 网络一次一个地成败。一个产品如果对一个社区中的五十个人完全有效,就证明了循环并可以复制;一个产品如果对五万个分散的用户半有效,则什么也证明不了,只能死于空虚。完整的小型网络还能暴露神奇时刻——即显示网络正在运行的体验(汽车到达、队友回复)——这成为后续每个网络的激活门槛。

关键见解:

  • 越小越好:找到产品能够工作的最小规模,然后为这个确切群体提供超值服务。
  • 严格限制第一个网络——一家公司、一个校园、一个社区、一个收藏家领域——这样密度就可以通过创始人的努力实现。
  • 精确定义神奇时刻并进行监测;将所有的扩展都限制在网络达到该时刻之后。
  • 为小网络打造的杀手级产品看起来像玩具(Facebook 在哈佛,eBay 的收藏品)——小众的外观是密度的代价。
  • 暂时手动填充空的一侧:创始人手动提供内容、库存或匹配,直到网络能够独立运作。

应用:

上下文应用示例
发布范围界定选择一个网络,而非一个市场“奥斯汀一家经纪公司的代理人,”而不是“美国住房市场”
激活定义并监测神奇时刻新成员发帖并在几分钟内收到队友回复
空侧手动补充缺失的供应创始人亲自完成前 100 个市场订单

伦理边界: 手动填充意味着在幕后做真正的工作——绝不捏造虚假用户、评论或活动来欺骗网络上的人。

在确定首次发布范围时,参见 references/atomic-networks.md——它包含 5 步最小规模推导、演员/动作/响应/时间神奇时刻模板、监测和零速率步骤、诚实手动填充规则、单人备用方案和发布清单。

3. 解决困难侧

核心概念: 每个网络都有一个困难侧——少数人完成了不成比例的工作,并且难以吸引和留住:卖家、创作者、司机、房东、组织者。他们有更好的替代选择和更高的期望,没有他们,容易侧会发现一个空产品。理解他们的动机——金钱、地位、效用——并为他们首先构建产品和经济学。

为什么有效: 容易侧只有在困难侧交付价值时才会出现,而不是之前。没有创作者的內容应用、没有供应的市场、没有设置它的组织者的协作工具——都是空房间。“为工具而来,为网络而留”是经典的困难侧楔子:一个单人工具(Instagram 的滤镜、OpenTable 的预订本)在网络存在之前,一个接一个地招募困难侧,然后网络使离开变得不可想象。

关键见解:

  • 通过完成的工作量来识别困难侧,而不是支付的金钱:在维基百科、YouTube 和大多数市场上,百分之几的用户创造了大部分价值。
  • 明确映射动机:金钱(司机、卖家)、地位(创作者、顶级评论者)、效用(无论如何都需要该工具的组织者)——每个都需要不同的产品投资。
  • 首先为困难侧构建专业工作流程和经济性;容易侧主要需要一个干净的消费者体验。
  • 早期补贴稀缺侧——担保、奖金、零费用——并公开补贴逐步取消的计划,以便信任在退出后仍然存在。
  • 早期的困难侧会迅速专业化:在第三个月,而不是第三年,计划提供强力工具、分析和付款改进。

应用:

上下文应用示例
市场播种在需求之前招募和补贴供应保证发布前八周清洁工收入
社交或内容应用用地位和影响力吸引创作者早期关注者优势、推荐、创作者基金
B2B 协作为组织者提供单人价值项目管理工具单独有用;邀请团队使其更好

伦理边界: 困难侧的经济性必须诚实——将发布补贴作为临时激励,绝不要在计划悄然降低的条款上建立人们的生计。

在设计供应侧获取和经济性时,参见 references/hard-side.md——它将金钱/地位/效用动机映射到产品投资,并详细说明了三个命名的策略(工具优先、内容优先、补贴)。

4. 引爆点和逃逸速度

核心概念: 一旦第一个原子网络成功,增长就变成了一个可复制的策略,用于引爆下一个网络,再下一个——每次发布的成本都比上一次低。核心引爆工具:仅限邀请机制(策展 + 稀缺性 + 社会证明)、付费启动(补贴、担保、预先承诺的供应)以及影响者或社区播种。达到引爆点之后,逃逸速度不是一个里程碑,而是一种运营模式:持续放大获取、参与和经济效应。

为什么有效: 仅限邀请发布看似排他,但通过设计建立了密度——每个受邀者到达时,内部至少有一个连接,网络沿着真实社交图复制,稀缺性制造了拉动下一批用户的社会证明。付费启动将钱转化为密度,这是竞争对手无法复制的一项资产。大爆炸式发布则相反:Google+ 将数亿注册用户推入空房间,而脆弱的网络从未留存。

关键见解:

  • 仅限邀请同时做三件事:策展早期文化、制造稀缺性热度、导入每个用户的社交图。
  • 补贴是网络 CAC:花钱制造流动性,衡量每个活跃网络的成本,按公布的时间表逐步取消。
  • 大爆炸式发布是典型反模式——快速填充,脆弱网络;新闻高峰落在一片空虚之上,永不回归。
  • 达到引爆点后,将三种力量作为命名的工作流运行:获取(病毒循环、推荐)、参与(增强循环、重新参与)、经济(转化、补贴取消、定价)。
  • 每个达到引爆点的网络都降低了下一个的成本:溢出知名度、可移植的策略、可重用的供应关系。

应用:

上下文应用示例
消费者发布仅限邀请并附推荐树等待列表加每个活跃用户五个邀请;追踪邀请图密度
市场城市 #2付费制造流动性90天司机收入保证,随着填充率上升逐步取消
引爆后增长将三种力量作为工作流配备人员推荐循环、摘要重新参与、抽成比例优化

伦理边界: 稀缺性和排他性必须是真实的——虚假的等待列表和制造的“限量名额”是欺骗,而非策略。

在规划第二个及以后的网络时,参见 references/tipping-playbooks.md——包含仅限邀请和推荐树机制、付费启动和供应预承诺策略、市场选择、反模式以及作为门槛的流动性指标。

5. 天花板和护城河

核心概念: 增长总会停滞。火箭曲线是 S 曲线的序列,每条曲线都会遇到天花板:市场饱和、渠道退化(CAC 上升、横幅盲点、病毒疲劳)、困难侧反抗以及规模带来的质量崩溃——垃圾信息、过度拥挤、情境崩溃。护城河就是网络本身:保护困难侧,预期竞争对手会挑选你最密集的细分市场,并记住捆绑可以填充容易侧,但很少能赢得困难侧。

为什么有效: 每个获取渠道都会随着受众习惯和竞争对手涌入而退化——最初的横幅广告点击率是两位数;今天的平均值是百分比的几分之一。网络也会从内部退化:规模吸引垃圾信息,并崩溃了使早期网络有价值的亲密情境,因此质量工作变成了增长工作。网络之间的竞争是不对称的:挑战者通过将原子网络纪律应用于一个未被充分服务的细分领域来获胜——而这正是现有企业被瓦解的方式。

关键见解:

  • 将增长绘制为叠加的 S 曲线;在当前曲线变平之前,启动下一条曲线(地理、细分、用例、产品)。
  • CAC 上升和病毒疲劳是规律,而非失败——在当前渠道仍然有效时,规划下一个渠道。
  • 警惕困难侧反抗信号:抽成比例投诉、多宿主、有组织的抗议——困难侧先离开,并带走网络。
  • 质量干预——策展、排名、验证、反垃圾信息、子群组——在规模上是增长投资,而非成本中心。
  • 通过过度服务你最密集的细分领域来防御 cherry-picking;这正是大卫攻击歌利亚的地方。
  • 捆绑购买分销,而非忠诚——它填充容易侧的座位,而深度参与则留给了掌握困难侧的人。

应用:

上下文应用示例
增长停滞诊断哪个天花板先被击中按网络区分饱和、CAC 上升和质量退化流失
规模质量资助信任和策展循环评级、排名、验证、垃圾信息过滤

…

[为完整翻译而截断]

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

wondelai/37signals-way

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

wondelai/blue-ocean-strategy

Create uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "eliminate-reduce-raise-create", or "uncontested market". Also trigger when comparing pricing strategies, exploring new market categories, finding underserved customer segments, or asking how to stop competing on price. Covers the Four Actions Framework, buyer utility map, and value-cost trade-offs. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.

wondelai/clean-architecture

Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters", "hexagonal architecture", "use case boundary", "onion architecture", "screaming architecture", or "framework independence". Also trigger when decoupling business logic from databases or frameworks, defining module boundaries, or debating where to put business rules. Covers component principles, boundaries, and SOLID. For code quality, see clean-code. For domain modeling, see domain-driven-design.

wondelai/clean-code

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

wondelai/contagious

Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "viral loop", "referral program", or "organic growth". Also trigger when designing shareable features, crafting social media campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.

wondelai/continuous-discovery

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", or "outcome-based roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or connecting discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.

wondelai/cro-methodology

Audit websites and landing pages for conversion issues and design evidence-based A/B tests. Use when the user mentions "landing page isnt converting", "conversion rate", "A/B test", "why visitors leave", "objection handling", "bounce rate", "split testing", or "conversion funnel". Also trigger when diagnosing why signups are low, designing experiment hypotheses, or auditing checkout flows for friction points. Covers funnel mapping, persuasion assets, and objection/counter-objection frameworks. For overall marketing strategy, see one-page-marketing. For usability issues, see ux-heuristics.

wondelai/crossing-the-chasm

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs. mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", or "pragmatist buyers". Also trigger when a startup has early traction but struggles to grow beyond initial users, or when planning go-to-market for technical products. Covers D-Day analogy, bowling-pin strategy, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.

wondelai/ddia-systems

Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", or "LSM tree vs B-tree". Also trigger when choosing between SQL and NoSQL, designing data pipelines, or debugging distributed system consistency issues. Covers data models, batch/stream processing, and distributed consensus. For system design, see system-design. For resilience, see release-it.

wondelai/design-everyday-things

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "fault tolerance", "mental model", "mapping", or "seven stages of action". Also trigger when diagnosing why users make mistakes, reducing product complexity, or improving error messages and feedback systems. Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design.

wondelai/design-sprint

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.

wondelai/domain-driven-design

Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user mentions "domain modeling", "bounded context", "aggregate root", "ubiquitous language", "anti-corruption layer", "context mapping", "domain events", or "strategic design". Also trigger when splitting a monolith into services, defining microservice boundaries, or aligning code structure with business processes. Covers entities vs value objects, domain events, and context mapping strategies. For architecture layers, see clean-architecture. For complexity, see software-design-philosophy.

wondelai/drive-motivation

Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "team incentives", "autonomy", "mastery", "purpose-driven", "employee engagement", or "reward systems". Also trigger when designing onboarding progression systems, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retention.

wondelai/high-perf-browser

Optimize web performance through network protocols, resource loading, and browser rendering internals. Use when the user mentions "page load speed", "Core Web Vitals", "HTTP/2", "resource hints", "network latency", "render blocking", "TCP optimization", "service worker", or "critical rendering path". Also trigger when diagnosing slow page loads, optimizing time to first byte, choosing between WebSocket and SSE, or reducing bundle sizes. Covers TCP/TLS optimization, caching strategies, WebSocket/SSE, and protocol selection. For UI visual performance, see refactoring-ui. For font loading, see web-typography.

wondelai/hooked-ux

Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "engagement loops", "habit formation", "push notifications", "variable rewards", "daily active users", "habit zone", or "user retention loops". Also trigger when designing notification strategies, building streaks or progress systems, or analyzing why users stop using a product after initial signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.

wondelai/hundred-million-offers

Create irresistible offers using the Value Equation, bonus stacking, risk-reversing guarantees, and ethical scarcity. Use when the user mentions "pricing strategy", "irresistible offer", "bonuses and guarantees", "value-to-price ratio", "offer naming", "grand slam offer", "guarantee strategy", or "premium pricing justification". Also trigger when packaging products for higher perceived value, designing money-back guarantees, or structuring pricing tiers to maximize conversions. Covers the MAGIC naming formula and starving-crowd targeting. For product positioning, see obviously-awesome. For outbound sales, see predictable-revenue.

wondelai/improve-retention

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users drop off", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", "user activation", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users stop after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

wondelai/influence-psychology

Apply the six principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity) to product design, copy, and sales. Use when the user mentions "social proof", "persuasive copy", "why users dont convert", "ethical persuasion", "reciprocity", "scarcity tactics", or "commitment and consistency". Also trigger when designing testimonial sections, crafting urgency messaging, or improving trust signals on landing pages. For deal negotiation tactics, see negotiation. For viral word-of-mouth, see contagious.

wondelai/inspired-product

Build empowered product teams using discovery and delivery dual-track. Use when the user mentions "product discovery", "empowered teams", "feature factory", "product roadmap", "opportunity assessment", "product vision", "product-led growth", or "discovery vs delivery". Also trigger when restructuring product teams away from output-driven models, setting product strategy, or defining what to build next based on outcomes. Covers product discovery techniques, team structure, and continuous value delivery. For customer interviews, see mom-test. For ongoing discovery systems, see continuous-discovery.

wondelai/ios-hig-design

Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad layout", "SwiftUI", "UIKit", "Dynamic Island", "safe areas", "HIG compliance", "SF Symbols", "haptic feedback", or "iOS accessibility". Also trigger when building tab bars, navigation stacks, sheets, or modals for iOS, implementing dark mode, or adapting layouts for different screen sizes. Covers navigation patterns, accessibility, SF Symbols, and platform conventions. For general UI polish, see refactoring-ui. For affordance design, see design-everyday-things.

相关技能