mental-model-alignment

Identify mismatches between design model, system image, and user model.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill mental-model-alignment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mental-model-alignment
Source: https://github.com/NlightNFotis/skills/tree/main/mental-model-alignment
Command: npx skills add https://github.com/NlightNFotis/skills --skill mental-model-alignment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose why users, developers, and the product itself seem to disagree about how a feature works. It is built for situations where the system behaves as designed, but confusing interfaces, hidden state, naming drift, or weak feedback cause repeated mistakes, support churn, and avoidable frustration.

Core Features & Use Cases

  • Three-model analysis: Compares the design model, system image, and user model to pinpoint where understanding breaks down.
  • Journey-based mismatch review: Walks a specific user task step by step to identify execution gulfs, evaluation gulfs, and concrete mismatch types such as hidden state, false affordances, or implementation leakage.
  • Fix prioritization: Recommends whether to solve the issue through behavior changes, interface and messaging improvements, or documentation as a last resort.
  • Use case: Review a CLI, dashboard, or workflow that keeps generating “user error” reports and determine whether the real problem is a misleading mental model created by the product.

Quick Start

Ask the mental-model-alignment skill to analyze one user journey where people repeatedly misunderstand a feature and recommend the highest-leverage fixes.

Frequently Asked Questions about mental-model-alignment

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

FAQPage Schema
How do I find UX mismatches that cause user confusion and perceived bugs?

To find UX mismatches causing user confusion, you analyze the gaps between the design model, system image, and user model. This process identifies execution and evaluation gulfs where hidden state or misleading feedback creates perceived bugs.

What is a mental model mismatch in interface design?

A mental model mismatch in interface design occurs when a product's system image contradicts user expectations, causing misuse. It happens when naming drift, implementation leakage, or false affordances mislead users about how a feature actually works.

How do I analyze a CLI or dashboard generating repeated user error reports?

Analyze a CLI or dashboard with repeated user errors by walking the specific user journey step by step. This identifies exact mismatch types like hidden state or ambiguous feedback and recommends whether to fix behavior, interface, or documentation.

Can I use mental model analysis to investigate support tickets for hidden state issues?

Yes, you can use mental model analysis to investigate support tickets by identifying hidden state or weak feedback causing the reported confusion. It categorizes the mismatch and prioritizes fixes across behavior, interface, and documentation layers.

What is the best way to prioritize UX fixes for misleading product features?

The best way to prioritize UX fixes for misleading features is to categorize mismatches by severity and recommend solutions starting with behavior changes, then interface improvements, using documentation only as a last resort.

Why does my product feature work as designed but users still report it as broken?

Users report properly designed features as broken when confusing interfaces or hidden state create a misleading mental model. The system behaves correctly, but the gap between the system image and user model causes perceived bugs and frustration.