---
description: Explain code, concepts, or errors in plain terms
argument-hint: "[topic: code, concept, or error]"
---
Explain the following in clear, plain language: $@

Structure your answer as:
1. **What it is** — one-sentence summary
2. **How it works** — walk through the key parts step by step
3. **Why it matters** — purpose, trade-offs, or design intent
4. **Connections** — how it relates to the surrounding system or codebase
5. **Key details to know** — important gotchas, assumptions, or common pitfalls

Avoid unnecessary jargon. If showing code, keep snippets short and annotate them. If explaining an error, include the likely cause and how to fix it.