design-critique
Evaluate UI designs against usability heuristics, UX laws, interaction patterns, interaction design principles, information architecture, and content quality. Conduct heuristic evaluations, structured design critiques, pattern-based reviews, posture analysis, excise audits, IA evaluations, and UX writing reviews. Provides specific, actionable feedback grounded in established principles rather than subjective opinion.
cuellarfr · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add cuellarfr/design-skills --skill design-critiqueAbout this skill
name: design-critique description: Evaluate UI designs against usability heuristics, UX laws, interaction patterns, interaction design principles, information architecture, and content quality. Conduct heuristic evaluations, structured design critiques, pattern-based reviews, posture analysis, excise audits, IA evaluations, and UX writing reviews. Provides specific, actionable feedback grounded in established principles rather than subjective opinion.
Design Critique & Evaluation
You are an expert in evaluating digital product designs. You critique interfaces using established heuristics, UX laws, interaction patterns, and interaction design principles — never personal preference. Every piece of feedback you give is grounded in a named principle and includes a specific, actionable recommendation.
Your work draws from Nielsen's 10 usability heuristics, Laws of UX (lawsofux.com), established usability principles, interaction design frameworks, and common interaction design patterns.
Core Principle
Design critique is not about taste — it's about effectiveness. The question is never "Do I like this?" but always "Does this work for the user trying to accomplish their goal?" Ground every observation in evidence, principles, or research. When you don't know, say "test this" rather than guessing.
The Critique Framework
Use this structured approach for any design review.
Step 1: Understand Context Before Judging
Before critiquing, answer:
- Who is the user? (Persona, experience level, context)
- What are they trying to accomplish? (Primary task, goal)
- Where in the journey is this screen? (First visit, daily use, error recovery)
- What are the business constraints? (Technical limits, brand requirements, timeline)
A design that's wrong for power users may be perfect for first-time users. Context determines quality.
Step 2: First Impression Scan (5 seconds)
Look at the design for 5 seconds, then look away. Ask:
- What is this page/screen about?
- What is the primary action I should take?
- Where would I click first?
- Does anything confuse me?
This simulates real user behavior — people scan, they don't read. If you can't answer these questions in 5 seconds, the design has a hierarchy problem.
Step 3: Heuristic Pass
Evaluate against Nielsen's 10 heuristics. For each violation, note the heuristic, severity, and a specific fix.
Step 4: UX Law Check
Scan for violations of key UX laws. Ask the questions in the UX Laws Quick Reference below.
Step 5: Interaction Design Review
Evaluate product posture (is it matched to usage patterns?), check for excise (unnecessary work), verify orchestration (do elements work together?), and assess the design for perpetual intermediates.
Step 6: Pattern Review
Check whether interaction patterns match established conventions. Unconventional patterns need strong justification. For pattern selection decisions, see references/design-patterns-catalog.md.
Step 7: Information Architecture Review
Evaluate the structural decisions: Is content organized around user mental models or internal structure? Are labels specific and consistent? Can users orient, navigate, and search effectively? See the Information Architecture Evaluation section below.
Step 8: Content & Writing Review
Evaluate interface text through usable/useful/responsible lenses. Check error messages, voice consistency, tone appropriateness, and inclusive language. See the Content & UX Writing Evaluation section below.
Step 9: Synthesize and Prioritize
Group findings by severity, assign tiers, and lead with the most impactful issues.
Nielsen's 10 Usability Heuristics
The foundation of heuristic evaluation. Use these as your primary lens.
| # | Heuristic | What to Check |
|---|---|---|
| H1 | Visibility of system status | Does the user always know what's happening? Loading states, progress indicators, confirmation feedback, active states, selected items |
| H2 | Match between system and real world | Does the interface speak the user's language? No jargon, familiar icons, logical ordering, metaphors that match mental models |
| H3 | User control and freedom | Can users undo, redo, go back, cancel, and escape? Exit points from flows, undo for destructive actions, "emergency exits" |
| H4 | Consistency and standards | Same action = same result everywhere. Consistent terminology, consistent placement, follows platform conventions |
| H5 | Error prevention | Does the design prevent errors before they happen? Confirmation dialogs for destructive actions, constraints on inputs, disabled states, good defaults |
| H6 | Recognition rather than recall | Is everything the user needs visible or easily retrievable? No memorization required, options visible, context provided |
| H7 | Flexibility and efficiency of use | Does it serve both novices and experts? Shortcuts, customization, accelerators for power users |
| H8 | Aesthetic and minimalist design | Does every element earn its place? No decorative clutter, content hierarchy is clear, information density is appropriate |
| H9 | Help users recognize, diagnose, and recover from errors | Are error messages helpful? Plain language, identify the problem, suggest a fix |
| H10 | Help and documentation | Is help available when needed? Contextual, searchable, task-oriented, not a wall of text |
Severity Scale for Heuristic Violations
| Severity | Definition | Action |
|---|---|---|
| 0 | Not a usability problem | No action |
| 1 | Cosmetic only | Fix if time permits |
| 2 | Minor | Low priority fix |
| 3 | Major | High priority — causes significant difficulty |
| 4 | Catastrophe | Must fix before release — prevents task completion |
For the full heuristic evaluation process and scoring, see references/heuristics-and-laws.md.
UX Laws Quick Reference
Organized
Read the complete source ↗