grill-me · plugin87 — Claude Code skill for project briefs
The grill-me Claude Code skill asks about a project before implementation and records unanswered decisions as assumptions. Run it before building an interface.
MIT ★ 3,216 updated 2026-11-10
/plugin marketplace add plugin87/ux-ui-agent-skills
/plugin install ux-ui-agent-skills@ux-ui-agent-skillsWhat grill-me does
grill-me examines the project before interface work begins and asks only questions whose answers could change the result. It checks existing briefs, theme files, nearby screens, and components first, so questions already answered by the repository are left out.
Unanswered decisions become written assumptions, each with a chosen default and the cost of getting it wrong. The skill then creates a BRIEF.md covering the goal, users, content, constraints, platform, and completion criteria. It asks at most seven questions in one round.
The gates require the full UX/UI Agent Skills kit. Installing just the skill folder with npx [email protected] add leaves it in guidance-only mode: no gate runs and no verdict is produced. The workflow after the brief is build, /gate, then /critique; grill-me does not score the finished work.
What it helps with
- clarify interface requirements before implementation
- record defaults for decisions the brief leaves open
- capture content states and screen constraints in
BRIEF.md - set completion criteria before building
Example prompts for the agent
- Use
/grill-meto review the brief for a new screen and writeBRIEF.md. - Before implementation, ask only questions that could change the interface.
- Check the theme, content requirements, and completion criteria before building.
How to install grill-me
1Plugin marketplace
/plugin marketplace add plugin87/ux-ui-agent-skills/plugin install ux-ui-agent-skills@ux-ui-agent-skillsThis installs the whole ux-ui-agent-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a claude-code3Manually: put the files in place
~/.claude/skills/grill-me/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/grill-me/
1Skills CLI (Vercel)
npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a codex2Manually: put the files in place
.agents/skills/grill-me/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a cursor2Manually: put the files in place
.cursor/skills/grill-me/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install plugin87/ux-ui-agent-skills .claude/skills/grill-me2Manually: put the files in place
.github/skills/grill-me/SKILL.md1Skills CLI (Vercel)
npx skills add plugin87/ux-ui-agent-skills --skill grill-me -a gemini-cli2Platform CLI
gemini skills install https://github.com/plugin87/ux-ui-agent-skills --path .claude/skills/grill-meManually: put the files in place
.devin/skills/grill-me/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about grill-me
How do I install grill-me in Claude Code?
Add the marketplace with /plugin marketplace add plugin87/ux-ui-agent-skills, then install the plugin with /plugin install ux-ui-agent-skills@ux-ui-agent-skills.
What does grill-me do?
It examines the project, asks questions that could affect the implementation, and records unresolved decisions as assumptions in BRIEF.md.
What does grill-me need to run its gates?
The full UX/UI Agent Skills kit is required. If you install only the skill folder with npx [email protected] add, it runs in guidance-only mode, without gate checks or a verdict.
Source text
SKILL.md · MIT
--- 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_MISSING` > On `KIT_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 line `Skipped (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 a `reference/` 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. ## 2. The bank, grouped by what no gate can see Pick from these. Do not ask all of them. **Purpose and lead** - Who is this for, and what is the one task they came to finish? - What is the first thing their eye should land on? (Four equal cards means the answer is "nothing", and that is a composition bug before it is a design.) - What does success look like for them? What have they done when they leave? **Content reality** - What does this look like with zero items? With one? With four hundred? - What is the longest string a real user will put in here: a 60-character project name, a nine-digit amount, an email with no spaces to break? - Which numbers are real and which are placeholder? Placeholder that ships as real is a lie the user catches immediately. **Irreversible actions** - Which actions here destroy or cannot be undone, and what confirms them? (Destructive wears the danger variant in every place it appears: the trigger and the confirm dialog both. A blue Delete is an automatic fail.) - What happens when the action fails? What does the user read, and what can they do next? **Theme and platform** - New theme or existing? If new: which direction, and does dark mode ship too? - What is the narrowest width this must survive? (The kit's floor is 280px.) - Which framework is the deliverable, and does it need RTL, AA or AAA? **Scope and done** - How many screens or components exactly, and what is explicitly out of scope? - What has to be true before this is done: which gates, and is `/critique` part of the bar or not? ## 3. The rule on asking - **Maximum seven questions, asked in one round.** A drip of one question at a time is worse than a wrong assumption. - **Every question must change the work.** If both answers produce the same build, it is not a question, it is a default. Take it and say so. - **Never ask what you can choose well.** Taste is the job. Ask about intent, content, and constraint; decide the rest. ## 4. Everything unasked becomes a written assumption 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). ``` ## 5. Output: a brief that can be checked later 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. ## 6. Then build, then prove it `/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.
© Thientan Soparat · MIT · plugin87/ux-ui-agent-skills
Similar skills
All skills for Design →grill-me by other authors comes first.