Skip to content
Skillpedia
Interfaces (UI/UX)48k · #4428

ui-review

Analyzes interface code to ensure it follows design, accessibility, and best practices. Improves code quality.

What it does

This tool reviews user interface (UI) code to ensure it follows design rules, is accessible to everyone, and adheres to programming best practices.

When to use it

  • ✓When you want to check if interface code follows the defined visual standard.
  • ✓When you need to ensure the interface works well for people with disabilities.
  • ✓When you want to be sure the code follows good development practices.

Example of what to ask your AI

“Review the UI code in this file: ui-code.js”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/ui-review/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/ui-review/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool compares your code against a list of rules about colors, sizes, accessibility, and other best practices. It points out what deviates from the standard and suggests how to fix it.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill ui-review

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/ui-review/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

UI Design Review

When to Use

Use this skill when you need review UI code for design system compliance, accessibility, and best practices.

When NOT to use

  • For accessibility-only issues → use /ss-a11y
  • For Nielsen UX heuristics → use /ss-audit
  • For a quick automated check → use /ss-lint
  • For non-UI code (data fetching, business rules)

Review the file: $ARGUMENTS

Checklist

1. Design Token Compliance

  • No hardcoded hex colors (use semantic tokens: text-foreground, bg-brand, etc.)
  • No hardcoded px spacing in Tailwind (use p-6 not p-[24px])
  • Shadows use CSS variables (shadow-[var(--shadow-card)])
  • Border radius follows the scale (rounded-md, rounded-lg, rounded-2xl)

2. Component Conventions

  • Uses data-slot attribute
  • Uses cn() for className merging
  • Props typed with React.ComponentProps<>
  • Supports className prop override
  • Named export (not default export for components)
  • No wrapper components that only add a className

3. Accessibility (a11y)

  • Touch targets >= 44x44px for interactive elements
  • focus-visible styles on all interactive elements
  • Proper aria-* attributes where needed
  • Color contrast meets WCAG AA (4.5:1 for text, 3:1 for large text)
  • Animations respect prefers-reduced-motion
  • Images have alt text
  • Form inputs have associated labels

4. Mobile Best Practices

  • No horizontal overflow
  • Touch-friendly spacing between interactive elements
  • Safe area insets handled for notched devices
  • Text sizes >= 12px for readability
  • Scrollable containers have -webkit-overflow-scrolling: touch

5. Performance

  • No unnecessary re-renders (stable references, memoization where needed)
  • Images are lazy-loaded
  • Heavy components are code-split

6. Typography

  • Uses the Pretendard/Inter font stack
  • Font sizes from the 14-step scale (10-48px, see CLAUDE.md)
  • Proper font weights (400, 500, 600, 700)
  • Display text (36-48px): leading-none + tracking-[-0.02em]
  • Heading text (18-24px): leading-snug + tracking-[-0.01em]
  • Body text (14-17px): leading-normal (no custom tracking)
  • Caption uppercase (10-13px): tracking-[0.05em] or tracking-wide
  • No line-height: 1.5 on display/heading text (too loose)

7. Spacing Consistency

  • All spacing values are multiples of 6px (p-1.5, p-3, p-6, etc.)
  • No arbitrary spacing (p-5=20px, gap-3.5=14px are violations)
  • Uses size-* shorthand instead of w-* h-*
  • Uses ms-*/me-* instead of ml-*/mr-* (logical properties)
  • Motion transitions use design tokens (duration-[var(--duration-fast)])

8. Coherence (VISUAL-CRAFT.md §C0 — the "one choice per axis" laws)

The biggest reason a UI reads as "AI-generated" isn't ugly parts — it's mixed parts. Check that each axis below uses ONE value system-wide; flag a mix as a real issue, not a nitpick.

  • One radius personality — sharp (0-4px) OR soft (8-12px) OR pill, applied to every card/button/input/modal. No mixing (e.g. a rounded-none panel with rounded-full buttons).
  • One accent color for interactive emphasis (+ semantic red/green/amber only) — not two+ competing accents.
  • No emoji as UI icons (🚗🧺⭐ as list/nav/status/category markers) — they inject many uncontrolled hues; use one line-icon set in currentColor.
  • Status color = severity, not decoration — a normal/OK/"보통" state is neutral grey (not colored); color marks only the minority of rows that need attention; same value → same color.
  • No decorative hues — favorite stars, category dots, avatars use the accent or grey, not a new color each.
  • One shadow language — same light direction, same scale/tint; not some black + some tinted, some up-lit + some down-lit.
  • One icon family / fill mode / stroke weight across the file.
  • Nested-radius law — an element inside a rounded container uses inner = outer − padding, not the same radius (which bulges).
  • Consistent control heights — buttons, inputs, selects share a height set (e.g. 40px).
  • Errors/states never rely on color alone (icon + text too).

Output Format

Provide:

  1. Score: Pass / Needs Improvement / Fail
  2. Issues: List each violation with file:line reference
  3. Fixes: Concrete code changes for each issue

Example

User request:

…

FAQ

What are 'design tokens'?

They are like predefined building blocks for colors, spacing, and other visual elements, ensuring design consistency.

What is 'accessibility (a11y)'?

It's about ensuring the interface can be used by all people, including those with visual, auditory, or motor impairments.

What does 'hardcoded' mean?

It means a value (like a color or size) was written directly into the code, instead of using a defined rule or variable.

Details

Original description by the author

Review UI code for design system compliance, accessibility, and best practices

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#4428
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills