Conduct expert heuristic evaluations using Nielsen's heuristics and domain-specific criteria.
--- name: heuristic-evaluation description: Run an expert review against Nielsen's heuristics and domain criteria, with severity ratings. Use when you need findings without recruiting participants. For a facilitated team feedback session, use `design-critique` (design-ops). --- # 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--- name: heuristic-evaluation description: Run an expert review against Nielsen's heuristics and domain criteria, with severity ratings. Use when you need findings without recruiting participants. For a facilitated team feedback session, use `design-critique` (design-ops). --- # 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
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.