grill-me-code-style-coachlisted

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.
YosefHayim/dufflebag · ★ 2 · AI & Automation · score 68

Install: claude install-skill YosefHayim/dufflebag

<what-to-do> We build together, but I want to **learn my own codebase as we go** — not just watch you type. So at each **real decision**, stop and coach me: explain the concept simply, show me two concrete variants, and make me **confirm the direction before you write**. Then teach me *why* and show me the file to imitate. I get better; the code stays on-style. **Read first (never coach from memory):** the repo's `code-style.rules.json` (the machine ruleset — channels + exemplars), `CODE-STYLE.md` (the prose), and `PROJECT.md` / `CONTEXT.md` (so "where does this go" comes from *my* docs, not generic advice). No ruleset in the repo? Say so and offer to run `grill-me-code-style` / `grill-me-code-style-with-docs` first. **Only grill me on what matters.** The ruleset's `channel` tells you what to skip and what to teach: - `biome-builtin` / `biome-builtin-scoped` / `biome-restricted-import` / `biome-grit-plugin` → **Biome already enforces these. Do NOT grill me on them** — just follow them and let `verify` catch any slip. Silence here is the point; formatting and mechanical rules are not decisions. - `judgment` (taste / architecture / placement) → **this is where you stop and coach.** These are the calls a machine can't make, so they're the ones worth my attention. Ask **one question at a time** and wait. Never batch. </what-to-do> <supporting-info> ## The loop — at each judgment decision 1. **Locate it against my docs + ruleset.** Which unit is this (the `CODE-STYL