design-everyday-things

Analyze product usability using Don Norman's design principles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses user confusion and product complexity by applying foundational design principles to ensure products are discoverable, understandable, and error-resistant.

Core Features & Use Cases

  • Usability Diagnostics: Evaluate products using the Seven Stages of Action and the Two Gulfs (Execution and Evaluation).
  • Design Pattern Analysis: Apply affordances, signifiers, mappings, and constraints to improve interface clarity.
  • Use Case: Use this Skill when users report that a feature is unintuitive or when you need to audit a new interface to ensure that interactive elements are clearly signaled and error paths are minimized.

Quick Start

Use the design-everyday-things skill to audit the current checkout flow and identify potential gulfs of execution or evaluation.

Frequently Asked Questions about design-everyday-things

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

FAQPage Schema
How do I evaluate product usability using the Seven Stages of Action?

To evaluate product usability, analyze the Two Gulfs of Execution and Evaluation to identify where users struggle to understand system state or formulate actionable goals. This diagnostic maps user confusion to specific design flaws in your interface.

What are affordances and signifiers in human-centered interface design?

Affordances are the actionable possibilities of a product, while signifiers are visual indicators that communicate where and how those actions occur. Analyzing both ensures interactive elements are clearly signaled and users understand what steps to take next.

How do I audit a digital checkout flow for discoverability and error prevention?

Audit a digital checkout flow by applying foundational design principles to trace user paths, identify missing feedback mechanisms, and detect missing constraints. This systematic process reduces complexity and prevents user errors before deployment.

Can I use this approach to reduce complexity in both physical and digital systems?

Yes, these foundational design principles apply to both physical and digital systems. By evaluating mappings, constraints, and feedback mechanisms universally, you can systematically reduce product complexity and improve discoverability across any interactive environment.

Why does my interface feel unintuitive even when all features are present?

An interface feels unintuitive when poor mappings and missing signifiers obscure functionality, creating a gulf of execution. Diagnosing these specific design flaws reveals why users cannot bridge the gap between their intentions and the available system actions.

What is the best way to identify design flaws related to user feedback mechanisms?

The best way to identify feedback flaws is to evaluate the Seven Stages of Action, checking whether the system provides clear, immediate responses to user inputs. This highlights where users lack the confirmation needed to evaluate their actions.