ux-evaluation

Evaluate product interfaces using Garrett's layered UX framework with per-layer reference guides.

3|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ever-just/agentskills --skill ux-evaluation-ever-just
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-evaluation
Source: https://github.com/ever-just/agentskills/tree/main/skills/ux-evaluation
Command: npx skills add https://github.com/ever-just/agentskills --skill ux-evaluation-ever-just

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? UX problems are often misdiagnosed: a visual complaint is treated with a visual fix when the real cause lives in strategy, scope, or structure. This Skill gives you a layered framework (Strategy, Scope, Structure, Skeleton, Surface) based on Jesse James Garrett's Elements of User Experience, so you can locate any UX question on the correct layer before recommending changes. ## Core Features & Use Cases - Layered diagnosis: Route any UX question to the right layer using a routing table covering strategy, scope, interaction design, information architecture, interface design, navigation design, information design, layout primitives, domain components, and visual design. - Per-layer reference guides: Ten reference files with definitions, evaluation questions, common failure modes, canonical sources, and diagnostic prompts for each layer. - Feature slicing: Structure feature briefs as vertical slices through the layers to detect altitude mismatches, gaps, and cascade costs. - Use Case: When asked "is this a UI problem or a deeper problem?", the Skill walks top-down from Strategy to Surface, reads the relevant references, and states explicitly which layer the cause lives on rather than proposing a surface fix for a structure problem. ## Quick Start Use the ux-evaluation skill to audit this product interface and tell me which layer the main problem actually lives on.

Frequently Asked Questions about ux-evaluation

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

FAQPage Schema
How do I evaluate whether a UX problem is a UI problem or something deeper?▼

Locate the symptom on Garrett's layered framework: Strategy, Scope, Structure, Skeleton, or Surface. Symptoms appear at the bottom but causes usually live higher up, so read the reference file for each candidate layer and diagnose at the level where the cause actually originates.

What is the difference between interaction design and interface design?▼

Interaction design sits on the Structure plane and defines what should happen when the user acts: flows, feedback timing, and error recovery. Interface design sits one plane below on Skeleton and defines the actual controls, form systems, and state vocabulary that render those behaviors.

How do I structure a feature brief so design and engineering stay aligned?▼

Write the feature as a vertical slice through the layers: the user need at Strategy, the capability at Scope, entities and flows at Structure, components and layouts at Skeleton, and any new tokens at Surface. Empty layers expose gaps, and naming layers prevents altitude mismatches in discussion.

Does this framework apply to a specific design system like Material or Apple HIG?▼

No, the framework is system-agnostic. Material Design and Apple HIG are implementations of the layers, not the layers themselves, so the evaluation criteria apply to any digital interface regardless of platform, framework, or tech stack.

What are layout primitives and when should I use them?▼

Layout primitives are irreducible spatial relationships like Stack, Cluster, Sidebar, and Grid from Every Layout. Use them as the composable substrate beneath interface and navigation design so spacing stays token-driven and layouts are described as trees of named primitives rather than bespoke CSS.