Framework for building habit-forming products. Based on a fundamental truth: habits are not created—they are built through successive cycles through the Hook.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionhooked-uxExecute the skills CLI command in your project's root directory to begin installation:
Fetches hooked-ux from wondelai/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate hooked-ux. Access via /hooked-ux in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
431
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
431
stars
Framework for building habit-forming products. Based on a fundamental truth: habits are not created—they are built through successive cycles through the Hook.
The Hook Model = a four-phase process that connects the user's problem to your solution frequently enough to form a habit.
Trigger → Action → Variable Reward → Investment
↑ │
└──────────────────────────────────────┘
Habit Zone: Products enter the "habit zone" when used frequently enough and with enough perceived value. The goal is to move users from deliberate usage to automatic, habitual behavior.
Goal: 10/10. When reviewing or creating product engagement mechanics, rate them 0-10 based on adherence to the principles below. A 10/10 means full alignment with all guidelines; lower scores indicate gaps to address. Always provide the current score and specific improvements needed to reach 10/10.
Core concept: The actuator of behavior. What prompts the user to take action? Triggers come in two forms: external (environment-driven) and internal (emotion-driven). The ultimate goal is to move users from external triggers to internal triggers.
Why it works: Every habit starts with a cue. Without a trigger, there is no behavior. External triggers get users started, but internal triggers — emotions like boredom, loneliness, uncertainty, or fear of missing out — are what drive unprompted, habitual usage. When your product becomes the automatic response to an internal trigger, you have a habit.
Key insights:
Product applications:
| Context | Application | Example |
|---|---|---|
| Onboarding | Use external triggers to establish first loop | Welcome email with one clear action to take |
| Retention | Map product to internal emotional trigger | Instagram resolves boredom; Google resolves confusion |
| Re-engagement | External triggers bridge gaps until habit forms | Push notification: "Your friend just posted a photo" |
| Emotion mapping | Identify which negative emotion your product addresses | Loneliness → Facebook; Uncertainty → Twitter/News apps |
| Trigger audit | Evaluate if users still need external prompts | If yes after 30 days, internal trigger hasn't formed |
Copy patterns:
Ethical boundary: Never exploit vulnerable emotional states (depression, addiction, grief) as triggers. Triggers should connect users to genuine value, not manufacture anxiety to drive opens.
See: references/triggers.md for detailed trigger design, emotion mapping, and external-to-internal transition strategies.
Core concept: The simplest behavior done in anticipation of a reward. Guided by the Fogg Behavior Model: B = MAT (Behavior = Motivation + Ability + Trigger). All three must converge at the same moment for action to occur.
Why it works: Increasing motivation is hard and unreliable. Reducing friction (increasing ability) is easier and often more effective. The key insight is that making the action simpler is almost always a better strategy than trying to increase motivation. Every extra step, field, or decision is a point where users drop off.
Key insights:
Product applications:
| Context | Application | Example |
|---|---|---|
| Signup flow | Minimize fields and steps to reduce friction | One-click Google/Apple sign-in instead of form |
| Core action | Make the key behavior completable in seconds | Twitter: type 280 characters and post (vs. write a blog) |
| Simplicity audit | Evaluate each of the six ability factors | Can user complete core action in under 60 seconds? |
| Progressive disclosure | Ask for more only after initial reward | Duolingo: play first, create account later |
| Friction removal | Identify and eliminate unnecessary steps | Autocomplete, defaults, skip options, smart prefills |
Copy patterns:
Ethical boundary: Reducing friction should make genuinely valuable actions easier — not trick users into actions they'd regret. Dark patterns that hide costs or consequences behind simple actions are unethical.
See: references/triggers.md for how triggers connect to the action phase, and references/product-applications.md for action design across product types.
Core concept: The phase that keeps users coming back. The anticipation of reward — not the reward itself — creates dopamine. Critically, rewards must be variable (unpredictable) to maintain engagement. Predictable rewards lose their power over time.
Why it works: The brain's dopamine system responds most strongly to the anticipation of uncertain rewards, not to the rewards themselves. This is the slot machine effect: variable reinforcement schedules are far more engaging than fixed ones. Three types of variable rewards — tribe (social), hunt (resources), and self (mastery) — tap into fundamental human drives.
Key insights:
Product applications:
| Context | Application | Example |
|---|---|---|
| Social features (Tribe) | Variable social validation from others | Instagram likes, Reddit upvotes — you never know how many |
| Content feeds (Hunt) | Unpredictable stream of resources/information | Infinite scroll with algorithmically varied content |
| Gamification (Self) | Personal accomplishment with variable difficulty | Duolingo streaks + surprise bonus challenges |
| Notifications | Variable content in each notification | "3 people liked your post" vs. "Sarah commented something surprising" |
| Search/Discovery | The hunt for the next great find | Pinterest: scroll to find the perfect pin; eBay: hunt for deals |
Copy patterns:
Ethical boundary: Variable rewards should deliver genuine value, not exploit compulsive behavior. If users consistently feel worse after engaging (regret, time loss, anxiety), the reward system is extractive, not valuable. Avoid infinite scroll without natural stopping points for vulnerable users.
See: references/rewards.md for reward design patterns, reinforcement schedules, and reward timing.
Core concept: The phase that increases the likelihood of another pass through the Hook. Users invest something — time, data, effort, social capital, or money — that improves the product for next use and raises switching costs. Investment loads the next trigger.
Why it works: People value what they put effort into (the IKEA effect). Investment creates stored value that makes the product better with use and harder to leave. Critically, investment is not about immediate reward — it's about improving the next cycle. Each investment loads the next trigger, creating a self-reinforcing loop.
Key insights:
Product applications:
| Context | Application | Example |
|---|---|---|
| Data investment | Preferences, history, uploads improve personalization | Spotify: the more you listen, the better recommendations get |
| Content investment | User-created content they don't want to lose | Instagram posts, Notion documents, Slack message history |
| Reputation investment | Reviews, ratings, followers create social capital | Airbnb host ratings, Stack Overflow reputation points |
| Skill investment | Learning the interface creates switching cost | Photoshop expertise, Vim muscle memory |
| Social investment | Connections and groups that exist only on platform | LinkedIn network, Discord communities, Slack workspaces |
Copy patterns:
Ethical boundary: Investment should genuinely improve the user's experience. Don't make data export impossible or trap users with artificial switching costs. Ethical products let users leave with their data while making staying the better choice through real value.
See: references/product-applications.md for investment patterns across B2B SaaS, e-commerce, health apps, and productivity tools.
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 |
Questions:
The 5% rule: A product has formed a habit when at least 5% of users show unprompted, habitual usage.
Three questions for habit testing:
Who are the habitual users?
What are they doing?
Why are they doing it?
See: references/habit-testing.md for testing methodology.
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 |
Questions to ask:
The Hook Model is inappropriate when:
See: references/ethical-boundaries.md for comprehensive ethics guidance.
Be aware of emerging regulations around:
Optimizing onboarding for habit formation:
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 |
| Mistake | Why It Fails | Fix |
|---|---|---|
| Relying on external triggers indefinitely | Users never form internal triggers; you're renting attention, not building habits | Map product to a specific emotion; transition from external to internal triggers within 30 days |
| Making the core action too complex | Users drop off before reaching the reward phase | Simplify to the minimum viable action; apply Fogg's six ability factors |
| Using predictable rewards | Engagement drops after novelty wears off; dopamine response fades | Introduce variability across tribe, hunt, and self reward types |
| Asking for investment before reward | Users haven't received value yet and resist investing effort | Always sequence: trigger, action, reward, THEN investment |
| Ignoring the ethics of your hook | User regret, backlash, regulatory risk, brand damage | Use the Manipulation Matrix; aim to be a Facilitator, not a Dealer |
This skill is based on the Hook Model developed by Nir Eyal. For the complete methodology, research, and case studies:
Nir Eyal is an author, lecturer, and investor who has taught at Stanfo
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: hooked-ux is the kind of skill you can hand to a new teammate without a long onboarding doc.
hooked-ux has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for hooked-ux matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in hooked-ux — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
hooked-ux has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend hooked-ux for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
hooked-ux has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: hooked-ux is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend hooked-ux for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
hooked-ux reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 55