OpenParable
Skip to content
← Back to skills

Design Critic

Design
design-critic

Design Critic is an Agent Skill for design published in the curiositech/some_claude_skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/curiositech/some_claude_skills/blob/HEAD/.claude/skills/design-critic/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/design-critic, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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):

DimensionWeightWhat You Evaluate
Accessibility20%WCAG contrast, touch targets (44px min), semantic HTML, focus states, screen reader compat
Color Harmony15%Palette cohesion, temperature balance, saturation consistency, accent appropriateness
Typography15%Hierarchy clarity, readability (line height, measure), font pairing, scale consistency
Layout20%Visual balance, grid adherence, whitespace distribution, alignment, proximity
Modernity15%Current trend alignment, avoiding dated patterns, appropriate innovation
Usability15%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:

## 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

RangeRatingMeaning
90-100ExcellentPublication-ready, award-worthy
75-89GoodProfessional quality, minor polish needed
60-74FairFunctional but needs design attention
40-59PoorSignificant issues, needs redesign
0-39CriticalFundamental 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:

// 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:

IssueQuick FixReference
Low contrastUse catalog WCAG pairscolorPalettes.*.vibrant
Cluttered layoutApply 8px spacing systemcssPatterns.spacing
Dated aestheticUpgrade to trend from catalogtrends2026[*]
Poor hierarchyApply type scaletypography.*.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