Skip to main content
ClaudeWave
Skill1.3k repo starsupdated 2d ago

made-to-stick

# Made to Stick This Claude Code skill applies the SUCCESs framework (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to evaluate and improve messaging that needs to stick in audiences' minds. Use it when crafting taglines, value propositions, pitch decks, or presentations where clarity and memorability matter, or when communication isn't landing due to complexity or the "curse of knowledge" that makes experts forget how to explain ideas to newcomers.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/wondelai/skills /tmp/made-to-stick && cp -r /tmp/made-to-stick/made-to-stick ~/.claude/skills/made-to-stick
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# Made to Stick Framework

A framework for crafting ideas and messages that are understood, remembered, and drive lasting action. Based on decades of research into why some ideas survive and others die.

## Core Principle

**The Curse of Knowledge is the single greatest barrier to effective communication.** Once we know something, we can't imagine not knowing it—which makes us bad at explaining our ideas to others. Sticky ideas aren't born, they're made: the SUCCESs framework provides six principles that make any idea more memorable and impactful.

## Scoring

**Goal: 10/10.** Rate any messaging (copy, presentations, campaigns, onboarding) 0-10 against the SUCCESs principles: simple, surprising, concrete, credible, emotional, and wrapped in a story scores 10; forgettable communication scores low. Always state the current score and the specific improvements needed to reach 10/10.

## The SUCCESs Framework

**S**imple · **U**nexpected · **C**oncrete · **C**redible · **E**motional · **S**tories

**Not a checklist—a toolkit.** Not every sticky idea uses all six, but the stickiest ideas tend to use most of them. **Ethical boundary:** use SUCCESs to make true ideas stick—never to make false claims memorable.

### 1. Simple

**Core concept:** Find the core of the idea and share it compactly. Simple ≠ dumbed down—it means ruthless prioritization: "if you say three things, you say nothing."

**The Commander's Intent:** if everything else goes wrong, what ONE thing must we accomplish? For messaging: if people remember ONE thing about your product, what should it be? **The inverted pyramid:** lead with the most important thing; readers who stop anywhere still got the core.

**Techniques for simplicity:**

| Technique | How It Works | Example |
|-----------|-------------|---------|
| **Core message** | Strip to the essential | Southwest: "THE low-fare airline" |
| **Analogy** | Explain new via known | "It's like Uber for dog walking" |
| **Generative** | Core idea that generates behavior | "Names, names, names" (local newspaper motto) |

**Application to product messaging:**

| Before (Complex) | After (Simple) |
|-------------------|----------------|
| "AI-powered, cloud-native customer engagement platform with omnichannel capabilities" | "Talk to all your customers in one place" |
| "We leverage machine learning algorithms to optimize conversion funnels" | "We find why visitors don't buy and fix it" |
| "Enterprise-grade project management with Gantt charts, resource allocation..." | "The simplest way to manage projects" |

**The test:** Can you explain it to a smart 12-year-old? **Warning:** don't simplify into emptiness—"we make the world better" is simple but meaningless.

See: [references/simple.md](references/simple.md) for simplification exercises and templates.

### 2. Unexpected

**Core concept:** Get attention by breaking patterns (surprise); hold attention by creating curiosity gaps (interest). The surprise must connect to the core message—identify the counterintuitive implication and communicate that.

**Example surprises:**

| Category | Expected | Unexpected (Sticky) |
|----------|----------|---------------------|
| **Product launch** | "Introducing our new feature" | "We removed your favorite feature. Here's why." |
| **Statistics** | "Obesity is growing" | "A bag of movie popcorn has more fat than a bacon-and-eggs breakfast, Big Mac and fries, and steak dinner — combined" |
| **Value prop** | "Save money on insurance" | "15 minutes could save you 15%" (specific, unexpected) |

**Creating curiosity gaps** — open a gap in knowledge, create the desire to fill it:

| Technique | How It Works | Example |
|-----------|-------------|---------|
| **Question** | Ask what they don't know | "What's the #1 reason startups fail?" |
| **Prediction** | Ask them to predict | "How many X do you think...?" |
| **Mystery** | Present a puzzle, delay the resolution | "Nordstrom once refunded a set of tires. They don't sell tires." |
| **Challenge** | Violate assumptions | "Everything you know about X is wrong" |

**Anti-pattern:** Gimmicky surprise without substance.

See: [references/unexpected.md](references/unexpected.md) for pattern-breaking techniques.

### 3. Concrete

**Core concept:** Use sensory language and specific details instead of abstract concepts. Abstraction kills memorability; the more concrete and specific the idea, the stickier it becomes.

**Abstract vs. Concrete:**

| Abstract | Concrete |
|----------|----------|
| "Improve customer experience" | "Customers get their order in 30 minutes, still hot" |
| "Increase engagement" | "Users open the app 8 times a day" |
| "Optimize efficiency" | "Reduce report generation from 4 hours to 10 minutes" |
| "World-class support" | "Call us and a human answers in under 60 seconds" |
| "Scalable solution" | "Handle 10,000 users on day one without code changes" |

**The Velcro theory of memory:** concrete ideas have more "hooks"—"bicycle" is easier to remember than "vehicle" because you can picture it.

**Techniques for concreteness:**

| Technique | How It Works | Example |
|-----------|-------------|---------|
| **Specific numbers** | Replace "a lot" with exact figures | "2,347 customers" not "thousands" |
| **Sensory language** | Engage senses | "Crispy, not crunchy" |
| **Concrete example** | Replace category with instance | "Like John, a 35-year-old teacher in Denver" |
| **Before/after** | Tangible transformation | "Before: 4 hours. After: 10 minutes." |

**Application:** features → outcomes; percentages → real numbers ("saves 40%" → "saves 16 hours/month"); categories → specific examples ("restaurants" → "pizza shops in Brooklyn"); demos > feature lists.

See: [references/concrete.md](references/concrete.md) for concreteness exercises.

### 4. Credible

**Core concept:** Help people believe your idea using external credibility (authorities, credentials) and internal credibility (vivid details, human-scale statistics, testable claims)—inter
37signals-waySkill

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.

blue-ocean-strategySkill

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.

clean-architectureSkill

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.

clean-codeSkill

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.

contagiousSkill

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.

continuous-discoverySkill

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.

cro-methodologySkill

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.

crossing-the-chasmSkill

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.