Overview
Structured framework for reviewing UI designs. Evaluates visual hierarchy, consistency, accessibility, spacing, typography, color usage, and provides actionable improvement recommendations.
Capabilities
- Analyze visual hierarchy and information architecture
- Check consistency across components and pages
- Evaluate accessibility (contrast, focus states, semantic HTML)
- Review responsive behavior across breakpoints
- Provide specific, actionable improvement recommendations
When to Use
Trigger phrases:
"ui critique"
"Structured UI review — visual hierarchy, consistency, accessibility, and actiona"
Before launching a new UI or redesign
Onboarding a new team member to design standards
User complaints about usability or confusion
Pre-launch design review checklist
When NOT to Use
- Task is about content strategy, not creation (use strategy skills)
- Task is about content distribution (use distribution skills)
- You need to analyze content performance (use analytics skills)
- Task is about content moderation (use moderation tools)
- You don't have content guidelines
- Task requires domain expertise (consult experts)
Pseudo Code
The ui-critique workflow follows a standard pipeline pattern.
Core flow:
# ui-critique primary flow
input = prepare(raw_data)
result = process(input, config={accessibility, actionable, consistency, critique, feedback})
validate(result)
deliver(result)
Error handling:
on error:
log(error_details)
retry_with_backoff(max=3)
if still_failing: alert_and_escalate()
Core Workflow
# ui-critique primary flow
input = prepare(raw_data)
result = process(input, config={accessibility, actionable, consistency, critique, feedback})
validate(result)
deliver(result)
Error Handling
on error:
log(error_details)
retry_with_backoff(max=3)
if still_failing: alert_and_escalate()
Critique Framework
def critique_ui(screenshot, url):
checks = {
"visual_hierarchy": check_hierarchy(screenshot), # Can user find CTA in 3s?
"consistency": check_spacing_and_colors(screenshot), # Same patterns everywhere?
"contrast": check_color_contrast(screenshot), # WCAG AA compliant?
"responsive": check_mobile_view(url), # Works on 320px?
"loading": check_performance(url), # LCP < 2.5s?
"accessibility": check_aria_and_semantics(url) # Screen reader friendly?
}
return generate_report(checks)
Common Patterns
- 3-second test: Can user identify the primary action in 3 seconds?
- Squint test: Blur the UI — does the hierarchy still work?
- Contrast check: All text meets WCAG AA (4.5:1 for normal text)
- Spacing audit: Consistent spacing between similar elements
How to Use
- Define content goal (traffic, engagement, conversion, brand awareness)
- Research target audience pain points and search intent
- Generate content using appropriate AI tools
- Edit and humanize output for authenticity
- Optimize for target platform (SEO, hashtags, format)
- Schedule and distribute across channels
- Measure performance and iterate
Red Flags
- AI-generated content sounds robotic: Always run through humanizer before publishing
- Engagement dropping week-over-week: Content fatigue or algorithm change — vary formats
- Duplicate content across platforms: Adapt content per platform, don't just cross-post
- No content calendar: Sporadic posting kills audience retention
- Ignoring analytics: Content without measurement is just publishing, not marketing
Verification
Process
- Analyze the task requirements
- Apply domain expertise
- Verify output quality
Anti-Rationalization Table
| Rationalization |
Reality |
| "Good enough content works" |
Quality content drives engagement. Mediocre content gets ignored. |
| "I will optimize later" |
SEO and distribution need optimization from the start. |
| "Templates are good enough" |
Templates are a starting point. Custom content outperforms generic. |
1---2name: ui-critique3description: Structured framework for reviewing UI designs, evaluating visual hierarchy, consistency, accessibility, spacing, typography, and color usage, and providing actionable improvement recommendations.4license: Apache-2.05---678910## Overview1112Structured framework for reviewing UI designs. Evaluates visual hierarchy, consistency, accessibility, spacing, typography, color usage, and provides actionable improvement recommendations.1314## Capabilities1516- Analyze visual hierarchy and information architecture17- Check consistency across components and pages18- Evaluate accessibility (contrast, focus states, semantic HTML)19- Review responsive behavior across breakpoints20- Provide specific, actionable improvement recommendations2122## When to Use23**Trigger phrases:**24- "ui critique"25- "Structured UI review — visual hierarchy, consistency, accessibility, and actiona"262728- Before launching a new UI or redesign29- Onboarding a new team member to design standards30- User complaints about usability or confusion31- Pre-launch design review checklist3233## When NOT to Use3435- Task is about content strategy, not creation (use strategy skills)36- Task is about content distribution (use distribution skills)37- You need to analyze content performance (use analytics skills)38- Task is about content moderation (use moderation tools)39- You don't have content guidelines40- Task requires domain expertise (consult experts)414243## Pseudo Code4445The ui-critique workflow follows a standard pipeline pattern.4647Core flow:48```49# ui-critique primary flow50input = prepare(raw_data)51result = process(input, config={accessibility, actionable, consistency, critique, feedback})52validate(result)53deliver(result)54```5556Error handling:57```58on error:59 log(error_details)60 retry_with_backoff(max=3)61 if still_failing: alert_and_escalate()62```636465### Core Workflow66```67# ui-critique primary flow68input = prepare(raw_data)69result = process(input, config={accessibility, actionable, consistency, critique, feedback})70validate(result)71deliver(result)72```7374### Error Handling75```76on error:77 log(error_details)78 retry_with_backoff(max=3)79 if still_failing: alert_and_escalate()80```818283### Critique Framework84```python85def critique_ui(screenshot, url):86 checks = {87 "visual_hierarchy": check_hierarchy(screenshot), # Can user find CTA in 3s?88 "consistency": check_spacing_and_colors(screenshot), # Same patterns everywhere?89 "contrast": check_color_contrast(screenshot), # WCAG AA compliant?90 "responsive": check_mobile_view(url), # Works on 320px?91 "loading": check_performance(url), # LCP < 2.5s?92 "accessibility": check_aria_and_semantics(url) # Screen reader friendly?93 }94 return generate_report(checks)95```9697## Common Patterns9899- **3-second test**: Can user identify the primary action in 3 seconds?100- **Squint test**: Blur the UI — does the hierarchy still work?101- **Contrast check**: All text meets WCAG AA (4.5:1 for normal text)102- **Spacing audit**: Consistent spacing between similar elements103104## How to Use1051061. Define content goal (traffic, engagement, conversion, brand awareness)1072. Research target audience pain points and search intent1083. Generate content using appropriate AI tools1094. Edit and humanize output for authenticity1105. Optimize for target platform (SEO, hashtags, format)1116. Schedule and distribute across channels1127. Measure performance and iterate113114## Red Flags115116- **AI-generated content sounds robotic**: Always run through humanizer before publishing117- **Engagement dropping week-over-week**: Content fatigue or algorithm change — vary formats118- **Duplicate content across platforms**: Adapt content per platform, don't just cross-post119- **No content calendar**: Sporadic posting kills audience retention120- **Ignoring analytics**: Content without measurement is just publishing, not marketing121122## Verification123124- [ ] Skill output matches expected behavior125126## Process1271281. Analyze the task requirements1292. Apply domain expertise1303. Verify output quality131132## Anti-Rationalization Table133134| Rationalization | Reality |135|---|---|136| "Good enough content works" | Quality content drives engagement. Mediocre content gets ignored. |137| "I will optimize later" | SEO and distribution need optimization from the start. |138| "Templates are good enough" | Templates are a starting point. Custom content outperforms generic. |