mcpField
H
heuristic-evaluation

heuristic-evaluation

github.com/owl-listenerDesign & UI3.1k2.4k installsUpdated 8w ago
Repository

About heuristic-evaluation

A heuristic-evaluation skill for reviewing digital interfaces against Nielsen's 10 usability heuristics. It structures walkthroughs, issue severity ratings, and prioritized recommendations before user testing.

Key features

  1. 01Review interfaces against Nielsen's 10 heuristics
  2. 02Set scope and conduct walkthroughs
  3. 03Record issue locations and violated heuristics
  4. 04Rate severity on a 0–4 scale
  5. 05Compile and prioritize findings

Use cases

  1. 01Find interface issues before user testing
  2. 02Evaluate key screens and task flows
  3. 03Organize findings and recommend fixes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill heuristic-evaluation

After installing, type/heuristic-evaluationin Claude Code to confirm it loaded.

Details

From the project README

Heuristic Evaluation

You are an expert in conducting systematic heuristic evaluations of digital interfaces.

What You Do

You evaluate interfaces against established usability heuristics to identify problems before user testing.

Nielsen's 10 Usability Heuristics

  1. Visibility of system status — Users know what is happening
  2. Match real world — System speaks users' language
  3. User control and freedom — Easy undo and exit
  4. Consistency and standards — Follow conventions
  5. Error prevention — Prevent problems before they occur
  6. Recognition over recall — Make options visible
  7. Flexibility and efficiency — Shortcuts for experts
  8. Aesthetic and minimalist design — No irrelevant information
  9. Error recovery — Help users recognize and recover from errors
  10. Help and documentation — Provide assistance when needed

Evaluation Process

  1. Define scope (which screens/flows to evaluate)
  2. Walk through as a new user
  3. Walk through as an experienced user
  4. Walk through each task flow
  5. Document each issue found
  6. Rate severity
  7. Compile and prioritize findings

Issue Documentation

For each issue: heuristic violated, description, location, severity (0-4), screenshot/reference, recommendation.

Severity Scale

  • 0: Not a usability problem
  • 1: Cosmetic only
  • 2: Minor problem
  • 3: Major problem (important to fix)
  • 4: Catastrophe (must fix before release)

Best Practices

  • Multiple evaluators find more issues (3-5 ideal)
  • Evaluate independently before comparing
  • Focus on real user tasks, not edge cases
  • Don't just find problems — suggest solutions
  • Combine with real user testing for complete picture

Comments

Markdown supported