claude-design-critic — Claude Code skill: audit and install
The claude-design-critic skill reviews a website or UI for generic design and copy, then ranks concrete fixes. Use it after generating a frontend or when a page feels bland.
MIT 184 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill claude-design-critic -a claude-codeWhat claude-design-critic does
The skill can inspect a URL, a local project, or pasted code. It checks composition, palette, typography, spacing, motion, icons, accessibility, and interface copy. The output points to specific sections, explains why they feel template-like, and rewrites the weakest lines.
Its report starts with the highest-impact findings, then separates short fixes from larger changes. The skill can use Read, Write, Bash, Glob, Grep, WebSearch, WebFetch, and Agent; when a project has design tokens, it can audit the UI against them.
Give it the page goal, intended audience, and main action before the review. Without that goal, the critique becomes opinion rather than a targeted audit.
What it helps with
- spot template-like layout patterns
- trace weak hierarchy across a page
- check contrast, focus states, and semantics
- rewrite vague interface copy
- rank design fixes by impact
Example prompts for the agent
- Audit this local frontend and point to the files and sections that make the UI look generated.
- Review this URL for layout, copy, and accessibility issues, then rank the fixes by priority.
- Inspect the pasted component and rewrite its weakest interface lines.
How to install claude-design-critic
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-design-critic -a claude-code2Manually: put the files in place
~/.claude/skills/claude-design-critic/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/claude-design-critic/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-design-critic -a codex2Manually: put the files in place
.agents/skills/claude-design-critic/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-design-critic -a cursor2Manually: put the files in place
.cursor/skills/claude-design-critic/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills claude-design-critic2Manually: put the files in place
.github/skills/claude-design-critic/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-design-critic -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path claude-design-criticManually: put the files in place
.devin/skills/claude-design-critic/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill claude-design-critic -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about claude-design-critic
How do I install claude-design-critic in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill claude-design-critic -a claude-code, then check ~/.claude/skills/claude-design-critic/SKILL.md.
What does claude-design-critic do?
It reviews a website or UI across layout, color, type, spacing, motion, accessibility, assets, and copy. It returns located findings, ranked fixes, and rewrites for weak text.
What can I give the skill to review?
Provide a URL, a local project, or pasted code. Include the page goal, its audience, and the single action it should drive.
Source text
SKILL.md · MIT
---
name: claude-design-critic
description: Audit a website or UI and de-AI it — find the patterns that make it look template-generated (in both design and copy) and return specific, prioritized fixes that push it toward editorial, premium, human-crafted. Reviews layout, color, type, spacing, motion, accessibility, AND the words. Use after building or generating any frontend, or when a site looks "fine but generic" and you can't say why.
tools: Read, Write, Bash, Glob, Grep, WebSearch, WebFetch, Agent
model: inherit
---
# Claude Design Critic
Some sites are technically fine and still scream "an AI made this in one shot." This skill names exactly why and tells you what to change. It reviews the design *and* the copy, because generated-looking text gives a build away as fast as a centered hero and a purple gradient.
Use it as the finishing pass on `claude-landing-composer` output, on any vibe-coded frontend, or on a live site that feels generic. It pairs with the design tokens from `claude-design-system-architect` (audit against them when they exist).
## Step 1 — Take in the target
A URL (WebFetch + screenshot), a local project (read the components/styles), or pasted code. Establish: what is this page for, who's the audience, and what's the one action it wants? A critique without the goal is just opinion.
## Step 2 — Audit across dimensions
Go dimension by dimension and flag concrete instances, not vibes:
**Layout & composition**
- Every section a centered stack? Three-identical-cards reflex? Predictable hero → cards → CTA with no rhythm? Symmetry where asymmetry would feel crafted? Cramped or uniform whitespace?
**Color**
- Purple or default-AI gradients (the dead giveaway). Too many competing accents. Off-brand or arbitrary hexes not mapped to tokens. Contrast failures (check AA).
**Type**
- Default system sans at 2–3 sizes. No real modular scale. Weak hierarchy. Generic pairing. Line length / line-height that reads like a default.
**Spacing & detail**
- Uniform padding everywhere. No optical adjustments. Borders/shadows that are all identical or all heavy.
**Motion**
- The same fade-up on every element. Motion that decorates instead of directs. `prefers-reduced-motion` ignored.
**Iconography & assets**
- Emoji used as UI (replace with Lucide/Heroicons). Generic stock imagery. Placeholder logos left in.
**Copy (review this as hard as the design)**
- AI tells: "elevate", "unlock", "seamless", "empower", "in today's fast-paced world", "we're thrilled to", "the power of", relentless em-dashes, every sentence a tricolon.
- Generic value props ("the best way to X"), hedged language, "Learn More" buttons, "Welcome to {Product}" heroes, filler microcopy.
- Flag the exact lines and rewrite the worst offenders.
**Accessibility & semantics**
- Heading order, alt text, focus states, semantic landmarks, tap-target sizes.
## Step 3 — Report with prioritized, specific fixes
```markdown
# Design Critique — {target}
Generated: {timestamp} · Goal: {…} · Verdict: {SHIP / FIX FIRST / REBUILD SECTION}
## The 30-second read
The 2–3 things making this look generated, in plain language.
## Findings (prioritized: High → Low)
| # | Dimension | What | Where (selector/line/section) | Why it reads as AI | Fix |
## Copy rewrites
"{exact current line}" → "{rewritten line}"
## Quick wins (under 30 min, high impact)
## Bigger moves (worth the time)
## What's already good (keep it)
```
Be specific enough that someone could apply every fix without asking a question. Point to the file/section/line. Where tokens exist, cite the token that should have been used.
## Step 4 — Offer to apply
Offer to implement the high-priority fixes directly (edit the components/copy) and re-audit, or hand a rebuild to `claude-landing-composer`.
## House standard
Premium = intentional layout rhythm, restrained palette, real type scale, generous whitespace, motion with purpose, human copy. Generated = centered everything, rainbow/purple gradients, default sans, uniform padding, fade-up-on-all, and "elevate your workflow." Push every target from the second toward the first. Never purple, never emoji-as-UI.
## Guardrails recap
Critique design AND copy · every finding is specific and located · cite tokens where they exist · prioritize by impact · offer to apply, then re-audit.
© OneWave-AI · MIT · OneWave-AI/claude-skills