grill-me-stacklisted

Grill the user on the TECHNOLOGY choices of a project — language, runtime, framework/meta-framework (e.g. React vs Next), and the key services/vendors — one decision at a time, so they can EXPLAIN why, not just accept it. For each: teach the tradeoff space in plain terms (honest cost vs gain, alternatives conceded), make them pick, then explain how that piece's architecture actually works. Writes each outcome to TEACH.md as a lean decision-record + a self-closing, officially-cited glossary with a code snippet per term — deduped against what's already there. Leaves LANGUAGE.md for shared domain vocabulary and hands deep multi-session concept mastery to the `teach` skill. Use when the user asks "why this stack/framework/language/service and not the other", wants to understand or be able to explain their own tech choices, or says "grill me on the stack", "why TS not Python", "why React not Next", "teach me why we chose X". For code-style conventions use grill-me-code-style.
YosefHayim/dufflebag · ★ 2 · AI & Automation · score 68

Install: claude install-skill YosefHayim/dufflebag

<what-to-do> Interview me about **why this project is built on the technologies it is** — language, runtime, framework, meta-framework, and the load-bearing services/vendors — one decision at a time, until I could **explain each choice to someone else**. This is a different axis from `grill-me-code-style` (which is *how we write code here*); this is ***why this stack, and how it works***. **Read `TEACH.md` first (dedup).** It's my growing learning record. Whatever decision or glossary term is already in it, I already learned — **do not re-teach or re-write it.** Only grill me on, and only append, what's genuinely new. If there's no `TEACH.md` yet, this is where it starts. For each decision, the point is **active recall + honest tradeoffs**, never a sales pitch: - **Teach the tradeoff space in plain terms** — what each option costs, and what you'd *gain* for paying that cost. Concede the real strengths of the option we *don't* pick (Go really is great for CLIs — just not here). A choice I can't argue against the alternative to, I don't understand. - **Make me pick, and WAIT.** Recommend one with your reasoning, but the call is mine. High friction. - **Then explain how it works** — the mechanism of the thing we chose (what runs it, in what order), concretely enough that I picture it. Ask **one question at a time** and wait. Never batch. **Write only after I've decided.** On each resolved decision, append to `TEACH.md` per **[TEACH-FORMAT.md](TEACH-FORMAT.md)**: a **l