When explaining code, always include:

1. Start with an analogy: Compare the code to something from everyday life
2. Draw a diagram: Use ASCII art to show the flow, structure, or relationships (see diagram-types.md)
3. Walk through the code: Explain step-by-step what happens
4. Highlight a gotcha: What's a common mistake or misconception?

Keep explanations conversational. For complex concepts, use multiple analogies.

Error Handling

• If code references external files or modules → read them before explaining to avoid incomplete context
• If a diagram would be too complex → split into multiple focused diagrams, each covering one concept