design-ui-usability-principles

Diagnose confusing or error-prone interfaces using Don Norman's usability principles.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/scanady/nexus-skills --skill design-ui-usability-principles-scanady
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-ui-usability-principles
Source: https://github.com/scanady/nexus-skills/tree/main/skills/design-ui-usability-principles
Command: npx skills add https://github.com/scanady/nexus-skills --skill design-ui-usability-principles-scanady

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Users blame themselves when a product is confusing, but the fault is almost always the design. This Skill gives you a structured diagnostic framework to locate exactly why an interface fails — a broken affordance, a missing signifier, an arbitrary mapping, absent constraints, silent feedback, or a mismatched conceptual model — and name the category of fix. ## Core Features & Use Cases - Two Gulfs Analysis: Walk the Gulf of Execution and Gulf of Evaluation for any task to find where users get stuck. - Seven-Principle Diagnosis: Systematically check discoverability, affordances, signifiers, mappings, constraints, feedback, and conceptual models against reference guides. - Error Classification: Distinguish slips from mistakes, trace each to its design cause, and layer defenses (constraints, warnings, feedback, undo, recovery). - Use Case: Users keep deleting the wrong item in your app. Walk the seven stages of action, classify the error as an adjacent-target slip, and fix it with distance, distinct styling, and undo instead of another confirmation dialog. ## Quick Start Ask the AI to diagnose why users keep making a specific mistake in your interface using Norman's usability principles.

Frequently Asked Questions about design-ui-usability-principles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I figure out why users find my interface confusing?▼

Score the design's discoverability and understandability, then walk the task through the two gulfs and seven stages of action. Each failure maps to a principle — affordances, signifiers, mappings, constraints, feedback, or conceptual models — which names both the problem and the fix category.

What is the difference between a slip and a mistake in UX design?▼

A slip is a correct intention executed wrongly, caused by attention or motor failures like adjacent targets or mode confusion. A mistake is a wrong intention from a faulty mental model or rule. Slips need distinct, recoverable actions; mistakes need better conceptual models and information.

When should I use this skill instead of a visual design review?▼

Use this skill to diagnose why users cannot figure out or complete tasks — the diagnostic layer. Use a visual-refactor skill for spacing, hierarchy, and color of an existing UI, and a microinteractions skill for choreographing a single interaction.

How do I prevent user errors without adding more confirmation dialogs?▼

Prevent errors with constraints that make wrong actions impossible, such as input validation, pickers, and disabled states with explanations. Reserve confirmation dialogs for irreversible or high-consequence actions only, since routine confirmations breed dialog blindness.

What are the limitations of a heuristic usability diagnosis?▼

A principles-based diagnosis identifies likely failure categories but cannot replace observing real users. It works best combined with usability testing, think-aloud sessions, and error-rate tracking to confirm which diagnosed issues actually affect task completion.