design-everyday-things

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

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/rachmadideni/ai-staff-assistant --skill design-everyday-things-rachmadideni
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-everyday-things
Source: https://github.com/rachmadideni/ai-staff-assistant/tree/main/.agents/skills/design-everyday-things
Command: npx skills add https://github.com/rachmadideni/ai-staff-assistant --skill design-everyday-things-rachmadideni

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 helps you diagnose why users make mistakes, why interfaces feel unintuitive, and how to fix discoverability, feedback, and error-prevention failures using Don Norman's foundational design principles. ## Core Features & Use Cases - Seven Design Principles: Apply affordances, signifiers, mappings, constraints, feedback, discoverability, and conceptual models to audit any physical or digital product. - Error Analysis: Classify slips and mistakes, then design constraints, undo, and clear error messages that prevent and recover from them. - Gulf & Stage Analysis: Bridge the gulfs of execution and evaluation using the seven stages of action framework. - Use Case: When users keep clicking the wrong button or abandoning a form, walk the interaction through the quick diagnostic checklist to pinpoint whether the failure is missing signifiers, poor mapping, or absent feedback, then apply the referenced fix patterns. ## Quick Start Ask the AI to audit your checkout flow using the Design of Everyday Things principles and score its discoverability, understandability, and error prevention out of 10.

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 keep making mistakes in my interface?▼

Classify the error as a slip (correct intention, wrong action) or a mistake (wrong intention), then identify the design cause. Use constraints to make wrong actions impossible, add undo for recovery, and write error messages that explain what happened and how to fix it.

What is the difference between an affordance and a signifier?▼

An affordance is the relationship between an object's properties and what actions it supports, while a signifier communicates where and how to act. Affordances determine what you can do; signifiers show you where and how to do it.

How do I fix poor discoverability in a product?▼

Add visible signifiers to every interactive element, align perceived affordances with real ones through visual treatment like shadows and hover states, and test with new users. If users cannot figure out what to do within 10 seconds, discoverability is broken.

When should I use this framework versus usability heuristics?▼

Use this framework for diagnosing root causes of confusion through conceptual models, mappings, and the gulfs of execution and evaluation. For structured usability scoring with heuristic checklists, the companion ux-heuristics skill is more appropriate.

Why do users blame themselves for design failures?▼

Users blame themselves because products fail to communicate their conceptual model through the system image. When the user's mental model mismatches the design model, errors feel like personal faults, but the fix is improving signifiers, feedback, and visible system state.