design-everyday-things

Diagnose usability problems using Norman's affordances, signifiers, constraints, feedback, and conceptual models.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/HafidJoss/Lummy --skill design-everyday-things-hafidjoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-everyday-things
Source: https://github.com/HafidJoss/Lummy/tree/main/agent/skills/design-everyday-things
Command: npx skills add https://github.com/HafidJoss/Lummy --skill design-everyday-things-hafidjoss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Users blame themselves when products confuse them, but the root cause is almost always design failure: missing signifiers, broken mappings, absent feedback, or mismatched mental models. This Skill gives you Don Norman's complete framework to diagnose why an interface is confusing and prescribe concrete fixes. ## Core Features & Use Cases - Seven Design Principles: Apply affordances, signifiers, mappings, constraints, feedback, conceptual models, and discoverability to audit any physical or digital product. - Error Analysis: Classify slips and mistakes, then design prevention (constraints, undo) and recovery (clear messages, preserved work) mechanisms. - Scored Diagnostic: Run the 5-row Quick Diagnostic to score designs out of 10 and identify which gulfs of execution or evaluation are broken. - Use Case: When users keep clicking the wrong control or abandoning a flow, walk the interaction through the Seven Stages of Action to pinpoint exactly where the design fails and which principle fixes it. ## Quick Start Ask the AI to audit your checkout flow using the Design of Everyday Things framework and score it with the Quick Diagnostic.

Frequently Asked Questions about design-everyday-things

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

FAQPage Schema
How do I diagnose why users find my interface confusing?

Run the Quick Diagnostic: check if users can figure out what to do, understand what happened, recover from errors, see control-output mapping, and are blocked from invalid options. Each failed row maps to a specific principle (signifiers, feedback, constraints) with concrete fixes.

What is the difference between an affordance and a signifier?

An affordance is what actions an object can support; a signifier communicates where and how to act. A button affords clicking, while its color, shadow, and label are signifiers showing it is clickable. Good design aligns perceived affordances with real ones.

How do I prevent user errors in form design?

Use constraints to make errors impossible: date pickers instead of free text, disabled submit until required fields are valid, input masks for phone numbers, and real-time inline validation. Add undo and soft-delete for recovery when errors still occur.

When should I use this framework versus usability heuristics?

Use this framework for foundational diagnosis of why interactions fail: discoverability, mental models, and the gulfs of execution and evaluation. For heuristic-based usability scoring of interfaces, the Skill itself directs you to a dedicated ux-heuristics skill.

Why do users keep making the same mistake with my product?

Repeated errors indicate design flaws, not user flaws. Classify the error as a slip (right intention, wrong action) or mistake (wrong intention), then fix the cause: separate destructive actions, show mode state, or correct the misleading conceptual model.