name: ui-ux-audit-guidelines
description: Professional UI/UX audit methodology and design vocabulary. Use when: conducting UI/UX audits, evaluating visual hierarchy, analyzing responsive design, assessing interaction patterns. Do NOT use for: code reviews, accessibility audits (WCAG), performance analysis, or security assessments.
UI/UX Audit Guidelines
This skill provides professional UI/UX audit methodology and evaluation criteria for comprehensive visual and interaction analysis.
Audit Viewports
Standard viewport configurations for responsive testing:
Mobile
- 428×926 - Large phone (iPhone 14 Pro Max equivalent)
Tablets
- 768×1024 - Portrait orientation (iPad portrait)
- 1024×768 - Landscape orientation (iPad landscape)
Desktop
- 1160×720 - Small desktop/laptop
- 1920×1080 - Large desktop (Full HD)
Evaluation Categories
1. Visual Hierarchy and Typography
Issues to identify:
- Unclear heading hierarchy (inconsistent size progression)
- Poor typographic scale (jumps between sizes too large/small)
- Insufficient weight contrast between headings and body
- Competing visual elements without clear focal points
- Inconsistent font families or weights
Terminology:
- Typographic scale, visual weight, font pairing
- Heading hierarchy, body text readability
- Line height (leading), letter spacing (tracking)
- Measure (line length), orphans and widows
2. Spacing and Layout
Issues to identify:
- Inconsistent vertical rhythm (varying spacing between elements)
- Irregular horizontal gutters
- Unbalanced whitespace distribution
- Overcrowded or overly sparse layouts
- Misaligned elements within the same context
Terminology:
- Padding, margin, gutter
- Vertical rhythm, baseline grid
- Breathing room, visual density
- Proximity principle, grouping
3. Grid and Alignment
Issues to identify:
- Elements breaking out of grid structure
- Inconsistent column spans
- Poor edge alignment between related elements
- Uneven container widths
- Misaligned form labels and inputs
Terminology:
- Grid system, column structure
- Edge alignment, center alignment
- Baseline alignment, optical alignment
- Proportional structure, golden ratio
4. Color and Contrast
Issues to identify:
- Insufficient text-to-background contrast (WCAG compliance)
- Unbalanced color weight distribution
- Overuse of accent colors
- Inconsistent color application across similar elements
- Poor use of color for state indication
Terminology:
- Contrast ratio, color weight
- Primary, secondary, accent colors
- Color temperature, saturation balance
- Semantic color usage
5. Navigation and Wayfinding
Issues to identify:
- Unclear active/current state indicators
- Poor discoverability of navigation elements
- Ambiguous or overly technical labeling
- Inconsistent navigation patterns across pages
- Missing breadcrumbs or context indicators
Terminology:
- Navigation hierarchy, active states
- Discoverability, affordance
- Information scent, wayfinding cues
- Progressive disclosure
6. Component Affordance and Interaction
Issues to identify:
- Buttons that don't look clickable
- Links that look like plain text
- Form elements with unclear boundaries
- Missing or weak hover/focus states
- Ambiguous interactive elements
Terminology:
- Affordance, signifiers
- Perceived affordance, learned affordance
- Interactive cues, click targets
- Touch target size, tap zones
7. Feedback States
Issues to identify:
- Missing hover states
- Unclear focus indicators
- No visual feedback for active/pressed states
- Missing disabled state styling
- Absent or inadequate loading indicators
Terminology:
- Hover state, focus ring, active state
- Disabled state, loading state
- Pressed state, selected state
- State transitions, micro-feedback
8. Dialog and Modal Behavior
Issues to identify:
- Modals not centered or poorly positioned
- Missing or broken backdrop/overlay
- No focus trap (can tab outside modal)
- Scroll not locked on body
- Missing close button or escape key handling
- Jarring or missing transitions
Terminology:
- Modal positioning, overlay opacity
- Focus trap, focus management
- Scroll lock, body scroll prevention
- Entry/exit transitions
9. Responsive Adaptation
Issues to identify:
- Content overflow at breakpoints
- Horizontal scrolling on mobile
- Touch targets too small on mobile
- Inappropriate layout patterns for viewport size
- Hidden content without proper disclosure
Terminology:
- Breakpoints, fluid layout
- Content reflow, stack order
- Mobile-first, responsive patterns
- Adaptive vs responsive design
10. Cross-Page Consistency
Issues to identify:
- Component styling variations between pages
- Inconsistent spacing scale usage
- Different typography treatment for same element types
- Color inconsistencies
- Varying interaction patterns
Terminology:
- Design system adherence
- Component consistency
- Pattern library compliance
- Visual language unity
11. Empty and Error States
Issues to identify:
- Generic or missing empty states
- Unhelpful zero-data views
- Missing first-time user guidance
- Unclear error messages
- No recovery path from errors
Terminology:
- Empty state design
- Zero-data state, blank slate
- Onboarding patterns
- Error recovery, graceful degradation
12. Loading Experiences
Issues to identify:
- No loading indication
- Jarring content jumps when loaded
- Inappropriate spinner vs skeleton usage
- Poor perceived performance
- Missing progress indicators for long operations
Terminology:
- Loading skeletons, shimmer effects
- Spinners, progress indicators
- Perceived performance
- Optimistic updates, lazy loading
13. Information Architecture
Issues to identify:
- Poor content grouping
- Unclear labeling or terminology
- High cognitive load from information density
- Missing or unclear section headers
- Illogical content ordering
Terminology:
- Information hierarchy
- Content grouping, chunking
- Cognitive load, mental models
- Labeling systems, taxonomy
14. Microinteractions and Transitions
Issues to identify:
- Missing subtle feedback animations
- Inconsistent animation timing/easing
- Jarring state changes without transitions
- Overuse of animation (distracting)
- Missing confirmation animations
Terminology:
- Microinteractions, motion design
- Easing curves, duration
- State transitions, animation choreography
- Feedback loops
15. Large Viewport Optimization
Issues to identify:
- Content stretching excessively on wide screens
- Oversized whitespace creating dead zones
- Tables or text blocks without max-width constraints
- Unused horizontal space
- Loss of visual hierarchy at scale
Terminology:
- Max-width constraints
- Content centering, container widths
- Widescreen optimization
- Layout scaling, proportional spacing
Improvement Recommendations Format
When suggesting improvements, use professional design language:
Good Examples
- "Establish a consistent 8px spacing scale across all components"
- "Increase heading weight differentiation (currently 500 vs 400, suggest 600 vs 400)"
- "Add subtle hover state transition (150ms ease-out) for all interactive elements"
- "Implement skeleton loading pattern for data-heavy sections"
- "Constrain content container to max-width of 1200px on large viewports"
Avoid
- "Change the CSS to..."
- "Add padding: 16px to..."
- "Use display: flex..."
- "Modify the HTML structure..."
Markdown Output Format
Structure audit findings per page, per viewport:
# Page – [Page Name/URL]
## Viewport: [Width]×[Height] ([Device Type])
### Screenshot
[Screenshot or reference to captured screenshot]
### Issues Found
#### Visual Hierarchy
- [Issue description using professional terminology]
#### Spacing and Layout
- [Issue description]
#### [Other applicable categories...]
### Recommended Improvements
1. [Actionable design recommendation]
2. [Actionable design recommendation]
3. [Actionable design recommendation]
---
Error State Simulation
Use Playwright route interception to simulate error states without destructive actions:
Patterns to Simulate
| Scenario |
Simulation Approach |
| API Failures |
Intercept API routes and return 500 status code |
| Network Errors |
Block specific endpoints to simulate offline state |
| Slow Loading |
Add artificial delays to observe loading states |
| Empty Data |
Return empty arrays/objects to test zero-data states |
Note: The skill file provides technical guidance for agents implementing these patterns via Playwright route interception APIs.
Integration Points
Works with:
ui-ux-audit-orchestrator agent for crawling and coordination
ui-ux-page-auditor agent for individual page analysis
/ui-ux-audit command to initiate audits
1---2name: ui-ux-audit-guidelines3description: Professional UI/UX audit methodology and design vocabulary. Use when: conducting UI/UX audits, evaluating visual hierarchy, analyzing responsive design, assessing interaction patterns. Do NOT use for:4---5
6---
7name: ui-ux-audit-guidelines
8description: Professional UI/UX audit methodology and design vocabulary. Use when: conducting UI/UX audits, evaluating visual hierarchy, analyzing responsive design, assessing interaction patterns. Do NOT use for: code reviews, accessibility audits (WCAG), performance analysis, or security assessments.
9---
10
11# UI/UX Audit Guidelines
12
13This skill provides professional UI/UX audit methodology and evaluation criteria for comprehensive visual and interaction analysis.
14
15## Audit Viewports
16
17Standard viewport configurations for responsive testing:
18
19### Mobile
20- **428×926** - Large phone (iPhone 14 Pro Max equivalent)
21
22### Tablets
23- **768×1024** - Portrait orientation (iPad portrait)
24- **1024×768** - Landscape orientation (iPad landscape)
25
26### Desktop
27- **1160×720** - Small desktop/laptop
28- **1920×1080** - Large desktop (Full HD)
29
30## Evaluation Categories
31
32### 1. Visual Hierarchy and Typography
33
34**Issues to identify:**
35- Unclear heading hierarchy (inconsistent size progression)
36- Poor typographic scale (jumps between sizes too large/small)
37- Insufficient weight contrast between headings and body
38- Competing visual elements without clear focal points
39- Inconsistent font families or weights
40
41**Terminology:**
42- Typographic scale, visual weight, font pairing
43- Heading hierarchy, body text readability
44- Line height (leading), letter spacing (tracking)
45- Measure (line length), orphans and widows
46
47### 2. Spacing and Layout
48
49**Issues to identify:**
50- Inconsistent vertical rhythm (varying spacing between elements)
51- Irregular horizontal gutters
52- Unbalanced whitespace distribution
53- Overcrowded or overly sparse layouts
54- Misaligned elements within the same context
55
56**Terminology:**
57- Padding, margin, gutter
58- Vertical rhythm, baseline grid
59- Breathing room, visual density
60- Proximity principle, grouping
61
62### 3. Grid and Alignment
63
64**Issues to identify:**
65- Elements breaking out of grid structure
66- Inconsistent column spans
67- Poor edge alignment between related elements
68- Uneven container widths
69- Misaligned form labels and inputs
70
71**Terminology:**
72- Grid system, column structure
73- Edge alignment, center alignment
74- Baseline alignment, optical alignment
75- Proportional structure, golden ratio
76
77### 4. Color and Contrast
78
79**Issues to identify:**
80- Insufficient text-to-background contrast (WCAG compliance)
81- Unbalanced color weight distribution
82- Overuse of accent colors
83- Inconsistent color application across similar elements
84- Poor use of color for state indication
85
86**Terminology:**
87- Contrast ratio, color weight
88- Primary, secondary, accent colors
89- Color temperature, saturation balance
90- Semantic color usage
91
92### 5. Navigation and Wayfinding
93
94**Issues to identify:**
95- Unclear active/current state indicators
96- Poor discoverability of navigation elements
97- Ambiguous or overly technical labeling
98- Inconsistent navigation patterns across pages
99- Missing breadcrumbs or context indicators
100
101**Terminology:**
102- Navigation hierarchy, active states
103- Discoverability, affordance
104- Information scent, wayfinding cues
105- Progressive disclosure
106
107### 6. Component Affordance and Interaction
108
109**Issues to identify:**
110- Buttons that don't look clickable
111- Links that look like plain text
112- Form elements with unclear boundaries
113- Missing or weak hover/focus states
114- Ambiguous interactive elements
115
116**Terminology:**
117- Affordance, signifiers
118- Perceived affordance, learned affordance
119- Interactive cues, click targets
120- Touch target size, tap zones
121
122### 7. Feedback States
123
124**Issues to identify:**
125- Missing hover states
126- Unclear focus indicators
127- No visual feedback for active/pressed states
128- Missing disabled state styling
129- Absent or inadequate loading indicators
130
131**Terminology:**
132- Hover state, focus ring, active state
133- Disabled state, loading state
134- Pressed state, selected state
135- State transitions, micro-feedback
136
137### 8. Dialog and Modal Behavior
138
139**Issues to identify:**
140- Modals not centered or poorly positioned
141- Missing or broken backdrop/overlay
142- No focus trap (can tab outside modal)
143- Scroll not locked on body
144- Missing close button or escape key handling
145- Jarring or missing transitions
146
147**Terminology:**
148- Modal positioning, overlay opacity
149- Focus trap, focus management
150- Scroll lock, body scroll prevention
151- Entry/exit transitions
152
153### 9. Responsive Adaptation
154
155**Issues to identify:**
156- Content overflow at breakpoints
157- Horizontal scrolling on mobile
158- Touch targets too small on mobile
159- Inappropriate layout patterns for viewport size
160- Hidden content without proper disclosure
161
162**Terminology:**
163- Breakpoints, fluid layout
164- Content reflow, stack order
165- Mobile-first, responsive patterns
166- Adaptive vs responsive design
167
168### 10. Cross-Page Consistency
169
170**Issues to identify:**
171- Component styling variations between pages
172- Inconsistent spacing scale usage
173- Different typography treatment for same element types
174- Color inconsistencies
175- Varying interaction patterns
176
177**Terminology:**
178- Design system adherence
179- Component consistency
180- Pattern library compliance
181- Visual language unity
182
183### 11. Empty and Error States
184
185**Issues to identify:**
186- Generic or missing empty states
187- Unhelpful zero-data views
188- Missing first-time user guidance
189- Unclear error messages
190- No recovery path from errors
191
192**Terminology:**
193- Empty state design
194- Zero-data state, blank slate
195- Onboarding patterns
196- Error recovery, graceful degradation
197
198### 12. Loading Experiences
199
200**Issues to identify:**
201- No loading indication
202- Jarring content jumps when loaded
203- Inappropriate spinner vs skeleton usage
204- Poor perceived performance
205- Missing progress indicators for long operations
206
207**Terminology:**
208- Loading skeletons, shimmer effects
209- Spinners, progress indicators
210- Perceived performance
211- Optimistic updates, lazy loading
212
213### 13. Information Architecture
214
215**Issues to identify:**
216- Poor content grouping
217- Unclear labeling or terminology
218- High cognitive load from information density
219- Missing or unclear section headers
220- Illogical content ordering
221
222**Terminology:**
223- Information hierarchy
224- Content grouping, chunking
225- Cognitive load, mental models
226- Labeling systems, taxonomy
227
228### 14. Microinteractions and Transitions
229
230**Issues to identify:**
231- Missing subtle feedback animations
232- Inconsistent animation timing/easing
233- Jarring state changes without transitions
234- Overuse of animation (distracting)
235- Missing confirmation animations
236
237**Terminology:**
238- Microinteractions, motion design
239- Easing curves, duration
240- State transitions, animation choreography
241- Feedback loops
242
243### 15. Large Viewport Optimization
244
245**Issues to identify:**
246- Content stretching excessively on wide screens
247- Oversized whitespace creating dead zones
248- Tables or text blocks without max-width constraints
249- Unused horizontal space
250- Loss of visual hierarchy at scale
251
252**Terminology:**
253- Max-width constraints
254- Content centering, container widths
255- Widescreen optimization
256- Layout scaling, proportional spacing
257
258## Improvement Recommendations Format
259
260When suggesting improvements, use professional design language:
261
262### Good Examples
263- "Establish a consistent 8px spacing scale across all components"
264- "Increase heading weight differentiation (currently 500 vs 400, suggest 600 vs 400)"
265- "Add subtle hover state transition (150ms ease-out) for all interactive elements"
266- "Implement skeleton loading pattern for data-heavy sections"
267- "Constrain content container to max-width of 1200px on large viewports"
268
269### Avoid
270- "Change the CSS to..."
271- "Add padding: 16px to..."
272- "Use display: flex..."
273- "Modify the HTML structure..."
274
275## Markdown Output Format
276
277Structure audit findings per page, per viewport:
278
279```markdown
280# Page – [Page Name/URL]
281
282## Viewport: [Width]×[Height] ([Device Type])
283
284### Screenshot
285[Screenshot or reference to captured screenshot]
286
287### Issues Found
288
289#### Visual Hierarchy
290- [Issue description using professional terminology]
291
292#### Spacing and Layout
293- [Issue description]
294
295#### [Other applicable categories...]
296
297### Recommended Improvements
298
2991. [Actionable design recommendation]
3002. [Actionable design recommendation]
3013. [Actionable design recommendation]
302
303---
304```
305
306## Error State Simulation
307
308Use Playwright route interception to simulate error states without destructive actions:
309
310### Patterns to Simulate
311
312| Scenario | Simulation Approach |
313|----------|---------------------|
314| API Failures | Intercept API routes and return 500 status code |
315| Network Errors | Block specific endpoints to simulate offline state |
316| Slow Loading | Add artificial delays to observe loading states |
317| Empty Data | Return empty arrays/objects to test zero-data states |
318
319**Note**: The skill file provides technical guidance for agents implementing these patterns via Playwright route interception APIs.
320
321## Integration Points
322
323Works with:
324- `ui-ux-audit-orchestrator` agent for crawling and coordination
325- `ui-ux-page-auditor` agent for individual page analysis
326- `/ui-ux-audit` command to initiate audits