Ux
Agent skills for agentic coding tools. Extremely opinionated. Updated (almost) daily.
npx -y skills add JHostalek/dotclaude --skill uxAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when reviewing a user-facing page or flow for usability issues, confusion, friction, or missed UX principles.
SKILL.md
1.4 KB, as published. Nobody here has run it
page_path = $ARGUMENTS
page_path provided → focus on that page/component. Otherwise evaluate entire application UI.
Approach
Match evaluation depth to scope: single component → the 2-3 most relevant dimensions; full page → every applicable fundamental; entire app → 3 highest-traffic flows first (a whole-app sweep produces more findings than anyone acts on). Every applicable fundamental gets evaluated even when another lens overlaps it.
Gather context from at least one source, in order of preference: live browser navigation, screenshots, code review. Combine when available.
Apply the dimensions below.
!cat "${CLAUDE_SKILL_DIR}/ui-evaluation.md"
Output
Scores
Rate each evaluated dimension 1-5 (1=broken, 5=excellent). Compact table. Overall UX score = average.
Findings
Critical (blocks primary task): Issue → file:line → specific fix
High (major frustration): Issue → location → fix
What Works: Preserve these during fixes
Low (polish): Brief list
Validation
For each critical/high fix: what to test (user action) and what success looks like (behavior or outcome).
After presenting, offer to implement the top 3 critical/high fixes. Change nothing before the user accepts.