- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add plugin87/ux-ui-agent-skills --skill critique -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add plugin87/ux-ui-agent-skills --skill critique -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add plugin87/ux-ui-agent-skills --skill critique -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add plugin87/ux-ui-agent-skills --skill critique -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/plugin87/ux-ui-agent-skills/tree/HEAD/.claude/skills/critique게시자 제공
This skill runs in a forked context. The conversation that produced the work is not visible here, there is no way to ask the user a question, and nothing from elsewhere applies. Everything the review needs is below or on disk.
This skill needs the full UX/UI Agent Skills kit: the gates, the references and
the design-system library. Install it with npx [email protected] init
or as the Claude Code plugin. npx [email protected] add copies the skill folder and
nothing else, and this skill has no guidance-only mode: its whole job is to
hand the work to the kit's design-critic agent, so without the kit there is nothing for it to do.
Step 0: is the kit here? Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSING, say plainly that only the skill folder was installed, name the install command above, and stop. Do not guess the contents of a file you could not open, and do not report a result you did not produce.
Step 1: take the critic's instructions, in full.
cat ${CLAUDE_SKILL_DIR}/../../../.claude/agents/design-critic.md
That 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}/../../..
DS_REQUIRE_BROWSER=1 node $KIT/scripts/taste_audit.mjs <file> && DS_REQUIRE_BROWSER=1 node $KIT/scripts/taste_audit.mjs <file> --dark
DS_REQUIRE_BROWSER=1 node $KIT/scripts/slop_tells.mjs <file> && DS_REQUIRE_BROWSER=1 node $KIT/scripts/slop_tells.mjs <file> --dark
node $KIT/scripts/gate.mjs verify_overflow.mjs <file|dir>
node $KIT/scripts/gate.mjs verify_responsive.mjs <file|dir> --scale=1.25
Report 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.
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.
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.
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.
---name: critiquedescription: Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the…---# .claude/skills/critique/SKILL.mdFAQ
게시자에게서 .claude/skills/critique/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/plugin87/ux-ui-agent-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.