Explain Code Structure and Concepts

Code Explanation is a prompt that explains a given piece of code in detail, following a fixed five-part structure. It starts with an Overview (a 1-2 sentence high-level summary of what the code does), then a Step-by-Step Breakdown walking through the code line by line or section by section - covering what each part does, why it's written that way, and any patterns or idioms in use. It then covers Key Concepts (design patterns, language-specific features, algorithms or data structures involved), Potential Issues (unhandled edge cases, performance considerations, security concerns, possible improvements), and, where applicable, a Usage Example showing how to call or use the code.

Use this prompt when you need code explained thoroughly enough to understand not just what it does but why it's written that way and what could go wrong with it - it explicitly asks for edge cases, performance, and security concerns to be called out, not just a functional walkthrough. Its formatting guidelines call for clear, accessible language with technical terms defined on first use, code comments for complex sections, and analogies where helpful, so the explanation works for someone who isn't already fluent in the code's specific patterns. It is not meant for a quick one-line summary - the fixed five-section structure is built for a genuinely detailed explanation of a real code sample, and the prompt template ends by explicitly asking the user to provide the code before proceeding.

// Example of how to call/use this code

Given a code sample, the prompt produces a structured explanation with an overview sentence, a section-by-section walkthrough, a list of key concepts and patterns used, a list of potential issues and improvements, and a usage example like the placeholder shown above, filled in with how the actual code would be called in practice.

Developers who need a thorough explanation of unfamiliar code - onboarding to a new codebase, reviewing a pull request, or learning from an example - who want the explanation structured consistently every time rather than an unstructured summary. It suits people who specifically want potential issues and edge cases flagged alongside the explanation, not just a description of intended behavior.