ux-behavior-design
Skill37 starsChanged 9 months agoLicence not identifiedView on GitHub
Fogg Behavior Model B=MAP bottleneck diagnosis sub-skill for the /user-experience parent skill. Diagnoses why users fail to take desired actions by analyzing the three B=MAP factors (Motivation, Ability, Prompt) and identifying which factor falls below the action threshold. Produces bottleneck diagnoses, factor-level assessments, and intervention recommendations with synthesis confidence gates. Invoke when teams need to understand why users are not completing a specific action, diagnose behavioral bottlenecks, design behavior change interventions, or analyze post-launch user inaction patterns. Invoked by ux-orchestrator during Wave 4 lifecycle-stage routing or when user intent is \"Users not completing action\" during the \"After launch\" stage. Triggers: behavior design, B=MAP, Fogg model, behavior bottleneck, motivation analysis, ability analysis, prompt design, why users don't, user inaction, behavior diagnosis, tiny habits, action threshold.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversarySkill
- architectureSkill
- astSkill
- bootstrapSkill
- contract-designSkill
- diataxisSkill
- eng-teamSkill
- worktracker-decompositionSkill
- worktrackerSkill
- nasa-seSkill
- orchestrationSkill
- pm-pmmSkill
- problem-solvingSkill
- prompt-engineeringSkill
- red-teamSkill
- saucer-boy-framework-voiceSkill
- saucer-boySkill
- test-specSkill
- transcriptSkill
- use-caseSkill
- user-experienceSkill
- ux-ai-first-designSkill
- ux-atomic-designSkill
- ux-design-sprintSkill
- ux-heart-metricsSkill
- ux-heuristic-evalSkill
- ux-inclusive-designSkill
- ux-jtbdSkill
- ux-kano-modelSkill
- ux-lean-uxSkill
- worktrackerSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.