mcpField
Q
quality-checklist

quality-checklist

github.com/dragoon0xDesign & UI694 installsUpdated 35w ago
Repository

About quality-checklist

Quality Checklist is a design-review skill for evaluating work in the current conversation. It guides a systematic review of hierarchy, typography, color, spacing, craft, and design-system readiness, while treating the checklist as a diagnostic rather than a pass/fail test.

Key features

  1. 01Reviews visual hierarchy
  2. 02Checks typography and color
  3. 03Evaluates spacing and craft
  4. 04Assesses design-system readiness
  5. 05Flags common review pitfalls

Use cases

  1. 01Review a screen design
  2. 02Check accessibility contrast
  3. 03Assess consistency across components

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/dragoon0x/taste-skills --skill quality-checklist

After installing, type/quality-checklistin Claude Code to confirm it loaded.

Details

From the project README

Quality Checklist

A systematic pass through every dimension of design quality.

How to use

  • /quality-checklist Run a quality evaluation on any design in this conversation.

Constraints

Hierarchy
  • Clear primary element on every screen
  • Visual weight matches content priority
  • No unintentional competing elements at the same hierarchy level
  • Eye path follows the intended reading order
Typography
  • Type scale uses a consistent ratio
  • Weight usage is systematic with named purposes
  • Line height varies appropriately (tighter headlines, looser body)
  • No more than 4-6 sizes per screen with clear justification
  • Typeface matches product voice
Color
  • Every color has a clear, non-overlapping role
  • Semantic colors are consistent everywhere
  • Neutrals do 80-90% of the heavy lifting
  • Sufficient contrast for accessibility (WCAG AA minimum)
Space
  • Spacing follows a consistent scale
  • Proximity signals correct relationships
  • Density matches the use case
  • Margins create appropriate breathing room
Craft
  • Border radii consistent across element types
  • Alignment pixel-perfect where intended
  • All states covered: loading, empty, error, success, overflow
  • Transitions purposeful and consistently timed
System
  • Design could scale to 10 more screens without breaking
  • Another designer could extend this without asking questions
  • Components are reusable, not one-offs
  • System breaks are intentional, not accidental
Anti-Patterns
  • Checking only visual polish and ignoring information architecture
  • Treating the checklist as pass/fail instead of diagnostic
  • Running the checklist once and never revisiting

Comments

Markdown supported