design-review
Skill0 starsChanged 15 days agoMITView on GitHub
Review a UI change for UX, visual quality and use of the design system, from screenshots. Use for each UI change.
166 other projects use a version of this.
Adopted by
Most recently taken up by
- schen22/claude-configtheir own version, first seen Nov 16, 2026
- Taro000/req-to-designtheir own version, first seen Nov 15, 2026
- persiyanov/skillstheir own version, first seen Nov 15, 2026
- SergioRibera/definitive-uxtheir own version, first seen Nov 15, 2026
- adelrodriguez/skillstheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
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.
CoralGameSkillproject-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
CoralGameSkillteam-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
julianoczkowskiSkillbrief-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
lilangMaxSkillasset-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
lilangMaxSkillcreate-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
Other versions166 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 166
- garrytan/gstack★ 142ksame name
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- DenchHQ/DenchClaw★ 1.7ksame name
- DenchHQ/ironclaw★ 1.7ksame name
- me2resh/apexyard★ 542same name
- julianoczkowski/designer-skills★ 536same name
- openclaw/openclaw-enterprise★ 454same name
- AndrewDryga/emisar★ 376same name
- TheDecipherist/claude-code-mastery-project-starter-kit★ 337same name
156 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- architecture-reviewSkill
- bootstrap-projectSkill
- capture-screenshotsSkill
- customizeSkill
- deliver-featureSkill
- docs-upkeepSkill
- fix-bugSkill
- handoffSkill
- implementSkill
- leadSkill
- log-decisionSkill
- refine-requirementsSkill
- release-readinessSkill
- reproduce-in-worktreeSkill
- security-auditSkill
- ship-prSkill
- start-taskSkill
- sync-branchSkill
- threat-modelSkill
- verify-featureSkill
- vet-dependencySkill
- write-adrSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 138 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read: the design source the ticket links (if any), the component kit, the tokens module, and the diff.
- Distinctive: line 17
Tokens and kit: no hard-coded colours, fonts, spacing, curves or durations.
- Distinctive: line 19
Copy: every string is in the catalogue, in the product's voice, written from the reader's side.
- Very specific: line 27
Look at real screenshots (ask for them, or capture them via verify-feature): the default state, each other state, the largest text size, …
“Common” is measured: kept by at least 6 in 10 of the 138 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.
Files
Design review
Playbook files named here: when the project has its own copy at
.playbook/local/<same path>, use that copy instead.
Scope: $ARGUMENTS
Read: the design source the ticket links (if any), the component kit, the tokens module, and the diff. Principles: ${CLAUDE_PLUGIN_ROOT}/principles/04-design-and-ux.md and 05-accessibility-i18n.md.
Check
- Tokens and kit: no hard-coded colours, fonts, spacing, curves or durations. Kit components are used where they exist, and any new pattern is added to the kit with a preview.
- States: loading (a skeleton in the content's shape), error (friendly, with retry), offline (calm, cached data visible), empty (invites action). Nothing flashes "empty" before data arrives.
- Copy: every string is in the catalogue, in the product's voice, written from the reader's side; names and pronouns come from data. Errors and limits are mapped by code. Destructive actions confirm with their consequence.
- Interaction: selected states have a non-colour cue; targets are at least 24 × 24 CSS px (44 recommended); feedback on press; no dead ends (every sheet and screen has a way back).
- Motion: meaningful, uses the token curves through the motion hook, gentle or reduced mode respected, nothing continuous on the main screen.
- Layout: wraps and stacks at 200% zoom; reflows at 320 CSS px; works at tablet and desktop widths; text in fixed art scales with it and its information is in an accessible name.
- Fidelity: matches the design source (spacing, hierarchy, illustration style). Deviations are deliberate and noted.
Evidence
Look at real screenshots (ask for them, or capture them via verify-feature): the default state, each other state, the largest text size, and the narrowest width. Review what's on screen, not just the code.
Output
Findings ranked by customer impact, each with a screenshot reference or a file:line and a suggested fix. List what's good too, so it stays that way.
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
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.

