Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Adversarial design critique of the current work — render it, look at it, and argue for rejection.
Install Critique
$ npx skills add plugin87/ux-ui-agent-skills --skill critique -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install plugin87/ux-ui-agent-skills critique --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/plugin87/ux-ui-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/critique .claude/skills/critique && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "critique" agent skill from https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/critique into .claude/skills/critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/critiqueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add plugin87/ux-ui-agent-skills --skill critique -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install plugin87/ux-ui-agent-skills critique --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/plugin87/ux-ui-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/critique .agents/skills/critique && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "critique" agent skill from https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/critique into .agents/skills/critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add plugin87/ux-ui-agent-skills --skill critique -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install plugin87/ux-ui-agent-skills critique --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/plugin87/ux-ui-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/critique .cursor/skills/critique && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "critique" agent skill from https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/critique into .cursor/skills/critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/plugin87/ux-ui-agent-skills.git --path .claude/skills/critique--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add plugin87/ux-ui-agent-skills --skill critique -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install plugin87/ux-ui-agent-skills critique --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/plugin87/ux-ui-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/critique .gemini/skills/critique && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "critique" agent skill from https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/critique into .gemini/skills/critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install plugin87/ux-ui-agent-skills critiqueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add plugin87/ux-ui-agent-skills --skill critique -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/plugin87/ux-ui-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/critique .github/skills/critique && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "critique" agent skill from https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/critique into .github/skills/critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add plugin87/ux-ui-agent-skills --skill critique -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install plugin87/ux-ui-agent-skills critique --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/plugin87/ux-ui-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/critique .opencode/skills/critique && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "critique" agent skill from https://github.com/plugin87/ux-ui-agent-skills/tree/main/.claude/skills/critique into .opencode/skills/critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
critique- GitHub stars
- 1.5k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 532 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- MIT
At a glance
Adversarial design critique of the current work — render it, look at it, and argue for rejection.
- Tasks that involve Design review and critique
- Calls node
What it does
Critique is an agent skill from plugin87/ux-ui-agent-skills. Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Design review and critique. The repository describes itself as: Turn Claude into a senior design architect: DTCG tokens, 52 components, WCAG 2.2 AA-AAA, 138 design systems, any-framework code, and 50 objective gates that fail the build… The licence is MIT.
When your agent uses it
- Tasks that involve Design review and critique
Example prompts
- “/critique”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 14f8d44. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Critique loads about 1.3k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 532 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from plugin87/ux-ui-agent-skills at commit 14f8d44, republished under its MIT licence (© plugin87). 532 words, ~1,275 tokens.
Download SKILL.mdSave it as
.claude/skills/critique/SKILL.md (or your agent's skills folder).- name
- critique
- description
- Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.
- disable-model-invocation
- true
- context
- fork
- background
- false
You are now running in a forked context. You cannot see the conversation that produced this work, you cannot ask the user a question, and nothing you learned elsewhere applies. Everything you need is below or on disk.
Step 0 — is the kit here?
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOn KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point at npx ux-ui-agent-skills init or the
plugin install, and stop. Do not guess the contents of a file you could not open.
Step 1 — take the critic's instructions, in full.
cat ${CLAUDE_SKILL_DIR}/../../../.claude/agents/design-critic.mdThat file is your brief: the stance, the three rules you never break, and the verdict format. Read it and follow it literally. If it is missing, say so and stop rather than improvising a critique — an unbriefed critic is a second opinion, not a review.
Step 2 — resolve the target.
Target: $ARGUMENTS — a file or a directory.
You cannot ask. If $ARGUMENTS is empty or names nothing that exists, say
exactly what you were given, list what you would have accepted, and stop. A
critique of a guessed target is worse than no critique, because it reads like a
verdict on the real work.
Step 3 — refuse to critique blind.
A critique written from source alone is worthless. Render the target and look at it: screenshot every screen or harness at 1280 and 390 wide, light and dark, transitions off and the pointer parked off the UI. Then click every control and write down what actually changed. A control that changes nothing is a finding.
Step 4 — gather the numbers you will cite.
KIT=${CLAUDE_SKILL_DIR}/../../..
node $KIT/scripts/taste_audit.mjs <file> && node $KIT/scripts/taste_audit.mjs <file> --dark
node $KIT/scripts/slop_tells.mjs <file> && node $KIT/scripts/slop_tells.mjs <file> --dark
node $KIT/scripts/verify_overflow.mjs <file|dir>
node $KIT/scripts/verify_responsive.mjs <file|dir> --scale=1.25Report what they actually printed. These are heuristics: they name what you saw, they do not decide whether it is good. A clean run is not a defence: the kit's own seeded-defect fixtures pass every one of these gates, in both themes, and every one of them is work a senior designer would send back.
Show full SKILL.md (210 more words)Show less
Step 5 — write the verdict.
In the format design-critic.md specifies: the verdict, the three reasons a
senior designer would send this back, and the findings table with evidence per
finding. Name the file and the element. "The spacing feels off" is not a finding;
"the card's 12px internal gap is the same as the 12px gap between cards, so the
grouping reads as one block" is.
Do not soften it, and do not pad the "what is good" list to balance the tone.
Step 6 — state the scope, every time.
This is judgement, not measurement. It produces no percentage, and no percentage in this repo covers taste. Say so in the output.
After the critique comes back
For the session that invoked this skill, not for the fork:
Act on it. Fix every Critical and Major finding, re-run /gate, and run this
critique again on what changed. The loop ends when the remaining findings are
Minor or Enhancement — not when you are tired of it.
Scoring the critic itself, rather than the work, is a maintainer task and lives with the harness in the kit's repository - not here. This skill installs into your project, and nothing it tells you to do should name a file your install does not have.
© plugin87, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/critique of plugin87/ux-ui-agent-skills.
Open the folder on GitHubat commit 14f8d44
Compare with similar skills
Critique next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Critique this skillplugin87/ux-ui-agent-skills | 1.5k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 98 repos | ~308 | Automated safety check: Pass | None | |
| Interface Design for Dashboards and Appsholaboss-ai/holaOS | 11k | 3 repos | ~6k | Automated safety check: Pass | MIT | |
| Impeccablemims-harvard/OptimusKG | 146 | 3 repos | ~5.5k | Automated safety check: Pass | Apache-2.0 | |
| Tastemaker UI Designcodeswithroh/tastemaker | 437 | — | ~16k | Automated safety check: Pass | MIT | |
| UI Aesthetics Judgmentkasonye/ui-aesthetics-skill | 384 | — | ~3.2k | Automated safety check: Pass | None |
Similar skills
- Official
Interface Design for Dashboards and Apps
holaboss-ai/holaOS
Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.
Impeccable
mims-harvard/OptimusKG
Create distinctive, production-grade frontend interfaces with high design quality.
Tastemaker UI Design
codeswithroh/tastemaker
Grounds AI-built interfaces in real reference images and a saved personal taste profile, so UI work avoids the generic defaults of typical generated apps.
UI Aesthetics Judgment
kasonye/ui-aesthetics-skill
Sets rules for web UI work that favor hierarchy, spacing and restrained styling, with routes for generating, reviewing and polishing interfaces.
I Frontend Design
boussadjra/vuestrata
Create distinctive, production-grade frontend interfaces with high design quality.
More from plugin87/ux-ui-agent-skills
All 23 skills in this repoData-Dense Dashboard Designer
plugin87/ux-ui-agent-skills
Lays out dense analytics or trading-terminal screens in banded sections with hand-drawn SVG charts, instead of a wall of identical stat cards.
UI Component Spec Designer
plugin87/ux-ui-agent-skills
Writes a complete UI component spec with anatomy, variants, sizes, eight interaction states, design-token mapping and accessibility notes before or alongside code.
Design Project Scaffold
plugin87/ux-ui-agent-skills
Creates a new design-product project from the kit's product-design template, then installs the engine folders and the Playwright dependency that the quality gates need.
Accessibility Audit
plugin87/ux-ui-agent-skills
Audits a UI or design against WCAG 2.2 and ARIA patterns and returns findings with the criterion, severity and a specific fix for each.
Apply Aesthetic
plugin87/ux-ui-agent-skills
Applies a chosen visual direction, an archetype or one of 138 named design systems, by remapping design tokens, then checks contrast before it finishes.
Brand Kit Design Tokens
plugin87/ux-ui-agent-skills
Builds a from-scratch brand design system as three-tier DTCG tokens plus one theme.css with light and dark modes, checked against WCAG contrast rules.
Related
Categories
Questions about Critique
What does Critique do?
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Critique is an agent skill from plugin87/ux-ui-agent-skills. Adversarial design critique of the current work — render it, look at it, and argue for rejection.
When should I use Critique?
Critique fits situations like: tasks that involve Design review and critique.
How do I install Critique in Claude Code?
Run `npx skills add plugin87/ux-ui-agent-skills --skill critique -a claude-code`. Or copy the skill folder (.claude/skills/critique in plugin87/ux-ui-agent-skills) into .claude/skills/critique in your project. Claude Code loads it when a task matches its description.
How do I install Critique in Codex?
Run `npx skills add plugin87/ux-ui-agent-skills --skill critique -a codex`. Or copy the skill folder (.claude/skills/critique in plugin87/ux-ui-agent-skills) into .agents/skills/critique in your project. Codex loads it when a task matches its description.
Can I use Critique in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add plugin87/ux-ui-agent-skills --skill critique -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/critique, .gemini/skills/critique, .github/skills/critique and .opencode/skills/critique in your project.
What does Critique need to run?
Going by SKILL.md and its folder, Critique needs the command-line tools its instructions call (node). Our summary lists: Node.js.
Does Critique access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Critique safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Critique use?
Critique is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Critique use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Critique?
Skills that share tags, products or a category with Critique: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Impeccable (mims-harvard/OptimusKG, 146 stars) and Tastemaker UI Design (codeswithroh/tastemaker, 437 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Critique?
plugin87 (a GitHub user) maintains it in plugin87/ux-ui-agent-skills, which has 1,543 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 7, 2026.
Source: plugin87/ux-ui-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.