- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add plugin87/ux-ui-agent-skills --skill grill-me -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/grill-me게시자 제공
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. Installed that way, this skill runs in guidance-only mode: no gate
runs, so it gives no verdict.
Step 0: is the kit here? Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSING, open your reply with: "Guidance-only mode: the UX/UI Agent Skills kit is not installed here, so no gate ran and nothing below is measured." Then work from this file and general practice, under three rules. Do not guess or cite the contents of a kit file you could not open. State no measured number (no contrast ratio, no N/N, no "passes WCAG"): write "not verified" where one would go. End with a lineSkipped (kit not installed):that names every gate script this file tells you to run, then the install command above.
The gates catch a screen built wrongly. Nothing in this repo catches a screen
built correctly from the wrong brief, and that is where the expensive rework
comes from: four eval runs scored 14/14 on the gates and still came back from
/critique as rework, every finding a decision no gate can see.
This command spends five minutes up front to remove that class of failure.
Target: $ARGUMENTS (the thing about to be built; if that is not clear, that is
itself the first question).
Asking for something the repo already answers is noise, and it teaches the user that answering you is a waste of time. Before writing a single question:
CLAUDE.md, BRIEF.md, or a reference/ folder.${CLAUDE_SKILL_DIR}/../../../tokens/*.json, design-tokens.json, theme.css.
If one exists, the theme question is answered. Do not ask it.Every question you keep after this pass is one the code genuinely cannot answer.
Pick from these. Do not ask all of them.
Purpose and lead
Content reality
Irreversible actions
Theme and platform
Scope and done
/critique
part of the bar or not?An assumption held silently is indistinguishable from a guess. Each one gets a line: what was assumed, the default taken, and what it costs if it is wrong.
Assumption: no dark mode requested -> shipping both anyway (the theme is already
dual, so the cost of including it is zero and the cost of retrofitting is not).
Write BRIEF.md next to the work, in this shape:
# <what is being built>
Goal one sentence, from the user's side
User and task who, and the task they came to finish
Deliverables exact list; N screens means N screens
Lead the one thing the eye lands on first
Content reality empty / one / many, longest string, real vs placeholder
Irreversible which actions, what confirms them, what failure reads like
Theme source of truth, dark mode, brand direction
Platform floor narrowest width, framework, RTL, AA or AAA
Out of scope what this is deliberately not
Assumptions each with its default and its cost if wrong
Done when the gates that must pass, and whether /critique is part of the bar
This file is the thing /critique and a later reviewer argue against. A brief
that lives only in the conversation cannot be checked, and so it will not be.
/grill-me -> build -> /gate -> /critique. This command removes ambiguity.
It does not produce quality, it does not score anything, and it is not a
substitute for rendering the work and looking at it.
Interrogate the brief before a line is built. Ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.
---name: grill-medescription: Interrogate the brief before a line is built. Ask only the questions whose answers change the work, and put…---# .claude/skills/grill-me/SKILL.mdFAQ
게시자에게서 .claude/skills/grill-me/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/plugin87/ux-ui-agent-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.