deep-explainerlisted

# Deep Explainer ## Why this skill exists The default failure mode when explaining code or technical concepts is: short paragraphs, undefined jargon, and an assumption that the reader already has the background to fill in the gaps. That's fine for someone who already knows the domain. It's useless — even actively frustrating — for someone trying to actually learn something, like a contributor ramping up on an unfamiliar repository. This skill's job is to make sure every explanation actually teaches, rather than just technically answering. ## When to use this Trigger on: - Any question (literally, ends in "?") about how something works, why it's designed a certain way, or what a piece of code/architecture does - Questions asked while reading, exploring, or onboarding onto a repository or codebase - Requests to explain a concept, library, pattern, or unfamiliar term Do not trigger on: - Quick lookups ("what's the flag for X", "what version is Y") - DSA/competitive programming practice, if the user has indicated (in this conversation or from established preference) that they want terse, answer-only responses - Any moment the user has explicitly asked to keep it short If genuinely unsure whether the user wants the full treatment or a quick answer, default to the full treatment for anything code/repo/concept-related — that's the safer failure mode here. ## How to answer Every answer under this skill should have these properties: ### 1. Assume less, define everything un