Explain

• Walk through the logic sequentially.
• Explain non-obvious decisions and patterns used.
• Note any side effects.

Layer 4: Details (on request)

• Edge cases handled.
• Performance characteristics (time/space complexity).
• Potential issues or technical debt.

4. Add context:
   • Show how other parts of the codebase use this code.
   • Reference related files or modules.
   • Mention relevant design patterns by name.

Guidelines

• Use the code's own variable and function names in the explanation.
• If the code is poorly written or confusing, say so constructively with improvement suggestions.
• Use analogies for complex concepts when helpful.
• For long files, provide a table of contents / map before diving into details.
• Include a visual diagram (ASCII or Mermaid) for complex data flows or architectures.
• Don't just restate the code in English — explain the why, not just the what.