hooked-ux
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.
- License 许可
- MIT
- 最近更新
- 2026-09-07
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- hooked-ux
- license
- MIT
- metadata
- { "author": "wondelai", "version": "1.5.1" }
- description
- 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.
02 资源文件 7
- 参考文档references/case-studies.md10.8 KB
- 参考文档references/ethical-boundaries.md9.4 KB
- 参考文档references/habit-testing.md6.8 KB
- 参考文档references/neuroscience-foundations.md7.7 KB
- 参考文档references/product-applications.md9.9 KB
- 参考文档references/rewards.md7.6 KB
- 参考文档references/triggers.md5.9 KB
03 SKILL.md 正文
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:
| Context | Application | Example |
|---|---|---|
| Onboarding | External triggers establish the first loop | Welcome email with one clear action |
| Retention | Map product to internal emotional trigger | Instagram resolves boredom; Google resolves confusion |
| Re-engagement | External triggers bridge gaps until habit forms | Push: "Your friend just posted a photo" |
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:
| Context | Application | Example |
|---|---|---|
| Signup flow | Minimize fields and steps | One-click Google/Apple sign-in |
| Core action | Completable in seconds | Twitter: type 280 characters and post |
| Progressive disclosure | Ask for more only after initial reward | Duolingo: play first, create account later |
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:
| Context | Application | Example |
|---|---|---|
| Social features (Tribe) | Variable social validation | Instagram likes — you never know how many |
| Content feeds (Hunt) | Unpredictable resource stream | Infinite scroll with algorithmically varied content |
| Gamification (Self) | Accomplishment with variable difficulty | Duolingo streaks + surprise bonus challenges |
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:
| Context | Application | Example |
|---|---|---|
| Data investment | History improves personalization | Spotify: more listening = better recommendations |
| Content investment | User-created content they won't abandon | Instagram posts, Notion documents |
| Reputation/social investment | Social capital that exists only on-platform | Airbnb host ratings, LinkedIn network |
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:
| Low Frequency | High Frequency | |
|---|---|---|
| High Perceived Value | Viable product (needs ads/marketing) | HABIT ZONE |
| Low Perceived Value | Failure | Failure |
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:
| Maker Uses Product | Maker Doesn't Use | |
|---|---|---|
| Materially Improves User's Life | Facilitator | Peddler |
| Doesn't Improve Life | Entertainer | Dealer |
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
See references/ethical-boundaries.md when the Manipulation Matrix flags a concern — dark-pattern catalog and how to protect vulnerable users.
Regulatory Context
Watch emerging regulation: children's apps (COPPA, GDPR-K), dark patterns (rising FTC enforcement), "addictive" notification practices, and loot boxes (expanding gaming rules).
Onboarding Audit Checklist
Optimizing onboarding for habit formation:
First Trigger
- [ ] First action obvious and easy; right external trigger for this user
- [ ] Value proposition clear before asking for investment
First Action
- [ ] Core action completable in under 60 seconds, friction removed
- [ ] UI familiar (no new learning required)
First Reward
- [ ] Immediate feedback with a variable element (surprise, delight)
- [ ] Reward connects to an internal trigger
First Investment
- [ ] Investment asked after reward (not before), small but meaningful
- [ ] Investment loads the next trigger
Loop Completion
- [ ] Clear path back to the trigger; external triggers sent at appropriate times
- [ ] Progression through the Hook is measured
Common Mistakes
| Mistake | Why It Fails | Fix |
|---|---|---|
| Relying on external triggers indefinitely | You're renting attention, not building habits | Map product to an emotion; transition to internal triggers within 30 days |
| Making the core action too complex | Users drop off before the reward | Simplify to minimum viable action; apply the six ability factors |
| Using predictable rewards | Dopamine response fades with novelty | Add variability across tribe, hunt, and self rewards |
| Asking for investment before reward | Users haven't received value yet | Sequence: trigger, action, reward, THEN investment |
| Ignoring the ethics of your hook | User regret, backlash, regulatory risk | Use the Manipulation Matrix; be a Facilitator, not a Dealer |
Quick Diagnostic
Audit any product feature:
| Question | If No | Action |
|---|---|---|
| What's the internal trigger? | Users need reminders to use it | Research user emotions |
| Is the action dead simple? | Users start but don't complete | Remove friction |
| Is the reward variable? | Users get bored | Add unpredictability |
| Does investment load next trigger? | Users don't return | Connect investment to triggers |
Further Reading
Based on the Hook Model developed by Nir Eyal:
- "Hooked: How to Build Habit-Forming Products" by Nir Eyal
- "Indistractable: How to Control Your Attention and Choose Your Life" by Nir Eyal (companion: resisting unwanted habits and building focus)
About the Author
Nir Eyal taught at Stanford Graduate School of Business and the Hasso Plattner Institute of Design, after working in the gaming and advertising industries where he saw habit psychology firsthand. Hooked distills that research into a framework used by product teams from startups to Fortune 500s; his follow-up Indistractable addresses resisting the same triggers.
04 同仓库更多 Skills
scrapling-official
Scrape web pages using Scrapling with anti-bot bypass (like Cloudflare Turnstile), stealth headless browsing, spiders framework, adaptive scraping, and JavaScript rendering. Use when asked to scrape, crawl, or extract data from websites; web_fetch fails; the site has anti-bot protections; write Python code to scrape/crawl; or write spiders.
working-with-legacy-code
Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.
ux-heuristics
Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "users are confused", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "is this easy to use". Also trigger when reviewing a design for usability issues, improving form-completion rates, or evaluating information architecture and navigation. Covers Krug's laws, Nielsen's 10 heuristics, severity ratings, dark-pattern recognition, and accessibility. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same problems", or "get the whole team aligned". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic way to solve recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard landing page into a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.