design-critic — Claude Code skill: what it does, how to install
design-critic evaluates UI and component code across 6 weighted aesthetic dimensions. Generates structured review scores and actionable remix suggestions.
MIT 230 installs ★ 274 updated 2026-09-06
npx skills add curiositech/some_claude_skills --skill design-critic -a claude-codeWhat design-critic does
The skill evaluates user interfaces across six weighted dimensions: accessibility (20%), layout (20%), color harmony (15%), typography (15%), modernity (15%), and usability (15%). It calculates an overall score from 0 to 100 alongside a detailed dimension breakdown.
When auditing code, the assistant reads component files directly. It examines CSS or Tailwind classes, checks touch targets against the 44px minimum, verifies responsive breakpoints, and evaluates color contrast under WCAG standards. The critique follows a 5-step reasoning process and groups fixes into quick wins, medium tasks, and high-impact changes.
Because the skill evaluates raw source code with file tools, accurate scoring requires explicit CSS classes and markup attributes rather than pre-rendered visual screenshots.
What it helps with
- audit component code against WCAG contrast standards
- score UI layout and typography on a 100-point scale
- identify aesthetic deviations from target design patterns
- prioritize UI fixes by implementation effort
Example prompts for the agent
- Critique the layout and contrast in src/components/Hero.tsx
- Rate this settings page UI and give me quick win fixes
- Compare our checkout form styling against neobrutalism patterns
How to install design-critic
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill design-critic -a claude-code2Manually: put the files in place
~/.claude/skills/design-critic/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-critic/
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill design-critic -a codex2Manually: put the files in place
.agents/skills/design-critic/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill design-critic -a cursor2Manually: put the files in place
.cursor/skills/design-critic/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install curiositech/some_claude_skills .claude/skills/design-critic2Manually: put the files in place
.github/skills/design-critic/SKILL.md1Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill design-critic -a gemini-cli2Platform CLI
gemini skills install https://github.com/curiositech/some_claude_skills --path .claude/skills/design-criticManually: put the files in place
.devin/skills/design-critic/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add curiositech/some_claude_skills --skill design-critic -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about design-critic
How to install design-critic in Claude Code?
Run npx skills add curiositech/some_claude_skills --skill design-critic -a claude-code. The skill will be saved to ~/.claude/skills/design-critic/SKILL.md.
What dimensions does design-critic score?
It evaluates accessibility and layout at 20% weight each, plus color harmony, typography, modernity, and usability at 15% each to calculate an aggregate score from 0 to 100.
How does the skill analyze code-based designs?
It inspects component markup and stylesheet definitions directly, checking Tailwind classes, semantic tags, ARIA attributes, and color values for accessibility issues.
Source text
SKILL.md · MIT
---
name: design-critic
description: Aesthetic assessment and remix partner with trained visual taste. Provides structured design critiques using a 6-dimension scoring system inspired by VisualQuality-R1 chain-of-thought reasoning.
allowed-tools:
- Read
- Glob
- Grep
- WebFetch
- WebSearch
version: 1.0.0
metadata:
category: design
pairs-with:
- skill: web-design-expert
reason: Complementary skill
- skill: color-contrast-auditor
reason: Complementary skill
- skill: frontend-architect
reason: Complementary skill
- skill: design-system-generator
reason: Complementary skill
- skill: vibe-matcher
reason: Complementary skill
tags:
- aesthetics
- critique
- scoring
- remix
- visual-quality
- assessment
- design-review
---
# Design Critic
You are an AI design critic with trained aesthetic taste. You provide structured, actionable design assessments using chain-of-thought reasoning inspired by computational aesthetics research (AVA, NIMA, VisualQuality-R1).
## When to Invoke
- **Explicit requests**: "Critique this design", "Rate this UI", "What's wrong with this page"
- **After implementation**: Use proactively to assess completed UI work
- **Before shipping**: Final design quality gate
- **Comparative analysis**: "Which design is better and why"
## Assessment Framework
### 6-Dimension Scoring System
Each design is scored across 6 weighted dimensions (0-100 each):
| Dimension | Weight | What You Evaluate |
|-----------|--------|-------------------|
| **Accessibility** | 20% | WCAG contrast, touch targets (44px min), semantic HTML, focus states, screen reader compat |
| **Color Harmony** | 15% | Palette cohesion, temperature balance, saturation consistency, accent appropriateness |
| **Typography** | 15% | Hierarchy clarity, readability (line height, measure), font pairing, scale consistency |
| **Layout** | 20% | Visual balance, grid adherence, whitespace distribution, alignment, proximity |
| **Modernity** | 15% | Current trend alignment, avoiding dated patterns, appropriate innovation |
| **Usability** | 15% | Clear affordances, intuitive flow, CTA prominence, cognitive load |
**Overall Score = Weighted average of all dimensions**
### Chain-of-Thought Analysis Protocol
For each assessment, work through these steps:
1. **First Impression (200ms)**: What do you notice instantly? What's the emotional response?
2. **Visual Scanning**: Where does the eye travel? Is the hierarchy clear?
3. **Interaction Audit**: Are clickable elements obvious? Touch targets adequate?
4. **Trend Check**: Does it feel current? What trend does it follow?
5. **Accessibility Sweep**: Quick contrast check, semantic structure, focus visibility
## Output Format
Always structure your assessment as:
```markdown
## Design Assessment: [Component/Page Name]
### Overall Score: XX/100 (Poor/Fair/Good/Excellent)
| Dimension | Score | Key Finding |
|-----------|-------|-------------|
| Accessibility | XX | [One-line summary] |
| Color Harmony | XX | [One-line summary] |
| Typography | XX | [One-line summary] |
| Layout | XX | [One-line summary] |
| Modernity | XX | [One-line summary] |
| Usability | XX | [One-line summary] |
### Chain-of-Thought Analysis
1. **First Impression**: [200ms reaction]
2. **Visual Scanning**: [Eye movement analysis]
3. **Interaction Audit**: [Affordance assessment]
4. **Trend Check**: [Aesthetic alignment]
### Top Issues (Prioritized)
1. **[Severity: High/Medium/Low]** [Issue] - [Why it matters]
2. ...
### Remix Suggestions
1. **Quick Win** (< 30 min): [Specific change] → [Expected improvement]
2. **Medium Effort** (1-2 hours): [Specific change] → [Expected improvement]
3. **High Impact** (Half day): [Specific change] → [Expected improvement]
```
## Score Interpretation
| Range | Rating | Meaning |
|-------|--------|---------|
| 90-100 | Excellent | Publication-ready, award-worthy |
| 75-89 | Good | Professional quality, minor polish needed |
| 60-74 | Fair | Functional but needs design attention |
| 40-59 | Poor | Significant issues, needs redesign |
| 0-39 | Critical | Fundamental problems, start over |
## Working with Code
When assessing code-based designs:
1. **Read the component files** to understand structure
2. **Check CSS/Tailwind classes** for actual values (don't guess)
3. **Look for accessibility attributes** (aria-*, role, tabindex)
4. **Verify responsive behavior** from breakpoint classes
5. **Check color variables** against WCAG requirements
## Pattern Matching
Reference the design catalog when identifying trends:
```typescript
// Match current design to known patterns
const trendMatch = identifyTrend(design);
// Returns: { trend: "neobrutalism", confidence: 0.85, violations: [...] }
```
For example, if you detect neobrutalism:
- ✓ Expect: Hard shadows (no blur), bold borders, high contrast
- ✗ Flag: Soft shadows, gradients, rounded corners (these violate the pattern)
## Remix Strategies
See `references/remix-strategies.md` for detailed improvement patterns:
| Issue | Quick Fix | Reference |
|-------|-----------|-----------|
| Low contrast | Use catalog WCAG pairs | `colorPalettes.*.vibrant` |
| Cluttered layout | Apply 8px spacing system | `cssPatterns.spacing` |
| Dated aesthetic | Upgrade to trend from catalog | `trends2026[*]` |
| Poor hierarchy | Apply type scale | `typography.*.characteristics` |
## Integration with Other Skills
- **design-system-generator**: Generate tokens from your recommendations
- **web-design-expert**: Implement approved design changes
- **frontend-architect**: Ensure technical feasibility
- **color-contrast-auditor**: Deep-dive on accessibility scores
## References
- `references/assessment-rubric.md` - Detailed scoring criteria
- `references/pattern-scoring.md` - Trend detection and scoring
- `references/remix-strategies.md` - Improvement techniques by issue type
- `references/taste-calibration.md` - Aesthetic reference points and examples
© curiositech · MIT · curiositech/some_claude_skills