UX Heuristics
Usability evaluation and principles
Evaluate and improve usability using Nielsen's heuristics and Krug's "Don't Make Me Think" principles. This skill gives your AI agent a systematic framework for finding and fixing UX problems before users encounter them.
npx skills add wondelai/skills/ux-heuristics --global 
Don’t Make Me Think Steve Krug & Jakob Nielsen View on Amazon
02 What it is
What is the UX Heuristics skill?
UX Heuristics folds two usability traditions into one skill: Jakob Nielsen’s ten heuristics and Steve Krug’s Don’t Make Me Think. It has your agent walk an interface the way an evaluator does — naming each violation, rating its severity from 0 to 4, and proposing the specific fix — instead of offering a general opinion on whether a screen looks usable.
03 Key concepts
Five principles your agent applies.
Drawn from Don’t Make Me Think — not advice it repeats back to you, but decisions it makes while it works.
04 Fit
When to use it, and
when not to.
four symptoms it fixes, and four it doesn't.
Reach for it when
Support answers the same “where do I find…” question every week and you suspect the navigation.
Your signup form is abandoned halfway and you need to know which fields cause it.
A page looks beautiful and a first-time visitor can’t tell what the site is or where to go.
You need an audit that produces a ranked issue list, not a design opinion.
Reach for something else when
The interface is usable and simply looks unprofessional. Refactoring UI handles spacing, color, and hierarchy.
You want more signups from the same traffic. CRO Methodology tests for revenue, not comprehension.
You need real reasons from real users instead of an expert walkthrough. start with The Mom Test.
It is an iOS app and the issue is convention rather than clarity. iOS HIG Design knows what users expect.
05 Prompts
Say it like this.
Name the skill at the end of a prompt and the agent applies the framework rather than a vibe. Or say nothing — it loads on its own when a task matches.
Run a heuristic evaluation on my checkout flow using ux-heuristics skill
Identify usability issues on this dashboard page using ux-heuristics skill
Simplify this navigation so users don't have to think using ux-heuristics skill
Add better error prevention to my form validation using ux-heuristics skill
06 About the author
07 Same stack
The stack it sits in.
Nine Design & UX skills. Most people run two: this one, and whichever fits the next problem.
All Design & UX skills08 Questions
Before you install.
How do I install the UX Heuristics skill?
Run npx skills add wondelai/skills/ux-heuristics --global. It takes about 30 seconds and needs no account. The UX Heuristics skill then works in Claude, Claude Code, Claude Cowork, Codex, Cursor, OpenClaw and Hermes Agent — anything that reads the open agentskills.io format — and your agent loads it on its own when a task calls for it. It is free and MIT-licensed, and the source is at https://github.com/wondelai/skills.
Which book is the UX Heuristics skill based on?
It packages Don’t Make Me Think by Steve Krug & Jakob Nielsen — pioneering usability experts and co-founders of modern UX. The skill distils the book's method into instructions your agent follows while it works, covering visibility of system status, recognition over recall and error prevention. It sits in the Design & UX part of the library.
What do Nielsen’s heuristics do that Krug’s laws don’t?
They do different halves of the job. Nielsen’s ten are an inspection checklist — system status, user control, error prevention, recognition over recall — designed so a reviewer covers the whole surface instead of noticing whatever catches their eye. Krug supplies the standard those violations are judged against: people scan rather than read, satisfice rather than optimise, and muddle through rather than learn. The skill enumerates with Nielsen and sets the bar with Krug.
Can a heuristic evaluation replace user testing?
No, and treating it as a substitute is the most common misuse. Expert inspection finds violations of known principles; it cannot tell you whether people want the feature, what they expected instead, or why they gave up. It was designed as a cheap pre-filter — clear the obvious problems before you spend a session on them. Krug himself argued for small, frequent tests with a handful of real users alongside it.
How is this different from the Design of Everyday Things skill?
Scope and output. Norman gives you a theory of why interaction fails at all, applicable to a stove as much as a checkout. This skill is narrower and more procedural: it walks your actual screens, tags each issue against a named heuristic, scores severity, and hands back a triage list. Use Norman when you are arguing about a design; use this when you need something a team can work through on Monday.
Does it cover accessibility?
Partly, and you should know where the line is. It flags the usability-adjacent things — unlabelled controls, low contrast, tap targets too small, focus and status that only exist visually, and dark patterns that pressure users. It is not a WCAG conformance audit and will not check your ARIA semantics or run assistive-technology testing. Treat what it finds as a floor, not a compliance report.
09 Guides that use it
Put it to work.
Long-form playbooks where this skill does part of the job.
One skill, one command.
Install UX Heuristics, or the whole stack.
npx skills add wondelai/skills/ux-heuristics --global MIT licensed · Claude, Claude Code, Codex, Cursor, OpenClaw, Hermes · No account