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

styleseed-design-review

Has your agent analyze interface code and explain why it looks 'AI-generated'. It also suggests how to fix it. Useful for improving website and app design.

What it does

This tool analyzes user interface (UI) code and explains why it looks 'AI-generated.' It then suggests how to fix these issues, providing a score from 0 to 100.

When to use it

  • ✓When an interface looks 'off,' generic, or unfinished, and you can't pinpoint why.
  • ✓To perform a design check before shipping or showing it to users.
  • ✓When you want a UI to look more professional and polished, not robotic.

Example of what to ask your AI

“Review this UI code and tell me how to improve the design.”

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/styleseed-design-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/styleseed-design-review/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool reads your code and checks if visual elements are consistent with each other, following design rules. It points out inconsistencies, like mixed colors or incorrect sizing, and recommends fixes.

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 styleseed-design-review

Or download just the file:

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

Original text by the author, straight from GitHub.

StyleSeed Design Review

Overview

A UI reads as "AI-generated" not because the components are ugly, but because the parts don't agree with each other — mixed corner radii, three accent colors, pure-black text, no hierarchy, missing states, robotic copy. This skill reviews a UI file (or a whole directory) against a concrete design rubric, scores it 0–100, and returns a prioritized fix list. It reviews and recommends; it never edits or deletes without you asking.

Full rule set (74 rules) and components: https://github.com/bitjaru/styleseed

When to use

  • A React / Tailwind / HTML UI "looks off," generic, or unfinished and you can't say why.
  • You want a design score / pre-ship check.
  • The user asks to make UI "look professional / polished / designed, not AI-generated."
  • After generating UI, to verify it before shipping.

How to review

Read the file(s). Score these seven categories (total 100); start each at full marks and subtract for violations you can cite by line. Be specific and evidence-based.

1. Coherence — 20 (the #1 "AI-generated" tell)

One choice per axis, applied everywhere. Deduct for each mixed axis:

  • mixed corner radii — e.g. a sharp card with pill buttons (−6)
  • two or more accent colors used for emphasis (−5)
  • emoji used as UI icons (🚗🧺⭐ as list/nav/status/category markers) — injects many uncontrolled hues; use one line-icon set in currentColor (−6)
  • mixed shadow languages / light directions (−3)
  • mixed icon families, fill modes, or stroke weights (−3)
  • inconsistent control heights (buttons/inputs differ) (−3)

2. Color discipline — 16

  • pure black (#000 / text-black) text — the refined black is ~`#2A2A2A` (−4 each, cap −8)
  • hardcoded hex where a semantic token exists (−2 each, cap −6)
  • a normal / OK / default ("보통") state shown in a status color instead of neutral grey (−4)
  • status color on most/every row (no severity hierarchy — color should mark the minority that needs attention) (−4)
  • decorative hues — gold stars, rainbow category dots, a different color per card — instead of accent/grey (−3)
  • status conveyed by color alone, no icon/text (−4)
  • contrast below WCAG AA (4.5:1 body, 3:1 large/UI) (−6)

3. Hierarchy & typography — 16

  • number and its unit not ~2:1 (48px number / 24px unit) (−4)
  • everything the same size and weight, no clear primary (−5)
  • arbitrary font sizes; no scale (−4)
  • wrong line-height (loose on display, cramped on body) (−3)

4. Layout & spacing — 12

  • content on a bare page background, not in cards (−6)
  • off-grid spacing (7/13/19px instead of an 8px scale) (−3)
  • the gap around a group not larger than the gap inside it (−3)
  • the same section type repeated in a row (−4)

5. States — 12

  • missing empty / loading / error state on a data surface (−5 each, cap −10)
  • empty state with no next action; error that blames instead of helping (−4)

6. UX writing — 12

  • buttons that don't name the action ("Submit" / "OK" instead of "Send $2,400") (−4)
  • error copy that blames or uses system-speak ("Invalid input", "An error occurred") (−4)
  • two terms for one concept (delete vs remove); filler words ("please", "successfully") (−2)

7. Motion & polish — 12

  • ad-hoc fades instead of one consistent, named feel (−3)
  • motion that delays content or blocks an action (−4)
  • no prefers-reduced-motion handling on custom motion (−3)
  • a single hard black shadow instead of a layered, low-opacity, tinted one (−2)

Clamp each category at 0; sum to a total. Bands: 90+ A · 80–89 B · 70–79 C · 60–69 D · <60 F.

Output format

## Design Score: 72 / 100   (src/Dashboard.tsx)   C

Coherence            13/20   sharp cards (l.22) + pill buttons (l.48); 3 accent hues
Color discipline     12/16   #000 headings (l.12, 40)
Hierarchy & type     15/16   number/unit 1:1 on hero (l.18)
Layout & spacing     10/12   two identical KPI rows (l.22-31)
States                7/12   no empty/loading state on the orders list
UX writing            8/12   "Submit" button (l.55); "Invalid input" (l.61)
Motion & polish      10/12   one hard black shadow (l.22)

### Fix first (highest score gain)
1. Unify radius (pick soft 8–12px) + collapse to one accent   → +11 coherence/color
2. Add empty + loading states to the orders list              → +7  states
3. Rename "Submit" → "Send $2,400"; "Invalid input" → "Check the card number" → +6 copy

Re-score after: ~90 / 100.

Rules

…

FAQ

What does 'looks AI-generated' mean?

It means the UI's visual elements don't harmonize well, even if they aren't ugly. Examples include mixed corner radii, too many accent colors, or pure black text.

Will the tool change my code automatically?

No. It only analyzes, gives a score, and suggests fixes. You decide which changes to implement.

How does it know what to fix?

It compares your code against a set of 74 design rules that define how a UI should look cohesive and professional, avoiding common mistakes that make it appear artificial.

Details

Original description by the author

Reviews UI/frontend code and tells you exactly why it \"looks AI-generated\" — then how to fix it.

repo: sickn33/agentic-awesome-skills

Popularity

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

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills