Skip to content

rsanaie/evaluate-design

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 

Repository files navigation

evaluate-design

A Claude Code skill that performs premium UI/UX design audits with the philosophy of Steve Jobs and Jony Ive.

This skill evaluates and improves the visual design of your application — hierarchy, spacing, typography, color, responsiveness, consistency, and more. It does not write features or touch functionality.

Installation

Add this skill to your Claude Code project:

claude mcp add-skill evaluate-design https://github.com/rsanaie/evaluate-design

Or clone the repo and add it locally:

git clone https://github.com/rsanaie/evaluate-design.git
claude mcp add-skill evaluate-design ./evaluate-design

Usage

Trigger the skill by asking Claude Code to evaluate your design:

  • "evaluate the design"
  • "run a design audit"
  • "review the UI/UX"
  • "make the app feel premium"
  • "critique the visual design"

How It Works

The skill follows a strict 4-step process:

1. Internalize Context

Reads your design system, frontend guidelines, app flow, PRD, tech stack, progress notes, and lessons learned. Then walks through every screen at mobile, tablet, and desktop viewports.

2. Full Audit

Reviews every screen against 15 dimensions:

Dimension Dimension Dimension
Visual Hierarchy Spacing & Rhythm Typography
Color Alignment & Grid Components
Iconography Motion & Transitions Empty States
Loading States Error States Dark Mode / Theming
Density Responsiveness Accessibility

3. Compile the Design Plan

Organizes findings into a phased plan — Critical, Refinement, and Polish — with specific, actionable instructions (exact file, exact component, exact property, exact old value to new value). No ambiguity.

4. Wait for Approval

Nothing is implemented until you review and approve each phase. After each phase is applied, results are presented for review before moving on.

Scope Discipline

This skill has strict boundaries:

Touches: Visual design, layout, spacing, typography, color, interaction design, motion, accessibility, design system token proposals.

Does not touch: Application logic, state management, API calls, data models, feature additions/removals, backend structure.

If a design improvement requires a functionality change, it gets flagged for a build agent to handle separately.

Core Principles

  • Simplicity is the ultimate sophistication
  • Remove until it breaks, then add back the last thing
  • Every pixel references the design system — no rogue values
  • Every screen must feel inevitable at every screen size
  • Propose everything, implement nothing without approval

License

MIT

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors