agentleFS
mshadmanrahmanmshadmanrahman/claude-for-designers/.claude/skills/design-review/SKILL.md

design-review

Skill32 starsChanged 49 days agoMITView on GitHub

Critique a design on layout, accessibility, responsiveness, dark mode and edge cases, with Pass, Needs work or Fail verdicts. Use on a built screen.

167 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use team-level, team-audio and 9 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

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 13 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 14 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 11 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 11 projects that use this

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

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 1

    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:

    Ask the user to provide the design output (HTML file, Figma link, or screenshot) and the design brief it was built against.

    line 8

“Common” is measured: kept by at least 6 in 10 of the 139 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

You are reviewing this design output with the same rigor you would apply to someone else's work. No vague feedback. Every finding must include a specific, actionable fix.

Ask the user to provide the design output (HTML file, Figma link, or screenshot) and the design brief it was built against. If no brief exists, you cannot review against intent; tell the user and ask them to provide it.

Review across five dimensions. Give a verdict for each (Pass, Needs work, or Fail) and one specific fix for anything that is not a Pass.

1. Layout Does the visual hierarchy match what the brief named as primary? Is the primary action immediately obvious without scanning? Is there sufficient whitespace to separate distinct content areas? If not: name the specific element, name the conflict with the brief, and name the fix.

2. Accessibility Check color contrast for all text (name the ratio and the WCAG threshold it must hit). Confirm focus states exist on all interactive elements. Confirm body text is at minimum 16px. Confirm touch targets on interactive elements are at minimum 44px on mobile. Do not say "improve contrast." Say: "The label text on the card uses #6B7280 on #FFFFFF, which is 4.6:1. It passes AA for normal text. The subtext uses #9CA3AF on #FFFFFF at 2.8:1, which fails AA. Change to #6B7280 or darker."

3. Responsiveness How does this break at 375px? At 768px? Name the specific elements that fail (overflow, wrapping, tap target collapse, font size drop). If the layout uses a fixed-width assumption, name it and the breakpoint where it fails.

4. Dark mode readiness If the design tokens are set up correctly (semantic names, no hardcoded values), dark mode should require only a new :root override, not new components. Verify this is the case. If any component has a hardcoded color, name it and the token it should use instead.

5. Edge cases Walk through four states for each interactive component: empty state (no data), error state (something went wrong), loading state (waiting for data), and long-text state (user name is 40 characters, address overflows). Name any state that breaks the layout and the specific fix.

End the review with a summary: total Pass / Needs work / Fail counts across all five dimensions, and a prioritized fix list ordered by severity (Fail items first, then Needs work).

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.