agentleFS
brainbytes-devbrainbytes-dev/everything-claude-marketing/skills/growth/viral-mechanics/SKILL.md

viral-mechanics

Skill9 starsChanged 8 months agoMITView on GitHub

Design viral mechanics and shareable experiences that drive organic distribution. Use when building features or campaigns designed to spread.

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a "wow moment" that users can't help but talk about.

    line 57
  2. Distinctive:

    Create something people want to share about themselves (identity expression).

    line 79
  3. Distinctive:

    Don't require login to view shared content (let recipients see value first).

    line 139
  4. Distinctive:

    When we care, we share. High-arousal emotions drive sharing.

    line 157
  5. Distinctive:

    Application: Create content that provokes awe, surprise, or excitement.

    line 160
  6. Distinctive:

    If it's built to show, it's built to grow.

    line 163
  7. Distinctive:

    Application: Create genuinely helpful tools, guides, calculators, templates.

    line 169
  8. Distinctive:

    Must be valuable enough that recipients forward to colleagues/friends.

    line 220
  9. Distinctive:

    Before launching a viral mechanic or campaign:

    line 244

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Viral Mechanics Design

When to Activate

  • Designing product features intended to drive organic sharing and distribution
  • Planning campaigns designed to spread through word-of-mouth or social sharing
  • Building shareable content experiences (tools, calculators, quizzes, reports)
  • Analyzing why something went viral and how to replicate it
  • Increasing organic reach without proportional spend increases
  • Making an existing product or feature more shareable

First Questions

  1. What type of virality are you designing for? (Inherent, collaborative, word-of-mouth, incentivized, manufactured)
  2. Who is the sharer and who is the audience? (Users sharing with peers, users sharing publicly, company sharing content)
  3. What is the natural sharing moment in your product or campaign?
  4. What platform(s) will the sharing happen on? (Email, SMS, social media, in-person)
  5. What does the recipient experience when they receive the share? (Landing page, app invite, content)
  6. What is the desired action from the recipient? (Sign up, view, purchase, reshare)

Types of Virality

1. Inherent Virality

The product requires others to be useful. Sharing IS using.

Examples: WhatsApp (need contacts), Venmo (need payment recipients), Google Docs (need collaborators), Zoom (need meeting attendees)

Design principles:

  • The core use case involves other people.
  • Non-users must interact with the product to complete the user's task.
  • The non-user experience is good enough to convert them.
  • Friction to join is extremely low.

2. Collaborative Virality

The product becomes more valuable when used with others, encouraging invitations.

Examples: Slack (better with your whole team), Figma (collaborative design), Notion (shared workspaces), Miro (team whiteboarding)

Design principles:

  • Show the user what they're missing by working alone.
  • Make inviting teammates part of the core workflow, not a side action.
  • Give the inviter and the invitee immediate collaborative value.
  • Build features that specifically require collaboration.

3. Word-of-Mouth Virality

Users voluntarily tell others because the experience is remarkable.

Examples: Tesla (the driving experience), Airbnb (unique stays), ChatGPT (mind-blowing outputs), Superhuman (email speed)

Design principles:

  • Create a "wow moment" that users can't help but talk about.
  • Make the product's value visible and demonstrable.
  • Give users a story to tell (not just "it's good" but "you won't believe what it did").
  • The product must be genuinely exceptional — you can't manufacture word-of-mouth for a mediocre product.

4. Incentivized Virality

Users share because they receive a tangible reward for doing so.

Examples: Dropbox (free storage), Uber (ride credits), Robinhood (free stock)

Design principles:

  • Reward must be valuable enough to motivate but not so large it attracts gamers.
  • Two-sided rewards outperform one-sided.
  • Reward should be product-related, not cash (strengthens product engagement).
  • See the referral-programs skill for detailed incentive design.

5. Manufactured / Campaign Virality

Deliberately designed content or experiences intended to spread.

Examples: Spotify Wrapped, Wordle sharing grid, ALS Ice Bucket Challenge, year-in-review campaigns

Design principles:

  • Create something people want to share about themselves (identity expression).
  • Make sharing effortless (pre-formatted for the target platform).
  • Include a hook for the viewer (not just interesting to the sharer).
  • Build in a call-to-action for viewers to create their own version.

Viral Coefficient and Cycle Time

Viral Coefficient (K-Factor)

K = invitations per user × conversion rate per invitation

  • K > 1: True viral growth (exponential). Extremely rare and usually temporary.
  • K = 0.5-1.0: Strong viral assist. Significantly reduces CAC.
  • K = 0.2-0.5: Meaningful but won't drive growth alone.
  • K < 0.2: Marginal viral contribution.

Cycle Time

How long between a user joining and their invited users joining.

Cycle TimeImpact
Hours (WhatsApp, TikTok)Explosive growth potential
Days (Calendly, Loom)Rapid, sustained growth
Weeks (Slack team adoption)Steady but reliable
Months (B2B enterprise)Too slow for viral to be primary driver

The Compound Effect

Growth at period n = Initial users × K^n (simplified, for K < 1 converges)

With K = 0.5 and 1,000 initial users:

  • After loop 1: 1,000 + 500 = 1,500
  • After loop 2: 1,500 + 250 = 1,750
  • After loop 3: 1,750 + 125 = 1,875
  • Converges to: 2,000 total (effectively doubles your acquisition)

Even K = 0.3 means your paid acquisition is amplified by 43%. This is why viral mechanics matter even when K < 1.

Designing for Shareability

The Shareability Checklist

For any feature, content, or experience, it should satisfy at least 3 of these:

  1. Makes the sharer look good. (Smart, funny, successful, interesting, caring)
  2. Is useful to the recipient. (Tool, information, entertainment, opportunity)
  3. Is easy to share. (One click, pre-formatted, native to the platform)
  4. Creates curiosity. (The recipient wants to know more or try it themselves)
  5. Is visual. (Images and video share better than text links)
  6. Is timely. (Connected to a current event, trend, or moment)
  7. Has a clear CTA for the viewer. (Create your own, sign up, try it)

Share Triggers in Products

  • Achievement moments: User completes a goal, hits a milestone, gets a result.
  • Creation moments: User creates something they're proud of (design, report, playlist).
  • Discovery moments: User finds something surprising or valuable.
  • Social moments: User interacts with others through the product.
  • Identity moments: Product reflects something about who the user is.

Reducing Sharing Friction

  • Pre-generate the shareable content (image, text, link).
  • Optimize for the platform (correct image dimensions, character counts).
  • Offer share options: Copy link, share to specific platforms, QR code.
  • Don't require login to view shared content (let recipients see value first).
  • Make the shared artifact valuable even without context.

The STEPPS Framework (Jonah Berger)

Six principles that drive sharing and word-of-mouth. Use as a design checklist.

Social Currency

People share things that make them look good.

  • Application: Make users feel like insiders. Give them exclusive information. Create scarcity. Let them show off achievements.
  • Example: Spotify Wrapped lets people show their unique music taste. "I was in the top 1% of listeners."

Triggers

Things that are top-of-mind get talked about.

  • Application: Link your product to something people encounter frequently. Create associations with common triggers.
  • Example: KitKat linked itself to coffee breaks. Every coffee break = a trigger to think about KitKat.

Emotion

When we care, we share. High-arousal emotions drive sharing.

  • High arousal (drives sharing): Awe, excitement, humor, anger, anxiety.
  • Low arousal (doesn't drive sharing): Sadness, contentment.
  • Application: Create content that provokes awe, surprise, or excitement. Avoid purely informational content if you want shares.

Public

If it's built to show, it's built to grow.

  • Application: Make product usage visible. Branded sharing (Sent from iPhone, Created with Canva). Public leaderboards. Visible badges.
  • Example: Livestrong wristbands. AirPods' distinctive design. Branded watermarks on free-tier content.

Practical Value

People share useful information.

  • Application: Create genuinely helpful tools, guides, calculators, templates. Package expertise into shareable formats.
  • Example: A mortgage calculator that generates a shareable result. A salary benchmarking tool. A savings calculator.

Stories

People share narratives, not facts.

  • Application: Embed your product/brand in a story worth telling. Create a narrative arc. Make the product a character in the story, not the whole story.
  • Example: Blendtec's "Will It Blend?" — the story is the ridiculous thing being blended, but the product (blender) is the hero.

Viral Campaign Examples and Analysis

Spotify Wrapped

  • Why it works: Social Currency (show music taste), Identity (it's about YOU), Public (designed for Instagram Stories), Annual ritual (trigger), Easy to share (pre-formatted for every platform).
  • Replicable elements: Year-in-review for any product. Personalized statistics. Platform-optimized share cards. Annual cadence builds anticipation.

Wordle Sharing Grid

  • Why it works: Social Currency (show you're smart), Public (visible emoji grid), Practical Value (here's a fun game), Low friction (copy-paste), Conversation starter.
  • Replicable elements: Abstracted results that are intriguing without spoiling. Daily cadence. Simple visual format optimized for text-based platforms.

Duolingo (Owl Notifications / TikTok Persona)

  • Why it works: Emotion (humor, slight anxiety), Public (everyone knows the owl), Stories (the owl is a character), User-generated memes expand reach.
  • Replicable elements: Brand character with personality. Lean into memes. Let users co-create the narrative.

Platform-Specific Viral Mechanics

X/Twitter

  • Quote tweets and threads drive distribution.
  • Controversial or surprising takes get engagement.
  • Visual content (images, video) dramatically outperforms text-only.
  • Optimal for B2B, tech, media, and opinion content.

Instagram / Stories

  • Visual-first. Shareable cards, infographics, carousel posts.
  • Stories sharing (repost, mention) is the primary viral mechanic.
  • Designed-for-sharing templates (fill in the blank, this or that, rankings).
  • Optimal for D2C, lifestyle, personal brand.

TikTok

  • Duets and stitches are the native viral mechanic.
  • Trends and sounds create participation loops.
  • Authenticity outperforms polish.
  • Hook in first 1-3 seconds or lose the viewer.
  • Optimal for reaching younger demographics, trend-based campaigns.

LinkedIn

  • Personal stories and contrarian professional takes drive engagement.
  • Carousel PDFs and document posts have high engagement.
  • Comments drive distribution (algorithm rewards conversations).
  • Optimal for B2B, HR, leadership, professional development.

Email / SMS

  • Forwarding is the viral mechanic.
  • Must be valuable enough that recipients forward to colleagues/friends.
  • Include "forward to a friend" CTA explicitly.
  • Optimal for newsletters, curated content, exclusive offers.

Measurement Framework

Core Viral Metrics

MetricFormulaTarget
K-FactorInvitations × Conversion rate> 0.2 for meaningful impact
Cycle TimeAvg days from user join to invitee join< 7 days ideal
Share Rate% of users who share at least once> 10% for in-product sharing
Viral Acquisition %Viral-sourced users / Total new usersGrowing over time
Amplification RatioReshares or secondary shares per original share> 1 = content is truly viral

Tracking Implementation

  • Unique referral/share links for attribution.
  • UTM parameters for campaign-based sharing.
  • Share event tracking in analytics (who shared, where, when).
  • Downstream conversion tracking (did the shared link lead to sign-up/purchase?).
  • Cohort quality comparison (viral-acquired vs. paid-acquired retention and LTV).

Quality Gate

Before launching a viral mechanic or campaign:

  • Does the shareable content/experience satisfy at least 3 items on the shareability checklist?
  • Is sharing a natural part of the user experience (not forced or awkward)?
  • Is the sharing friction minimal (1-2 actions maximum)?
  • Is the experience for the recipient compelling (not just spam)?
  • Is the shareable content optimized for the target platform(s)?
  • Have you defined and instrumented K-factor, cycle time, and share rate metrics?
  • Does the viral mechanic serve the user's interests, not just the company's growth goals?
  • Have you tested the sharing flow end-to-end (share, receive, view, convert)?
  • Is there a clear call-to-action for the recipient?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.