drive-motivation
Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "team incentives", "autonomy", "mastery", "purpose-driven", "employee engagement", or "reward systems". Also trigger when designing onboarding progression systems, fixing broken gamification, or building team structures that sustain high performance. Covers why carrot-and-stick fails and how to build progress systems. For habit-forming product loops, see hooked-ux. For retention behavior design, see improve-retention.
What this skill does
# Drive Motivation Framework
Framework for designing motivation systems in products, teams, and organizations based on the science of what actually motivates humans. Replaces outdated carrot-and-stick thinking with intrinsic motivation.
## Core Principle
**The secret to high performance isn't rewards and punishment — it's the deeply human need to direct our own lives, learn and create new things, and do better for ourselves and our world.**
**The foundation:** For any task requiring even rudimentary cognitive effort, external rewards (bonuses, prizes, punishments) either don't work or actively make performance worse. Intrinsic motivation — Autonomy, Mastery, Purpose — drives lasting engagement.
## Scoring
**Goal: 10/10.** When evaluating motivation systems (product features, team incentives, gamification, engagement loops), rate 0-10 based on AMP principles. A 10/10 means the system supports autonomy, enables mastery, and connects to purpose; lower scores indicate reliance on extrinsic rewards or controlling behaviors. Always provide current score and improvements to reach 10/10.
## Motivation 1.0, 2.0, and 3.0
| Version | Core Assumption | Approach | Era |
|---------|----------------|----------|-----|
| **1.0** | Humans are biological beings | Survival drives (food, shelter, safety) | Pre-industrial |
| **2.0** | Humans respond to rewards/punishments | Carrot and stick (bonuses, penalties) | Industrial age |
| **3.0** | Humans seek autonomy, mastery, purpose | Intrinsic motivation | Knowledge economy |
**The problem with Motivation 2.0 (carrot and stick):**
Most organizations still run on Motivation 2.0, but it's fundamentally broken for modern work.
### The Seven Deadly Flaws of Extrinsic Rewards
External rewards ("if-then" rewards: "If you do X, then you get Y"):
| Flaw | Mechanism | Example |
|------|-----------|---------|
| **1. Extinguish intrinsic motivation** | Turns play into work | Kids who were paid to draw stopped drawing when payments stopped |
| **2. Diminish performance** | Narrow focus, reduce creativity | Candle problem: reward group performed worse |
| **3. Crush creativity** | Focus on reward, not exploration | Artists creating commissioned work are less creative |
| **4. Crowd out good behavior** | Financial framing replaces moral framing | Day care late-pickup fee: lateness increased (became a "service") |
| **5. Encourage cheating** | Goal fixation leads to shortcuts | Wells Fargo fake accounts scandal |
| **6. Become addictive** | Need bigger rewards over time | Bonus escalation: last year's bonus = this year's expectation |
| **7. Foster short-term thinking** | Optimize for reward period | Quarterly bonuses → quarterly thinking |
**When extrinsic rewards DO work:**
- Routine, algorithmic tasks (assembly line, data entry)
- Tasks requiring no creativity or judgment
- When the task is genuinely boring and no intrinsic motivation exists
**When extrinsic rewards DON'T work (and hurt):**
- Creative work
- Complex problem-solving
- Any task requiring cognitive effort
- Long-term engagement
See: [references/extrinsic-rewards.md](references/extrinsic-rewards.md) for the science behind reward failures.
## The Three Pillars: Autonomy, Mastery, Purpose
### 1. Autonomy
**Definition:** The desire to direct our own lives — to have choice over what we do, when we do it, how we do it, and who we do it with.
**Autonomy ≠ independence.** Autonomy means acting with choice. You can be autonomous while being interdependent with a team.
**The Four T's of Autonomy:**
| Dimension | Question | Example |
|-----------|----------|---------|
| **Task** | What do I work on? | Google's 20% time, Atlassian ShipIt days |
| **Time** | When do I work? | Flexible hours, no mandatory meetings |
| **Technique** | How do I do it? | Choose your own tools, methods, approach |
| **Team** | Who do I work with? | Self-forming teams, choose collaborators |
**Product applications:**
| Context | Autonomy Killer | Autonomy Enabler |
|---------|----------------|-------------------|
| **Onboarding** | Forced linear tutorial | Choose your own path, skip steps |
| **Customization** | One-size-fits-all | Themes, layouts, preferences |
| **Content** | Algorithm-only feed | User-controlled feeds, filters |
| **Communication** | Forced notifications | Notification preferences, DND |
| **Workflow** | Rigid process | Flexible workflow, custom automations |
| **Features** | Feature bloat (all visible) | Show/hide features, progressive disclosure |
**Autonomy audit questions:**
- Can users choose WHAT to do in the product?
- Can users choose WHEN to engage?
- Can users choose HOW to complete tasks?
- Can users choose their own path through the experience?
**Warning signs of autonomy violation:**
- "You must complete X before Y"
- Forced tutorials with no skip option
- Mandatory notifications
- No customization options
- Rigid workflows with no flexibility
See: [references/autonomy.md](references/autonomy.md) for autonomy design patterns.
### 2. Mastery
**Definition:** The desire to get better at something that matters — to continually improve and grow.
**Mastery is a mindset, not a destination.** It's asymptotic — you can approach it but never fully reach it. The joy is in the pursuit.
**Three laws of mastery:**
**Law 1: Mastery is a Mindset**
- Growth mindset (Carol Dweck): Ability is developed, not fixed
- People with growth mindset seek challenges and learn from failure
- Fixed mindset people avoid challenges (might reveal inadequacy)
- **Design implication:** Frame failures as learning, not judgment
**Law 2: Mastery is a Pain**
- Requires effort, deliberate practice, and grit
- Flow (Csikszentmihalyi): Optimal state between boredom and anxiety
- Challenge must match skill level — too easy = boring, too hard = anxious
- **Design implication:** Calibrate difficulty to user's level
**Law 3: Mastery is Asymptotic**
- You can approach mastery but never fully arrive
- The pursuit itself is the reward
- **Design implication:** Always have next level, next challenge
**The Flow Channel:**
```
ANXIETY
/
/
FLOW ←──────────── Optimal challenge zone
\
\
BOREDOM
Low Skill ──────────────── High Skill
```
**Flow conditions:**
- Clear goals
- Immediate feedback
- Challenge/skill balance
- Sense of control
- Deep concentration
**Product applications:**
| Context | Mastery Design | Example |
|---------|---------------|---------|
| **Progress** | Visible skill development | GitHub contribution graph, Duolingo levels |
| **Difficulty** | Adaptive challenge | Games that adjust to player skill |
| **Feedback** | Immediate, clear signals | Real-time writing analysis (Grammarly) |
| **Goals** | Clear, achievable milestones | LinkedIn profile strength meter |
| **Learning** | Skill trees, structured paths | Codecademy learning paths |
| **Streaks** | Consistency tracking | Duolingo streaks (careful: can become extrinsic) |
**Mastery audit questions:**
- Can users see their progress over time?
- Does the product adapt to skill level?
- Is there immediate, meaningful feedback?
- Are there clear next steps for improvement?
- Does the challenge increase as skill increases?
**Warning signs of mastery violation:**
- No way to see improvement
- Same difficulty regardless of skill
- Delayed or absent feedback
- No clear path forward
- Punishing failures instead of teaching
See: [references/mastery.md](references/mastery.md) for mastery design patterns and flow state principles.
### 3. Purpose
**Definition:** The yearning to do what we do in the service of something larger than ourselves.
**Purpose is the context for autonomy and mastery.** Without purpose, autonomy is directionless and mastery is hollow.
**Three expressions of purpose:**
| Expression | How It Manifests | Example |
|-----------|-----------------|---------|
| **Goals** | Purpose-driven objectivRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.