design-everyday-things

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

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill design-everyday-things-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-everyday-things
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/design-everyday-things
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill design-everyday-things-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Users blame themselves when products confuse them, but the fault is almost always in the design. This Skill gives you Don Norman's foundational framework to diagnose why users make mistakes, bridge the gulfs of execution and evaluation, and redesign interactions so they are discoverable and understandable. ## Core Features & Use Cases - Seven Design Principles: Apply affordances, signifiers, mappings, constraints, feedback, and conceptual models to evaluate any interface or product. - Error Analysis: Classify slips and mistakes, then design prevention (constraints, undo, confirmation) and recovery (clear error messages) mechanisms. - Usability Scoring: Rate designs 0-10 on discoverability, understandability, and error prevention, with concrete improvements to reach 10/10. - Use Case: A user asks why customers keep clicking the wrong button in a checkout flow. Walk through the seven stages of action, identify missing signifiers and poor mapping, and propose constraints and feedback fixes. ## Quick Start Review this checkout form using the design-everyday-things framework and tell me why users keep submitting it with errors.

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 product confusing?▼

Analyze the two gulfs: execution (can users figure out what to do?) and evaluation (do they understand what happened?). Check discoverability through affordances, signifiers, constraints, mappings, and feedback, then walk the seven stages of action to find where users get stuck.

What is the difference between affordances and signifiers in UX design?▼

Affordances define what actions are possible between an object and a user, while signifiers communicate where and how to perform those actions. A button affords clicking; its color, label, and hover state are signifiers showing you to click it.

How do I prevent user errors in form design?▼

Use constraints to make wrong actions impossible: input validation, disabled states for invalid options, and forced sequences. Add undo for destructive actions, sensible defaults, and error messages that explain what went wrong and how to fix it without blaming the user.

When should I use this framework instead of usability heuristics?▼

Use this framework for foundational diagnosis of why interactions fail, such as confusing controls, poor feedback, or mismatched mental models. For heuristic-based usability scoring, the skill itself points to ux-heuristics, and for iOS patterns it points to ios-hig-design.

Why do users blame themselves for design failures?▼

Norman's core insight is that there is no human error, only bad design. When the system image fails to communicate a correct conceptual model, users form wrong mental models and blame themselves. The fix is redesigning signifiers, feedback, and mappings, not retraining users.