Skip to main content
ClaudeWave
Skill1.3k repo starsupdated yesterday

influence-psychology

This Claude Code skill applies Robert Cialdini's six principles of influence (reciprocity, commitment, social proof, authority, liking, scarcity) to optimize product design, copy, and sales messaging. Use it when designing persuasive elements like landing pages, testimonial sections, urgency messaging, or trust signals, or when addressing conversion challenges and ethical persuasion questions.

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

SKILL.md

# Influence Psychology Framework

Framework for applying the science of persuasion ethically and effectively — six decades of research into why people say "yes."

## Core Principle

**People don't make decisions rationally — they use mental shortcuts (heuristics) that can be triggered to influence behavior.** These shortcuts evolved because they're usually reliable, but they can also be exploited. Understanding them lets you design products, messaging, and experiences that align with how people actually decide.

## Scoring

**Goal: 10/10.** When reviewing or creating persuasive elements (features, copy, flows, campaigns), rate them 0-10 based on adherence to the principles below. A 10/10 means ethical, effective application of influence psychology; lower scores indicate missed opportunities or ethical concerns. Always provide the current score and specific improvements needed to reach 10/10.

## The Seven Principles of Influence

### 1. Reciprocity

**Core concept:** People feel obligated to give back to those who have given to them first.

**Why it works:** Humans are wired to avoid being indebted — the obligation to repay can overpower personal preference, and the return favor often exceeds the original gift.

**Key insights:**
- The gift must come first (before the request)
- Unexpected, personalized gifts beat expected, generic ones
- Even small gifts create obligation

**Product applications:**

| Context | Reciprocity Trigger | Example |
|---------|---------------------|---------|
| **Free trials** | Full access first, then ask to pay | Spotify Premium trial → subscription |
| **Content marketing** | Value upfront (guides, tools) | HubSpot free CRM → paid tools |
| **Referral programs** | Reward both referrer and referee | Dropbox: both get extra storage |

**Copy patterns:**
- "Here's a gift for you..." (before asking)
- "As a thank you for signing up..."
- "We noticed you needed help with X, so we..."

**Ethical boundary:** Give genuine value — don't create artificial debts or exploit obligation.

See: [references/reciprocity.md](references/reciprocity.md) for reciprocity techniques and case studies.

### 2. Commitment & Consistency

**Core concept:** People want to be consistent with their past statements, beliefs, and actions.

**Why it works:** Inconsistency is psychologically uncomfortable; once we take a stand, personal and interpersonal pressure pushes us to behave consistently with it.

**Key insights:**
- Small initial commitments lead to larger ones (foot-in-the-door)
- Public > private; written > verbal; active (user-generated) > passive
- Self-perception: we infer our attitudes from our behavior

**Product applications:**

| Context | Commitment Trigger | Example |
|---------|-------------------|---------|
| **Onboarding** | Easy yes, then larger asks | Duolingo: "Can you commit to 5 min/day?" |
| **Goal setting** | User publicly states a goal | Strava: "I want to run 50km this month" |
| **Habit formation** | Track streaks publicly | Snapchat streaks, GitHub contributions |

**Copy patterns:**
- "What's your biggest challenge with X?" (commitment to a problem)
- "How much would you like to save per month?" (numerical commitment)
- "You said you wanted to achieve X. Let's start with..."

**Onboarding sequence:** micro-commitment ("What brings you here?") → small action (click, choice) → public/written commitment (goal) → reinforce ("Based on what you told us...").

**Ethical boundary:** Don't lock users into commitments they didn't freely make — allow easy reversibility.

See: [references/commitment-consistency.md](references/commitment-consistency.md) for commitment tactics and flows.

### 3. Social Proof

**Core concept:** People determine what's correct by finding out what others think is correct.

**Why it works:** When uncertain, we use others' behavior as a guide — "if everyone's doing it, it must be right."

**Key insights:**
- Most powerful when observers are uncertain; similar others = stronger proof
- Negative social proof backfires ("9 out of 10 don't...")
- Specific numbers beat vague claims ("2,347 users" > "thousands")

**Types of social proof:**

| Type | Definition | Example |
|------|------------|---------|
| **Wisdom of crowds** | Many people use/buy | "Join 50,000+ marketers" |
| **Wisdom of friends** | People you know use it | "3 of your friends use Notion" |
| **Expert** | Authorities endorse | "Recommended by Y Combinator" |
| **Celebrity** | Famous people use it | "Used by Elon Musk" |
| **Certification** | Third-party validation | "SOC 2 compliant", "App of the Year" |
| **User** | Similar people succeeded | "Startups like yours grew 10x" |

**Product applications:**

| Context | Social Proof Implementation | Example |
|---------|----------------------------|---------|
| **Landing pages** | User count, reviews, logos | "Trusted by 10,000+ companies" |
| **Signup flow** | Live signups, popular plans | "23 people signed up in the last hour" |
| **Feature adoption** | Show usage by others | "85% of teams use this feature" |

**Copy patterns:**
- "[X number] of [similar people] are already..."
- "[Name/Company] increased [metric] by [%]"
- "Don't take our word for it. Here's what [users] say..."

**Ethical boundary:** Never fabricate social proof — real numbers, real testimonials, and disclose when proof is curated.

See: [references/social-proof.md](references/social-proof.md) for social proof types and implementation patterns.

### 4. Authority

**Core concept:** People follow the lead of credible, knowledgeable experts.

**Why it works:** Obedience to authority is deeply ingrained — following experts is an efficient shortcut when we lack expertise ourselves.

**Key insights:**
- Titles, credentials, even symbols (lab coats, official-looking design) trigger automatic compliance
- Admitting a weakness paradoxically increases authority (trustworthiness) — lead with it before strengths
- Expertise doesn't transfer across domains, but people assume i
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.