grill-me

Solid

Two modes, picked from the file you point it at. Contract mode grills a claude-contract.md line by line until every line is a thing Claude must always do or must never do, editing that file in place and creating nothing new. Brief mode interrogates a design brief until it has no soft spots left, then produces a Requirements Handshake of confirmed constraints, open questions and carried assumptions. Use in Class 2 on the working contract, and before any design work begins on a brief.

AI & Automation 26 stars 7 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
48
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

Read the file you were pointed at before you ask anything. That file decides which mode you run. - The target is a `claude-contract.md`, at either level (`principles/claude-contract.md` or `projects/<client>/claude-contract.md`): run **contract mode**. - The target is anything else, a brief, a client email, a spec: run **brief mode**. If no file was named, ask which file to run on. Do not send the student to the project brief instead. Both modes are real, and Class 2 runs this skill on the contract. --- # Contract mode You are a skeptical senior designer reading someone's working contract. This is not a brief, so none of the brief questions further down apply here. Do not ask them. One test runs this whole mode. **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 a thing Claude 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. The...

Details

Author
mshadmanrahman
Repository
mshadmanrahman/claude-for-designers
Created
2 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

grill-me-code-style-coach

Coach the user WHILE building or fixing code in a repo that has a code-style.rules.json — at each real style/structure decision, explain the concept concisely (KISS) in terms they already know, show two concrete variants, make them confirm the direction before writing, then teach the mechanism and link the exemplar it mirrors. High-friction on judgment calls; silent on anything Biome already enforces. Grounds "where the business logic goes" in PROJECT.md / CONTEXT.md. Use when writing a feature/fix and the user wants to LEARN their own architecture as we go, not just delegate — or says "coach me", "teach me as we build", "grill me while we code". For reviewing a finished diff instead, use grill-me-code-style-review; to CREATE the ruleset, grill-me-code-style.

0 Updated 2 days ago
YosefHayim
Data & Documents Listed

contract

Negotiate the "what done means" contract on disk before any autonomous code cycle starts. Produces contract.json with weighted criteria, user_flow (CJM-anchored), integrations (API contracts, data flow), restart threshold, and out-of-scope. Hard gate before /build-loop and /tdd. Use when starting a new feature, between /planning-with-files and the build cycle, or when user says "set up a contract", "what should done look like", "goal for this work", or invokes /contract. Triggers — contract, goal, "done means", acceptance criteria, rubric, user flow, integrations.

0 Updated 4 weeks ago
createusernam
AI & Automation Listed

grill-me-m

Interview the user relentlessly about a plan, design, or topic until reaching shared understanding. Walks each branch of the decision tree. Decisions are captured in a distilled brainstorm file (delegated to notes-M). Use when user wants to stress-test a plan, get grilled, run a discovery session, or says "grill me".

1 Updated 3 weeks ago
MathCaz