contagious
The contagious skill applies Jonah Berger's STEPPS framework to engineer word-of-mouth growth by identifying which psychological drivers of sharing are present in a product, campaign, or idea. It rates content or features on six dimensions, Social Currency, Triggers, Emotion, Public visibility, Practical Value, and Stories, then recommends specific improvements to maximize viral potential. Use when designing shareable products, analyzing why content spreads, building referral programs, or crafting campaigns intended to spread through peer recommendation rather than paid distribution.
git clone --depth 1 https://github.com/wondelai/skills /tmp/contagious && cp -r /tmp/contagious/plugins/marketing-cro/skills/contagious ~/.claude/skills/contagiousSKILL.md
# Word-of-Mouth & Virality Framework A framework for engineering word-of-mouth and making products, ideas, and content contagious, based on Jonah Berger's research into why things catch on. Use it to design shareability into products, campaigns, and content instead of hoping for luck. ## Core Principle **Virality is not born — it is engineered.** Products spread because they were designed — consciously or not — to be shared. Only 7% of word-of-mouth happens online; the other 93% happens in offline conversations, so virality is about the psychology of sharing, not social media mechanics. Those psychological patterns are predictable and can be engineered into anything using the STEPPS framework. See: [references/word-of-mouth.md](references/word-of-mouth.md) when the brief over-indexes on social media — it makes the offline-vs-online case, lists conversation triggers, and gives a WOM measurement/audit method. ## Scoring **Goal: 10/10.** Score each of the six STEPPS drivers (the six Quick Diagnostic rows) — **0** absent, **1** present but weak, **2** strong and deliberate — for a raw 0-12, then map: 11-12 -> 10, 9-10 -> 8-9, 6-8 -> 6-7, 3-5 -> 4-5, 0-2 -> <=3. Bands: - **9-10** — three or more drivers at strength 2, at least one of them Public or Social Currency (the self-propagating ones), and the brand survives the Trojan Horse test. - **6-8** — two drivers genuinely strong, but spread still leans on paid reach or product quality alone. - **<=5** — at most one weak driver; sharing is incidental, not engineered. Report the raw count, the mapped score, and the specific driver(s) to raise next to reach 10/10. ## STEPPS Overview **Not a checklist — a multiplier.** Each principle independently increases sharing; the most contagious ideas activate several at once, but even one or two done well dramatically increase word-of-mouth. | Principle | Core Question | Sharing Driver | |-----------|--------------|----------------| | **S — Social Currency** | Does sharing it make people look good? | Self-enhancement | | **T — Triggers** | What in the environment reminds people of it? | Top-of-mind accessibility | | **E — Emotion** | Does it fire up high-arousal feelings? | Physiological arousal | | **P — Public** | Can others see people using it? | Observational learning | | **P — Practical Value** | Is it useful enough to pass along? | Altruism and helpfulness | | **S — Stories** | Is the brand embedded in a narrative? | Entertainment and identity | ## The STEPPS Framework ### 1. Social Currency **Core concept:** People share things that make them look good — smart, cool, in-the-know. Make people feel like insiders and they'll spread it to boost their own image. **Why it works:** Sharing is self-presentation — listeners infer the sharer's traits from what they pass on, so people curate shares the way they curate clothes. Mechanism: give the sharer a payoff in status or identity and you outsource your marketing to their ego. **Key insights:** - **Remarkability** — surprising, novel, or extreme things make the sharer seem interesting; "Did you know...?" is a powerful sharing trigger - **Game mechanics** — leaderboards, badges, and status tiers create visible accomplishments people want to display - **Exclusivity and scarcity** — secret menus and invite-only access give people "insider knowledge" to share - **Inner remarkability** — even mundane products have a remarkable angle; it's framing, not the product **Product applications:** | Context | Application | Example | |---------|------------|---------| | Content platform | Insider statistics or year-in-review | Spotify Wrapped | | Mobile app | Shareable accomplishment cards | Duolingo streak badges | | B2B product | Benchmarking data users want to cite | HubSpot State of Marketing report | **Copy patterns:** - "Most people don't know that..." - "You're one of the first to try..." - "You've unlocked [achievement]..." **Ethical boundary:** Create real insider value, not false scarcity or manufactured exclusivity that breeds toxicity. See: [references/social-currency.md](references/social-currency.md) when a product feels unremarkable — it has the inner-remarkability exercise, game-mechanic design, exclusivity types, and a scored audit. ### 2. Triggers **Core concept:** Top-of-mind means tip-of-tongue. Link your product to environmental cues — sights, sounds, times, routines — so everyday life keeps reminding people to talk about you. **Why it works:** Most word-of-mouth is driven not by excitement but by whatever happens to be top-of-mind mid-conversation; a product linked to a frequent cue gets mentioned more because it's more accessible in memory. **Key insights:** - **Frequency beats strength** — a daily trigger (coffee) outperforms a powerful but rare one (a holiday); Kit Kat linked itself to coffee breaks - **Habitat matters** — map where and when people encounter contexts related to your product - **Competitive triggers** — link a competitor's moment to your own brand - **Ongoing vs. temporary** — persistent environmental triggers sustain word-of-mouth; event triggers only spike it **Product applications:** | Context | Application | Example | |---------|------------|---------| | Food/Beverage | Link to a daily habit | Kit Kat + coffee break | | Productivity tool | Tie to a recurring workflow moment | "Every Monday standup..." | | Financial product | Link to payday | "Every time you get paid..." | **Copy patterns:** - "Every time you [frequent activity], think of..." - "Next time you [daily habit]..." - "It's [day/time] — time for..." **Ethical boundary:** Build genuine, helpful associations — hijacking sensitive contexts (grief, health scares) as triggers backfires. See: [references/triggers.md](references/triggers.md) when picking a cue to attach to — it has the habitat-analysis worksheet, the frequency matrix, and the 4-step trigger design process. ### 3. Emotion **Core concept:** When we care, we share. High-arousal e
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", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
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", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
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)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.
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", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying 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.
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", "conversion funnel", "increase signups", or "people add to cart but dont buy". 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.
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", "pragmatist buyers", "growth stalled after early adopters", or "our go-to-market plan". Also trigger when planning go-to-market for a technical product. Covers the D-Day analogy, bowling-pin strategy, the tornado, and positioning against incumbents. For product positioning, see obviously-awesome. For new market creation, see blue-ocean-strategy.
Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID transactions", "eventual consistency", "my queries are slow at scale", or "data is inconsistent across replicas". Also trigger when choosing a datastore, 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.