ux-behaviour-audit
Skill1 starsChanged 8 days agoNo licenceView on GitHub
Audit a UI by how users behave on it. Walk one task as the user, or every edge case of one behaviour bug, check each screen through six behaviour lenses (decide, scan, act, trust, commit, orient), weigh each fix against the product's own philosophy, place every screen on a junior-to-staff ladder, flag persuasion that crosses into a dark pattern, and render the report in chat. Use when asked for a UX audit, a usability review of a flow, the edge cases of a behaviour, or why users hesitate or drop off, from screenshots, a live URL, frontend code or a native app. Visual polish is the impeccable skill; brand and token drift across screens is the design-direction skill; a report file to keep is the report-web skill.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- art-critiqueSkill
- brand-artSkill
- design-directionSkill
- learnSkill
- moodboardSkill
- motion-directionSkill
- report-changelogSkill
- report-deckSkill
- report-webSkill
- video-contextSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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.