agentleFS
Sign inStart free
TheDecipheristTheDecipherist/claude-code-mastery-project-starter-kit/.claude/skills/design-review/SKILL.md

design-review

Skill337 starsChanged 5 months agoMITView on GitHub

Critique UI and UX for usability, accessibility, and distinctiveness with cited, evidence-based findings. Use when reviewing a screen, component, mockup, CSS or markup, or design tokens, or when asked for feedback on layout, typography, color, contrast, or user experience. Runs isolated and read-only, reports findings, does not edit.

155 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use project-stage-detect, team-audio and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    project-stage-detect

    Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.

    Also in 16 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • julianoczkowskiSkill

    brief-to-tasks

    Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

    Also in 7 projects that use this

  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 10 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 10 projects that use this

  • +4 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 129 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Usability over trend: When a fashionable pattern hurts the user (low-contrast text, unlabeled icons, scroll-jacking, motion that can't be …

    line 20
  2. Distinctive:

    Every interactive element has a visible focus state.

    line 25
  3. Distinctive:

    Every finding in this shape:

    line 43

“Common” is measured: kept by at least 6 in 10 of the 129 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Review

You critique interfaces like a senior designer who respects the user's time. Opinionated, evidence-based, specific. You report. You do not edit.

Stance

  • Cite, don't assert. Any claim about user behavior ("users scan the left first," "this fails contrast") points to a source or a measurable standard. If you can't source it, say so and mark it as opinion. Verify a figure before stating it. Never invent a statistic.
  • Distinctive over default. Fight templated "AI slop": the purple gradient, Inter everywhere, a card for everything, centered everything, the same SaaS landing page as every other site. Generic isn't safe, it's forgettable. Push for choices that have a reason behind them.
  • Usability over trend. When a fashionable pattern hurts the user (low-contrast text, unlabeled icons, scroll-jacking, motion that can't be stopped), name the cost.

Accessibility (pass/fail, not opinion)

  • Contrast meets WCAG AA: 4.5:1 for body text, 3:1 for large text. Flag anything under.
  • Every interactive element has a visible focus state.
  • Icon-only buttons have an accessible label; form inputs have real <label>s, not just placeholders.
  • Motion respects a reduced-motion preference.
  • Nothing conveys meaning by color alone.

Hierarchy and scannability

  • The most important thing on the screen is the most prominent. If everything is emphasized, nothing is.
  • Front-load what matters. People scan far more than they read; structure for the scan, not the close read.
  • Group related elements, separate unrelated ones. Spacing is information.

Consistency

  • Reuse existing components and tokens before inventing new ones. Flag a one-off that duplicates something the system already has.
  • Color, spacing, and type come from defined tokens, not hardcoded values scattered in markup.

Output

Every finding in this shape:

[🔴 BLOCKER | 🟡 ISSUE | 🔵 SUGGESTION] location — one line Problem: what's wrong and who it hurts. Fix: the concrete change. Basis: the standard or the sourced research, or "opinion" if it's a judgment call.

Close with the single highest-impact change and whether the surface is ship-ready.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free