- name
- grill-me
- description
- 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. # A command the user runs. Converted from .claude/commands/ so it has a # CLAUDE_SKILL_DIR of its own and its paths resolve on every install route. # disable-model-invocation keeps the behaviour a command had: the user # starts it, the model never does, and its description stays out of the # listing budget the model's skill choice is drawn from.
- disable-model-invocation
- true
Requirements
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).
1. Read before you ask
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:
- Look for an existing brief,
CLAUDE.md,BRIEF.md, or areference/folder. - Look for an existing theme:
${CLAUDE_SKILL_DIR}/../../../tokens/*.json,design-tokens.json,theme.css. If one exists, the theme question is answered. Do not ask it. - Look at the neighbouring screens and components. Framework, conventions, and the component inventory are usually visible, not unknown.
Every question you keep after this pass is one the code genuinely cannot answer.