hooked-ux skill

by wondelai·wondelai/skills·2.3k stars·MIT

Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building streaks or progress systems, or analyzing why users stop after signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.

A100/100content scan

Is the hooked-ux skill safe?

Clean: nothing in its files matched our rules. We read 8 files in the folder on 2026-09-28.

No findings.

Install the hooked-ux skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/wondelai/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/plugins/ux-design/skills/hooked-ux ~/.claude/skills/hooked-ux

available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Hook Model Framework

Framework for building habit-forming products. Habits are not created — they are built through successive cycles through the Hook.

Core Principle

The Hook Model = a four-phase loop that connects the user's problem to your solution frequently enough to form a habit, moving usage from deliberate to automatic.

Trigger → Action → Variable Reward → Investment
    ↑                                      │
    └──────────────────────────────────────┘

Scoring

Goal: 10/10. When reviewing or creating product engagement mechanics, score the loop by the four Quick Diagnostic rows (internal trigger, dead-simple action, variable reward, investment loads next trigger): each row earns 2 (fully satisfied), 1 (partial), or 0 (absent), then score = round(total / 8 × 10). Then apply the ethics gate: if the Manipulation Matrix places the product as Dealer (or it hits any "When NOT to Use" condition), cap the score at 3 regardless of mechanics. Bands: 9-10 = complete loop, internal trigger identified, ethics clear; 5-6 = loop runs but leans on external triggers or predictable rewards; <=3 = broken loop or extractive design. Always state the current score and the specific diagnostic rows blocking 10/10.

The Four Phases

1. Trigger

Core concept: The actuator of behavior. Triggers are external (environment-driven: notifications, emails, ads) or internal (emotion-driven) — and the goal is to migrate users from external to internal triggers.

Why it works: Every habit starts with a cue. External triggers get users started, but internal triggers — boredom, loneliness, uncertainty, FOMO — drive unprompted usage because the emotion itself fires before any reminder can.

Key insights:

Map your product to the specific negative emotion it resolves (boredom, loneliness, confusion, FOMO)
Effective external triggers are well-timed, actionable, and lead to the simplest possible next action
If users still need external prompts after ~30 days, no internal trigger has formed

Product applications:

Copy patterns:

"Don't miss what happened while you were away" (FOMO trigger)
"Your friend just..." (social trigger bridging to internal)
"Pick up where you left off" (routine trigger)

Ethical boundary: Don't build triggers that fire on vulnerable emotional states (depression, addiction, grief) — those users can't exercise the autonomy the loop assumes.

See references/triggers.md when mapping triggers — the emotion-to-product mapping exercise and the external-to-internal transition plan.

2. Action

Core concept: The simplest behavior done in anticipation of a reward, guided by the Fogg Behavior Model: Behavior = Motivation + Ability + Trigger, all converging at the same moment.

Why it works: Increasing motivation is hard and unreliable; reducing friction (increasing ability) is easier and more effective. Every extra step, field, or decision is a drop-off point.

Key insights:

Six elements of simplicity: time, money, physical effort, brain cycles, social deviance, non-routine
The action is the simplest behavior in anticipation of reward — not the full task
Hick's Law: more choices = slower decisions; reduce options to increase action rate

Product applications:

Copy patterns:

"Just one tap to..." (emphasizes simplicity)
"No credit card required" (money/risk simplicity)
Buttons should be verbs: "Post", "Save", "Share" — not "Submit" or "Continue"

Ethical boundary: When you simplify an action, don't strip the cost or consequence with it — a one-tap purchase must still surface the price and the commitment.

See references/product-applications.md when adapting the loop to your context — action and investment patterns for B2B SaaS, e-commerce, health, and productivity tools.

3. Variable Reward

Core concept: The phase that keeps users coming back. Anticipation of reward — not the reward itself — creates dopamine, and rewards must be variable (unpredictable) to sustain engagement.

Why it works: The brain's dopamine system responds most strongly to anticipation of uncertain rewards — the slot machine effect. Three reward types — tribe (social), hunt (resources), self (mastery) — tap fundamental human drives.

Key insights:

Tribe = social validation; Hunt = search for resources/information; Self = personal mastery
Predictable rewards lose power; finite variability eventually becomes predictable — aim for infinite variability
Autonomy is critical: users must feel in control; forced engagement backfires

Product applications:

Copy patterns:

"See what's new" (implies variability)
"3 people responded to your post" (tribe reward, variable quantity)
"You've unlocked a new achievement!" (self reward, unexpected)

Ethical boundary: If users consistently feel worse after engaging (regret, time loss, anxiety), the reward system is extractive — avoid infinite scroll without natural stopping points.

See references/rewards.md when designing a reward — tribe/hunt/self patterns, the four reinforcement schedules, and reward timing. For the dopamine/anticipation mechanism behind variable rewards, see references/neuroscience-foundations.md.

4. Investment

Core concept: Users invest something — time, data, effort, social capital, money — that improves the product for next use, raises switching costs, and loads the next trigger.

Why it works: People value what they put effort into (the IKEA effect). Investment is not about immediate reward — it improves the next cycle, creating a self-reinforcing loop.

Key insights:

Investment should come after reward, not before — users invest when they feel good
Each investment should load the next trigger (posting content triggers reply notifications)
Small investments compound: preferences → better recommendations → more usage; stored value grows over time

Product applications:

Copy patterns:

"Complete your profile to get better matches" (investment → future value)
"The more you use it, the smarter it gets" (compound investment)
"Invite your team to collaborate" (social investment)

Ethical boundary: Investment should genuinely improve the experience — never trap users with artificial switching costs or impossible data export; make staying the better choice through real value.

The Habit Zone

Two axes determine if a product can become a habit:

Ask: how often do users need to engage, what's the perceived value of each engagement, and is frequency high enough to form automatic behavior?

Habit Testing

The 5% rule: a habit has formed when at least 5% of users show unprompted, habitual usage.

Three questions:

Who are the habitual users? Which users engage most frequently, and what do they share?
What are they doing? Identify the "Habit Path" — the action sequence that separates power users from casual users.
Why are they doing it? What internal trigger and emotion precede usage?

See references/habit-testing.md when running the test — cohort analysis, finding the Habit Path, and confirming the 5% threshold. For worked teardowns of these loops in real products (Instagram, Slack, Duolingo, Pinterest, and failures), see references/case-studies.md.

The Manipulation Matrix

Framework for evaluating the ethics of habit-forming products:

Ask: would I use this myself? Does it genuinely help users achieve their goals? Am I exploiting vulnerabilities or serving needs?

When NOT to Use the Hook Model

Your product doesn't genuinely improve lives
You're targeting vulnerable populations (children, addiction-prone users)
The business model depends on user regret
Engagement conflicts with user wellbeing

More skills from wondelai/skills

A37signals-wayBuild 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", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
A37signals-wayBuild 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", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
A37signals-wayBuild 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", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
Aarchitecture-optimizationGuided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to make an app faster, untangle drifted boundaries, fix slow endpoints and queries, or says ''it works but it is slow and getting worse''. For an untested prototype, improve-code-quality; for an aged codebase you fear to touch, remove-technical-debt; for greenfield structure, design-code-architecture; for marketing-site page speed, improve-website. For one framework in isolation, invoke that skill directly.
Ablue-ocean-strategyCreate 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", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
Ablue-ocean-strategyCreate 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", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
Ablue-ocean-strategyCreate 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", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
Aclean-architectureStructure 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)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
Aclean-architectureStructure 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)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
Aclean-architectureStructure 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)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.

All agent skills → · MCP servers