← ClaudeAtlas

usability-checklisted

Evaluate user-facing interfaces against Nielsen's 10 Usability Heuristics. Complements /mycelium:service-check (Downe = service-level quality, Nielsen = interface-level quality).
haabe/mycelium · ★ 27 · AI & Automation · score 85
Install: claude install-skill haabe/mycelium
# Usability Heuristic Evaluation 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. ## When to Use - During L4 Delivery for any user-facing work (REVIEW via G-V10) - After UI implementation, before marking delivery complete - When users report confusion or friction ## The 10 Heuristics ### 1. Visibility of System Status The system should always keep users informed about what is going on through timely and appropriate feedback. - [ ] Loading states visible for any operation > 1 second - [ ] Progress indicators for multi-step processes - [ ] Success/failure feedback for user actions - [ ] Current location/state clearly indicated (breadcrumbs, active nav) ### 2. Match Between System and Real World The system should speak the users' language, using familiar words, phrases, and concepts rather than system-oriented terms. - [ ] No technical jargon in user-facing text - [ ] Familiar icons and metaphors - [ ] Information in natural, logical order - [ ] Real-world conventions followed (calendar = dates, cart = shopping) ### 3. User Control and Freedom Users often perform actions by mistake. They need a clearly marked "emergency exit" to leave the unwanted action. - [ ] Undo/redo available for destructive actions - [ ] Cancel option in all multi-step flows - [ ] Back button w