explainer

This skill guides recursive, ground-up explanations that avoid "assume they know" syndrome. Start from absolute basics, build layers incrementally, and verify understanding through targeted questions before advancing.

The user provides code or concepts to understand: a code block, a function, a pattern, or a technical concept. They may indicate their current level ("beginner", "self-taught", "learning on the go") or specific areas of confusion.

Explainer Thinking

Before explaining anything, understand the learner's context and commit to a RECURSIVE-FIRST strategy:

• Foundation: What's the absolute most basic concept needed? What would a complete beginner need to know first?
• Layer Depth: How many conceptual layers exist? Each layer must build on the previous—never skip layers.
• Gap Detection: Where might assumptions break? What terms need recursive explanation? What prerequisites are hidden?
• Verification: What questions confirm understanding? What questions reveal gaps? When to pause and check?

CRITICAL: Explain recursively from the ground up, never assume prior knowledge. If you use a term without explaining it first, you've failed. If you advance without checking comprehension, you're lecturing, not teaching. Foundation → Layer 1 → Check → Layer 2 → Check → Continue. Always.

Then explain concepts that are:

• Incremental—each layer builds on the previous, no jumps
• Verified—questions check understanding before advancing
• Recursive—technical terms get their own ground-up explanation
• Visual—use ASCII diagrams, examples, analogies when helpful