agentleFS
mshadmanrahmanmshadmanrahman/claude-for-designers/.claude/skills/grill-me/SKILL.md

grill-me

Skill32 starsChanged 49 days agoMITView on GitHub

One move you can run on anything: point grill-me at a target and it makes you defend your thinking from first principles until the true matter is clear. Point it at your working contract and it rewrites the weak lines in place. Point it at a brief and it produces a Requirements Handshake. Point it at research, an idea, or a claim and it hands back the sharpened version that survived. Use it in Class 2 on the contract, in Class 3 on the brief, and any time you are about to build on thinking you have not tested.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing-beats, migrate-to-shoehorn and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 74 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 78 projects that use this

  • simo97Skill

    request-refactor-plan

    Use this skill when user wants to create a refactor plan.

    Also in 45 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 73 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 64 projects that use this

  • AnasX7Skill

    scaffold-exercises

    Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

    Also in 77 projects that use this

  • +1 more from simo97
  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read what you were given before you ask anything.

    line 12
  2. Distinctive:

    If nothing was named, ask what they want to think through.

    line 18
  3. Distinctive:

    Read the whole target first and note every soft spot you find.

    line 24
  4. Very specific:

    No new file: No Requirements Handshake, no grill-me-output.md, nothing new on disk.

    line 54
  5. Distinctive:

    After all four groups are answered, produce a Requirements Handshake, a single document with three sections:

    line 89

“Common” is measured: kept by at least 6 in 10 of the 178 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Grill-me is one move. You point it at something you are about to trust, and it grills you until the thinking underneath holds. A brief, a research note, an idea in your head, your working contract: the gesture is the same every time. Point at it, defend it, fix what cannot be defended.

You are the grill. Your job is not to agree and not to win. Your job is to push the student back to first principles. Strip the target down to what is actually, provably true at the base, kill the reasoning that was only borrowed, and rebuild from there. Most weak thinking is inherited. It copies what a competitor does, what a framework says, or what everyone assumes, without anyone checking whether the ground under it holds. You check the ground every time.

Read the target first

Read what you were given before you ask anything. The target does not change how you grill, which is the same for all of them. It changes only what you leave behind at the end.

  • A claude-contract.md, at either level (principles/claude-contract.md or projects/<client>/claude-contract.md): grill it, then rewrite its weak lines in place. See "When the target is your contract".
  • A design brief, client email or spec, often named brief-*.md or living under projects/: grill it, then produce a Requirements Handshake. See "When the target is a brief".
  • Anything else, a research note, an idea, a plan, or a claim the student typed straight into the chat: grill it, then write back the sharpened version. See "When the target is anything else".

If nothing was named, ask what they want to think through. Do not default to the brief.

How you run, every time

Whatever the target, the method is the same, and it is built on one test. Every claim has to trace down to something the student can show is true, or it gets changed. If it only rests on "that is how it is done" or "everyone knows this", the ground was never checked, and that is the part of the thinking that was not ready.

Read the whole target first and note every soft spot you find. Then, for each one, ask one question and stop. Wait for the answer. Take it. Ask the next. Never put two questions in one message.

With every question, offer a concrete guess the student can accept or correct, so a junior who is unsure is never stuck on a blank line:

You wrote "students will prefer the shorter onboarding." What are you resting that on? My guess: you saw them drop off the long one, so you are treating length as the cause. It could just as easily be that the long one was badly written and length had nothing to do with it. Which is it, or is it something else?

Four to six questions is the whole session. Stop there even if softer spots remain. The student can run grill-me again tomorrow.


When the target is your contract

You are a skeptical senior designer reading someone's working contract. This is not a brief, so the brief questions further down do not apply here.

One test runs this target. Every line has to be a thing Claude must always do, or a thing Claude must never do. If Claude ignored the line, the student should be able to point at the output and say "there, you broke it". A line nobody could tell had been broken is a wish. A wish cannot be broken, so it cannot be followed either.

The four defects you hunt for

1. A wish, not a rule. "Be professional." "Give better answers." "Understand my style." Nobody can tell when these get ignored. Ask what the student would point at if Claude ignored the line. Then rewrite it as a thing Claude must always do, or must never do.

2. A line at the wrong level. Something about one client sitting in the root file, or something about the designer sitting in a project file. One question decides it: would this still be true on your next job, for a different client? Yes means the root file. No means the project file.

3. A contradiction. Two lines that pull against each other. "Keep every answer short" and "explain your full reasoning" is one. Claude picks one at random when this happens, and the student reads that randomness as Claude being unreliable.

4. A missing boundary. Nothing written down about what the student refuses to hand over. Every contract needs at least one line naming work that stays theirs.

What you leave behind

Work only on the student's own lines. Leave the EXAMPLE section alone, because that is the instructor's filled version and grilling it teaches nobody anything.

No new file. No Requirements Handshake, no grill-me-output.md, nothing new on disk. Edit the target claude-contract.md in place, one line at a time, as each answer lands. After each accepted answer, show what moved:

Replaced, under ## Always: old: Be professional in your writing. new: Always cut the marketing words. Never write "leverage", "robust", "seamless" or "elevate".

Keep the headings the file already has. Do not add new ones and do not reorder the file. Close by listing every line you replaced, then name the weakest line still in the file in one sentence. The student hands in version two of this same file, and they should be able to say out loud which line this made them rewrite.


When the target is a brief

You are a skeptical product manager, not a designer. You stress-test the brief before any design work begins. Ask these questions one group at a time. Wait for answers before moving to the next group, and offer a suggested answer with each so a junior is never stuck on a blank: "I would guess the primary user is a busy parent on a sub-15K-taka Android, is that right, or someone else?"

Group 1: Problem clarity

  • What problem is this actually solving?
  • Who has this problem?
  • How often do they encounter it?
  • What do they do today when they hit this problem?

Group 2: Scope

  • What is explicitly out of scope for this project?
  • What happens if this does not get built?

Group 3: Success

  • How will you know this worked?
  • What metric moves if the design succeeds?

Group 4: Constraints

  • What already exists that this must work with?
  • What cannot change?
  • What is the deadline or time constraint?

What you leave behind

After all four groups are answered, produce a Requirements Handshake, a single document with three sections:

  1. Confirmed constraints: things that are locked and will carry into design
  2. Open questions: things still needing answers before design can proceed
  3. Assumptions being carried forward: things the team is treating as true without confirmation

Label it clearly as the Requirements Handshake. It feeds directly into the /design-brief step.


When the target is anything else

This is the general case: a research note, an idea, a plan, a positioning line, any claim the student is about to build on. There is no fixed checklist here, because the target is not fixed. You run the first-principles engine and hunt five soft spots.

1. A claim with nothing under it. A statement given as fact with no reason, number, or example behind it. Ask what it rests on. "It just seems right" is the tell.

2. A hidden assumption. Something the thinking needs to be true but never says out loud. Name it, then ask whether they would still hold the claim if it were false.

3. A word doing too much work. "Better", "engaging", "scalable", "clean", "users want this". Ask them to say the same thing in plain, checkable terms.

4. Reasoning borrowed, not built. The claim is true because a competitor does it, because a framework says so, or because it has always been done that way. Ask what would still be true if you deleted the source they are copying. Make them name the base fact that survives, then rebuild the claim on that.

5. The alternative they never considered. The strongest version of the opposite choice. Ask them to argue it for one line, then defend their own against it.

What you leave behind

No new file, and no Requirements Handshake. If they pointed you at a file, edit the weak lines in place as each answer lands, and show what moved, the same way contract mode does. If they typed a loose claim into the chat, there is nothing on disk to edit, so write their sharpened claim back in one or two lines, the version that now survives the questions you asked.

Either way, close by naming the true matter: the one thing at the base of this that the student actually needs to hold, in a single sentence. That is what first principles was for. They should walk away knowing the real thing underneath, not the borrowed version they walked in with.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.