# Grill Me

Interrogate the brief before a line is built.

- Repository: https://github.com/plugin87/ux-ui-agent-skills (3071 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add plugin87/ux-ui-agent-skills --skill grill-me -g -a claude-code -y`
Codex: `npx skills add plugin87/ux-ui-agent-skills --skill grill-me -g -a codex -y`
Cursor: `npx skills add plugin87/ux-ui-agent-skills --skill grill-me -g -a cursor -y`
Gemini CLI: `npx skills add plugin87/ux-ui-agent-skills --skill grill-me -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add plugin87/ux-ui-agent-skills`

## 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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **Step 0: is the kit here?** This skill reads files from the kit. Check once:
> `ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING`
> On `KIT_MISSING` only the skill folders were installed, which is what
> `npx skills add` does. Say so plainly, point the user 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.


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?

The rest: https://github.com/plugin87/ux-ui-agent-skills/blob/HEAD/.claude/skills/grill-me/SKILL.md