loss-aversion-psychology

Leverage loss aversion in product design and messaging. Use when designing retention features, pricing strategies, onboarding flows, or any experience where framing around potential loss can drive behavior.

210 stars

Best use case

loss-aversion-psychology is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Leverage loss aversion in product design and messaging. Use when designing retention features, pricing strategies, onboarding flows, or any experience where framing around potential loss can drive behavior.

Teams using loss-aversion-psychology should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/loss-aversion-psychology/SKILL.md --create-dirs "https://raw.githubusercontent.com/flpbalada/my-opencode-config/main/skills/loss-aversion-psychology/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/loss-aversion-psychology/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How loss-aversion-psychology Compares

Feature / Agentloss-aversion-psychologyStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Leverage loss aversion in product design and messaging. Use when designing retention features, pricing strategies, onboarding flows, or any experience where framing around potential loss can drive behavior.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Loss Aversion Psychology - Losses Loom Larger Than Gains

Loss Aversion is a cognitive bias discovered by Daniel Kahneman and Amos Tversky
showing that people feel losses approximately twice as strongly as equivalent
gains. This asymmetry profoundly influences decision-making and behavior.

## When to Use This Skill

- Designing retention and anti-churn features
- Crafting pricing and upgrade messaging
- Creating urgency in conversion funnels
- Building streak and progress features
- Writing copy for landing pages
- Framing feature benefits

## Core Concepts

### The 2:1 Ratio

```
        Psychological Impact
              ^
              |         Gains
              |        /
              |      /
     +--------|----/---------> Value
              |  /
           Loss|/
              |
              |  The loss curve is ~2x steeper
              v
```

A $100 loss feels as bad as a $200 gain feels good.

### Prospect Theory Framework

| Concept              | Description                      | Example                      |
| -------------------- | -------------------------------- | ---------------------------- |
| **Reference Point**  | Current state as baseline        | "You currently have X"       |
| **Loss Frame**       | Emphasis on what could be lost   | "Don't lose your progress"   |
| **Gain Frame**       | Emphasis on what could be gained | "Get 50% more"               |
| **Endowment Effect** | Valuing owned things higher      | Free trial creates ownership |

### When Loss Framing Works Best

| Situation                 | Loss Frame Effective? |
| ------------------------- | --------------------- |
| High stakes decisions     | Yes                   |
| Preventing bad outcomes   | Yes                   |
| Risk-averse audiences     | Yes                   |
| Building habits           | Yes                   |
| Low-involvement decisions | Less effective        |
| Exploratory behavior      | Less effective        |

## Analysis Framework

### Step 1: Identify Loss Opportunities

Map user journey for potential loss frames:

| Stage   | What User Has      | Potential Loss  |
| ------- | ------------------ | --------------- |
| Trial   | Access to features | Losing access   |
| Active  | Progress/data      | Losing progress |
| At-risk | Streak/status      | Breaking streak |
| Churned | History/investment | Losing history  |

### Step 2: Choose Frame Appropriately

```
Decision: Frame as loss or gain?

Consider:
├── User relationship stage
│   └── New users: Gains more welcoming
│   └── Existing users: Losses more motivating
├── Action reversibility
│   └── Reversible: Lighter touch OK
│   └── Irreversible: Loss frame powerful
└── Ethical considerations
    └── Does this genuinely help the user?
```

### Step 3: Implement Ethically

| Approach                 | Ethical          | Manipulative       |
| ------------------------ | ---------------- | ------------------ |
| "Your streak will reset" | Honest reminder  | Manufactured guilt |
| "Unused credits expire"  | Clear policy     | Hidden deadline    |
| "Limited time offer"     | Genuine scarcity | Fake urgency       |

## Output Template

```markdown
## Loss Aversion Analysis

**Feature/Message:** [Name] **Date:** [Date]

### Current Framing

**As gain:** [Current copy/design] **User response:** [Current metrics]

### Loss Frame Opportunity

**What user has:** [Established value] **Potential loss:** [What could be lost]
**Loss frame version:** [Proposed copy/design]

### Ethical Check

- [ ] User genuinely benefits from taking action
- [ ] Loss is real, not manufactured
- [ ] Messaging is honest and transparent
- [ ] Would we be comfortable if users knew the psychology?

### Implementation Plan

| Element  | Current   | Proposed | Expected Impact |
| -------- | --------- | -------- | --------------- |
| [Copy 1] | [Text]    | [Text]   | [Estimate]      |
| [Design] | [Current] | [Change] | [Estimate]      |
```

## Real-World Examples

### Example 1: Duolingo Streaks

**Mechanism**: Users build daily learning streaks **Loss frame**: "Don't lose
your 47-day streak!" **Psychology**:

- Streak = accumulated investment (endowment)
- Breaking it = losing days of effort
- Effect: 2x stronger than "Build a 48-day streak!"

### Example 2: LinkedIn Profile Completion

**Gain frame**: "Complete your profile to get more views" **Loss frame**:
"You're missing out on 40% more profile views"

The loss frame outperforms because it highlights what you're currently losing.

### Example 3: Trial Expiration

**Weak**: "Your trial ends tomorrow" **Strong**: "Tomorrow you'll lose access
to:

- 47 saved projects
- 12 team members
- All your custom settings"

Making the loss concrete and specific amplifies the effect.

## Ethical Guidelines

### Do

- Use loss framing for genuinely beneficial actions
- Be honest about what's at stake
- Give users real control and options
- Balance loss frames with positive experiences
- Test that users feel good after taking action

### Avoid

- Manufacturing fake urgency or scarcity
- Guilt-tripping for engagement metrics
- Hiding information to create loss anxiety
- Using loss aversion on vulnerable users
- Dark patterns that exploit psychology

### The Ethics Test

Ask: "If users knew exactly how this works psychologically, would they:

1. Thank us for the helpful reminder?
2. Feel manipulated and resentful?"

If (2), reconsider the approach.

## Best Practices

### Effective Loss Messaging

| Element         | Example                                         |
| --------------- | ----------------------------------------------- |
| **Specific**    | "Lose your 23 saved items" not "Lose your data" |
| **Immediate**   | "Expires tonight" not "Expires soon"            |
| **Personal**    | "Your progress" not "Progress"                  |
| **Recoverable** | Show how to prevent the loss                    |

### Timing Matters

| Timing     | Effectiveness             |
| ---------- | ------------------------- |
| Too early  | Feels irrelevant, ignored |
| Just right | Motivates action          |
| Too late   | Creates resentment        |
| After loss | Recovery opportunity      |

## Integration with Other Methods

| Method                     | Combined Use                            |
| -------------------------- | --------------------------------------- |
| **Hooked Model**           | Investment phase creates loss potential |
| **Fogg Behavior Model**    | Loss increases motivation               |
| **Cognitive Biases**       | Combine with other biases carefully     |
| **Progressive Disclosure** | Reveal loss implications gradually      |

## Resources

- [Thinking, Fast and Slow - Daniel Kahneman](https://www.amazon.com/Thinking-Fast-Slow-Daniel-Kahneman/dp/0374533555)
- [Predictably Irrational - Dan Ariely](https://www.amazon.com/Predictably-Irrational-Hidden-Forces-Decisions/dp/0061353248)
- [Prospect Theory Original Paper - Kahneman & Tversky](https://www.jstor.org/stable/1914185)

Related Skills

visual-cues-cta-psychology

210
from flpbalada/my-opencode-config

Design effective CTAs using visual attention and gaze psychology principles. Use when designing landing pages, button hierarchies, conversion elements, or optimizing user attention flow through interfaces.

trust-psychology

210
from flpbalada/my-opencode-config

Build trust signals that reduce perceived risk and enable user action. Use when designing landing pages, checkout flows, onboarding experiences, or any conversion point where user hesitation is a barrier.

social-proof-psychology

210
from flpbalada/my-opencode-config

Leverage social proof principles to build trust and influence user behavior. Use when designing landing pages, adding testimonials, displaying user stats, or optimizing conversion elements with social validation.

halo-effect-psychology

210
from flpbalada/my-opencode-config

Apply the halo effect in product design and UX. Use when designing first impressions, brand perception, feature presentation, or understanding how one positive attribute influences perception of others.

cognitive-fluency-psychology

210
from flpbalada/my-opencode-config

Apply cognitive fluency principles to improve clarity, trust, and conversion. Use when designing landing pages, writing copy, creating interfaces, or optimizing any content for better user comprehension and engagement.

what-not-to-do-as-product-manager

210
from flpbalada/my-opencode-config

Anti-patterns and mistakes to avoid as a product manager. Use when evaluating leadership behaviors, improving team dynamics, reflecting on management practices, or onboarding new product managers.

vercel-sandbox

210
from flpbalada/my-opencode-config

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

value-realization

210
from flpbalada/my-opencode-config

Analyze if end users discover clear value. Use when evaluating product concepts, analyzing adoption, or uncertain about direction.

user-story-fundamentals

210
from flpbalada/my-opencode-config

Capture requirements from user perspective with structured user stories. Use when writing backlog items, defining acceptance criteria, prioritizing features, or communicating requirements between product and development.

typescript-satisfies-operator

210
from flpbalada/my-opencode-config

Guides proper usage of TypeScript's satisfies operator vs type annotations. Use this skill when deciding between type annotations (colon) and satisfies, validating object shapes while preserving literal types, or troubleshooting type inference issues.

typescript-interface-vs-type

210
from flpbalada/my-opencode-config

Guides when to use interface vs type in TypeScript. Use this skill when defining object types, extending types, or choosing between interface and type aliases.

typescript-best-practices

210
from flpbalada/my-opencode-config

Guides TypeScript best practices for type safety, code organization, and maintainability. Use this skill when configuring TypeScript projects, deciding on typing strategies, writing async code, or reviewing TypeScript code quality.