UX Evaluator
Overview
Systematically evaluate UI components against established UX principles using a 3-dimension framework. Transform subjective design feedback into actionable, evidence-based recommendations by comparing against industry conventions and authoritative sources.
Core Value: Prevents subjective design debates by grounding decisions in documented best practices.
When to Use This Skill
Triggers:
- User provides UX feedback on a component
- User references external design guidelines (Balsamiq, Nielsen, Material Design)
- User asks to "review", "evaluate", or "check" UI elements
- User questions button labels, spacing, or visual hierarchy
- Before implementing UI changes that affect user interaction
Do NOT use for:
- Pure visual aesthetics (colors, fonts) without UX implications
- Backend or non-UI changes
- When user has already made a firm decision and just wants implementation
Evaluation Framework
The 3-Dimension Analysis
For ANY UI component, evaluate these three dimensions:
| Dimension |
What to Analyze |
Key Questions |
| 1. Position |
Where is it located relative to other elements? |
Does position follow conventions? Is it discoverable? |
| 2. Visual Weight |
How prominent is it visually? |
Does it compete with primary actions? Is hierarchy clear? |
| 3. Spacing |
What's the gap from adjacent elements? |
Is there adequate separation? Is spacing consistent? |
Evaluation Workflow
Step 1: GATHER CONTEXT
├── What component is being evaluated?
├── What user feedback or concern triggered this?
├── Is there an external reference (article, guideline)?
└── What is the component's purpose (primary CTA, utility, navigation)?
Step 2: ANALYZE CURRENT STATE
├── Position: Document exact location in layout
├── Visual Weight: Describe styling (filled, ghost, icon-only, etc.)
├── Spacing: Measure gaps from adjacent elements
└── Compare to industry conventions (see references/)
Step 3: PRODUCE VERDICT
├── For each dimension: CORRECT / NEEDS CHANGE / ACCEPTABLE
├── If NEEDS CHANGE: Specific recommendation with rationale
├── Reference authoritative source for each recommendation
└── Prioritize changes (P1: breaks UX, P2: suboptimal, P3: polish)
Component-Specific Guidelines
Buttons (Action Elements)
Position:
- Primary action (Sign Up, Submit, Buy) → RIGHT side
- Secondary action (Cancel, Sign In) → LEFT of primary
- Utility controls (theme, settings) → FAR RIGHT after primary actions
Visual Weight:
- Primary: Filled background, brand color, shadow
- Secondary: Ghost/outline, no fill, subtle border
- Utility: Icon-only or minimal text, neutral color
Spacing:
- Between button groups: 1.5rem (24px) minimum
- Between buttons in same group: 0.5rem-0.75rem (8-12px)
- Touch targets: 44px minimum height on mobile
Labels:
- Use conventional labels: "Sign Up" not "Get Started", "Sign In" not "Login"
- Say exactly what happens: "Delete Account" not "Proceed"
- Verb-first for actions: "Create Project", "Send Message"
Navigation Elements
Position:
- Logo → LEFT
- Primary nav → CENTER or after logo
- Utility items (search, auth, theme) → RIGHT
Visual Weight:
- Active state clearly distinguished
- Current page indicator visible
- Don't compete with page content
Spacing:
- Group related items visually
- Clear separation between nav groups
- Adequate click/tap targets
Form Elements
Position:
- Labels above or to the left of inputs
- Submit button at bottom, right-aligned or full-width
- Error messages adjacent to field
Visual Weight:
- Required fields marked clearly
- Error states prominent (red border/text)
- Success states confirmatory (green checkmark)
Spacing:
- Consistent vertical rhythm between fields
- Label-to-input gap: 0.25-0.5rem
- Field-to-field gap: 1-1.5rem
Industry Conventions Reference
Button Order (Major Sites)
| Site |
Pattern |
| GitHub |
[Sign In] [Sign Up] - secondary left, primary right |
| Stripe |
[Sign In] [Start now →] - secondary left, primary right |
| Google |
[Sign In] [Create account] - same pattern |
| Notion |
[Log in] [Get Notion free] - same pattern |
Verdict: Secondary LEFT, Primary RIGHT is the standard.
Theme Toggle Placement
| Site |
Placement |
| GitHub |
Far right, after user menu |
| VS Code Docs |
Far right |
| Stripe Docs |
Far right |
| Discord |
In settings, not navbar |
Verdict: Far right (after auth) or in settings dropdown.
Utility Control Visual Weight
| Control |
Expected Weight |
| Theme toggle |
Icon-only, subtle, doesn't compete with CTAs |
| Search |
Icon trigger or compact input, expandable |
| Language selector |
Icon or compact dropdown |
Verdict: Utilities should be accessible but subordinate to primary actions.
Output Format
When evaluating a component, produce this structured output:
## [Component Name] Evaluation
### Current State
- **Position**: [Description]
- **Visual Weight**: [Description]
- **Spacing**: [Measurements]
### Analysis
| Dimension | Assessment | Rationale |
|-----------|------------|-----------|
| Position | [OK/CHANGE] | [Why, with reference] |
| Visual Weight | [OK/CHANGE] | [Why, with reference] |
| Spacing | [OK/CHANGE] | [Why, with reference] |
### Verdict: [CORRECT / NEEDS CHANGES]
### Recommendations (if any)
| Priority | Change | Rationale |
|----------|--------|-----------|
| P1 | [Specific change] | [Reference to principle] |
| P2 | [Specific change] | [Reference to principle] |
References
See references/ for detailed UX principles:
balsamiq-button-principles.md - Button design best practices
nielsen-heuristics.md - 10 usability heuristics (to be added)
Self-Monitoring
Before finalizing evaluation:
1---2name: ux-evaluator3description: This skill should be used when evaluating UI components against UX best practices. Use for reviewing buttons, navigation elements, spacing, visual hierarchy, or any interface element. Provides a systematic 3-dimension framework (Position, Visual Weight, Spacing) aligned with industry standards (Balsamiq, Nielsen heuristics). Invoke when user asks to "review UX", "check button design", "evaluate layout", or references design guidelines.4metadata:5 source: https://skillmd.com/skills/mjunaidca/ux-evaluator6---78# UX Evaluator910## Overview1112Systematically evaluate UI components against established UX principles using a 3-dimension framework. Transform subjective design feedback into actionable, evidence-based recommendations by comparing against industry conventions and authoritative sources.1314**Core Value**: Prevents subjective design debates by grounding decisions in documented best practices.1516## When to Use This Skill1718**Triggers**:19- User provides UX feedback on a component20- User references external design guidelines (Balsamiq, Nielsen, Material Design)21- User asks to "review", "evaluate", or "check" UI elements22- User questions button labels, spacing, or visual hierarchy23- Before implementing UI changes that affect user interaction2425**Do NOT use for**:26- Pure visual aesthetics (colors, fonts) without UX implications27- Backend or non-UI changes28- When user has already made a firm decision and just wants implementation2930## Evaluation Framework3132### The 3-Dimension Analysis3334For ANY UI component, evaluate these three dimensions:3536| Dimension | What to Analyze | Key Questions |37|-----------|-----------------|---------------|38| **1. Position** | Where is it located relative to other elements? | Does position follow conventions? Is it discoverable? |39| **2. Visual Weight** | How prominent is it visually? | Does it compete with primary actions? Is hierarchy clear? |40| **3. Spacing** | What's the gap from adjacent elements? | Is there adequate separation? Is spacing consistent? |4142### Evaluation Workflow4344```45Step 1: GATHER CONTEXT46├── What component is being evaluated?47├── What user feedback or concern triggered this?48├── Is there an external reference (article, guideline)?49└── What is the component's purpose (primary CTA, utility, navigation)?5051Step 2: ANALYZE CURRENT STATE52├── Position: Document exact location in layout53├── Visual Weight: Describe styling (filled, ghost, icon-only, etc.)54├── Spacing: Measure gaps from adjacent elements55└── Compare to industry conventions (see references/)5657Step 3: PRODUCE VERDICT58├── For each dimension: CORRECT / NEEDS CHANGE / ACCEPTABLE59├── If NEEDS CHANGE: Specific recommendation with rationale60├── Reference authoritative source for each recommendation61└── Prioritize changes (P1: breaks UX, P2: suboptimal, P3: polish)62```6364## Component-Specific Guidelines6566### Buttons (Action Elements)6768**Position**:69- Primary action (Sign Up, Submit, Buy) → RIGHT side70- Secondary action (Cancel, Sign In) → LEFT of primary71- Utility controls (theme, settings) → FAR RIGHT after primary actions7273**Visual Weight**:74- Primary: Filled background, brand color, shadow75- Secondary: Ghost/outline, no fill, subtle border76- Utility: Icon-only or minimal text, neutral color7778**Spacing**:79- Between button groups: 1.5rem (24px) minimum80- Between buttons in same group: 0.5rem-0.75rem (8-12px)81- Touch targets: 44px minimum height on mobile8283**Labels**:84- Use conventional labels: "Sign Up" not "Get Started", "Sign In" not "Login"85- Say exactly what happens: "Delete Account" not "Proceed"86- Verb-first for actions: "Create Project", "Send Message"8788### Navigation Elements8990**Position**:91- Logo → LEFT92- Primary nav → CENTER or after logo93- Utility items (search, auth, theme) → RIGHT9495**Visual Weight**:96- Active state clearly distinguished97- Current page indicator visible98- Don't compete with page content99100**Spacing**:101- Group related items visually102- Clear separation between nav groups103- Adequate click/tap targets104105### Form Elements106107**Position**:108- Labels above or to the left of inputs109- Submit button at bottom, right-aligned or full-width110- Error messages adjacent to field111112**Visual Weight**:113- Required fields marked clearly114- Error states prominent (red border/text)115- Success states confirmatory (green checkmark)116117**Spacing**:118- Consistent vertical rhythm between fields119- Label-to-input gap: 0.25-0.5rem120- Field-to-field gap: 1-1.5rem121122## Industry Conventions Reference123124### Button Order (Major Sites)125126| Site | Pattern |127|------|---------|128| GitHub | [Sign In] [Sign Up] - secondary left, primary right |129| Stripe | [Sign In] [Start now →] - secondary left, primary right |130| Google | [Sign In] [Create account] - same pattern |131| Notion | [Log in] [Get Notion free] - same pattern |132133**Verdict**: Secondary LEFT, Primary RIGHT is the standard.134135### Theme Toggle Placement136137| Site | Placement |138|------|-----------|139| GitHub | Far right, after user menu |140| VS Code Docs | Far right |141| Stripe Docs | Far right |142| Discord | In settings, not navbar |143144**Verdict**: Far right (after auth) or in settings dropdown.145146### Utility Control Visual Weight147148| Control | Expected Weight |149|---------|-----------------|150| Theme toggle | Icon-only, subtle, doesn't compete with CTAs |151| Search | Icon trigger or compact input, expandable |152| Language selector | Icon or compact dropdown |153154**Verdict**: Utilities should be accessible but subordinate to primary actions.155156## Output Format157158When evaluating a component, produce this structured output:159160```markdown161## [Component Name] Evaluation162163### Current State164- **Position**: [Description]165- **Visual Weight**: [Description]166- **Spacing**: [Measurements]167168### Analysis169170| Dimension | Assessment | Rationale |171|-----------|------------|-----------|172| Position | [OK/CHANGE] | [Why, with reference] |173| Visual Weight | [OK/CHANGE] | [Why, with reference] |174| Spacing | [OK/CHANGE] | [Why, with reference] |175176### Verdict: [CORRECT / NEEDS CHANGES]177178### Recommendations (if any)179| Priority | Change | Rationale |180|----------|--------|-----------|181| P1 | [Specific change] | [Reference to principle] |182| P2 | [Specific change] | [Reference to principle] |183```184185## References186187See `references/` for detailed UX principles:188- `balsamiq-button-principles.md` - Button design best practices189- `nielsen-heuristics.md` - 10 usability heuristics (to be added)190191## Self-Monitoring192193Before finalizing evaluation:194- [ ] All 3 dimensions analyzed (Position, Visual Weight, Spacing)195- [ ] Current state documented with specifics (not vague descriptions)196- [ ] Each recommendation references an authoritative source or convention197- [ ] Compared against industry conventions (GitHub, Stripe, etc.)198- [ ] Priorities assigned (P1/P2/P3) based on UX impact199- [ ] Verdict is clear and actionable