Stats
Actions
Tags
From mycelium
Evaluates user-facing UI against Nielsen's 10 Usability Heuristics with checklists. Use for L4 delivery reviews, post-UI implementation, or user friction reports.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mycelium:usability-checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Evaluate interface-level usability using Jakob Nielsen's 10 heuristics (1994). This complements Downe's 15 Good Services principles: Downe checks end-to-end SERVICE quality, Nielsen checks screen-level INTERFACE quality. Both are needed for user-facing work.
Evaluate interface-level usability using Jakob Nielsen's 10 heuristics (1994). This complements Downe's 15 Good Services principles: Downe checks end-to-end SERVICE quality, Nielsen checks screen-level INTERFACE quality. Both are needed for user-facing work.
The system should always keep users informed about what is going on through timely and appropriate feedback.
The system should speak the users' language, using familiar words, phrases, and concepts rather than system-oriented terms.
Users often perform actions by mistake. They need a clearly marked "emergency exit" to leave the unwanted action.
Users should not have to wonder whether different words, situations, or actions mean the same thing.
Even better than good error messages is a careful design that prevents problems in the first place.
Minimize the user's memory load by making elements, actions, and options visible.
Accelerators — unseen by the novice user — may speed up the interaction for the expert user.
Dialogues should not contain information that is irrelevant or rarely needed.
Error messages should be expressed in plain language, precisely indicate the problem, and constructively suggest a solution.
Even though it is better if the system can be used without documentation, it may be necessary to provide help.
## Usability Heuristic Evaluation
| Heuristic | Status | Issues |
|-----------|--------|--------|
| 1. Visibility of status | pass/partial/fail | ... |
| 2. Match real world | pass/partial/fail | ... |
| 3. User control & freedom | pass/partial/fail | ... |
| 4. Consistency & standards | pass/partial/fail | ... |
| 5. Error prevention | pass/partial/fail | ... |
| 6. Recognition > recall | pass/partial/fail | ... |
| 7. Flexibility & efficiency | pass/partial/fail | ... |
| 8. Aesthetic & minimal | pass/partial/fail | ... |
| 9. Error recovery | pass/partial/fail | ... |
| 10. Help & documentation | pass/partial/fail | ... |
Overall: [X]/10 passing
Priority fixes: [list most impactful issues]
npx claudepluginhub haabe/mycelium --plugin myceliumEvaluates user interfaces using Nielsen's 10 usability heuristics to identify violations like poor system status visibility, inconsistency, and error-prone designs. Reports severity, location, and fixes for UX reviews.
Conducts usability review using Nielsen's 10 heuristics to identify interface problems without user testing.
Evaluates UI implementations against Nielsen's 10 usability heuristics, Norman's principles, and Krug's laws. Runs alongside quality-review at the review phase.