design-everyday-things

Diagnose usability breakdowns using Norman's principles of affordances, signifiers, mappings, constraints, and feedback.

7|1|Updated May 14, 2026
One-click install
npx skills add https://github.com/klarbau/govtech-de --skill design-everyday-things-klarbau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-everyday-things
Source: https://github.com/klarbau/govtech-de/tree/main/.claude/skills/design-everyday-things
Command: npx skills add https://github.com/klarbau/govtech-de --skill design-everyday-things-klarbau

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you diagnose why a design feels confusing, hard to discover, or easy to misuse, and then turn those findings into concrete UX improvements.

Core Features & Use Cases

  • Usability diagnosis: Evaluate affordances, signifiers, mappings, constraints, feedback, and conceptual models in one pass.
  • Error reduction: Find the root causes of slips, mistakes, hidden modes, and unclear system state before they frustrate users.
  • Workflow review: Analyze forms, navigation, status messages, and multi-step journeys for the Gulf of Execution and the Gulf of Evaluation.
  • Use case: Review a checkout flow, a settings page, or a public-service portal and identify the exact design changes that will make it more intuitive.

Quick Start

Ask the Skill to critique a screen, flow, or error message using Norman's principles and return the highest-impact fixes first.

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 usability breakdowns in a user interface?

Diagnose usability breakdowns by evaluating weak affordances, unclear signifiers, poor mappings, missing constraints, and inadequate feedback. This structured evaluation identifies the root causes of slips and mistakes, revealing exact design changes needed to make products more intuitive.

What is the Gulf of Execution and Evaluation in UX workflow review?

The Gulf of Execution and Evaluation represents the gap between user intentions and system state understanding. Analyzing multi-step journeys, forms, and navigation for these gulfs identifies missing feedback and mapping issues that prevent intuitive task completion.

How do I fix confusing error messages and hidden modes in a product?

Fix confusing error messages and hidden modes by analyzing human error patterns and conceptual model mismatches. Redesigning status messages and applying strict constraints prevents slips and mistakes, ensuring system state remains clear to the user.

Can I apply human-centered design critique to physical-digital embedded systems?

Human-centered design critique applies to physical-digital interaction analysis across web, mobile, and embedded systems. Evaluating affordances and signifiers ensures that both physical and digital touchpoints provide clear feedback and intuitive mappings.

What's the best way to review a multi-step checkout flow for usability issues?

The best way to review a checkout flow is evaluating its Gulf of Execution and Gulf of Evaluation. Assess mappings, constraints, and feedback mechanisms to find the highest-impact fixes that reduce user error and make the journey more error-proof.

Why does my onboarding flow feel hard to discover and easy to misuse?

An onboarding flow feels hard to discover and easy to misuse due to weak affordances and unclear signifiers. Diagnosing conceptual model mismatches and inadequate feedback highlights the exact design changes required to improve intuitiveness.