explain

To explain complex code architecture for onboarding, provide the codebase or target file to generate a detailed explanation covering structured big-picture intros, step-by-step data flow tracing across boundaries, and clear design rationale.

The best way to trace data flow in unfamiliar code is to map step-by-step data paths across component boundaries. This identifies system dependencies, reveals behavioral logic, and highlights exactly what would break if specific features are modified.

Yes, you can use it to understand code rationale before modifying features. It enforces rationale-focused explanations of design decisions and maps dependencies to ensure you fully grasp system behavior and potential breakage risks before making changes.

Yes, it scales for both high-level architecture and specific component behavior. It enforces a big-picture intro while simultaneously tracing detailed data-path logic across components, making it suitable for both junior and senior developers.

You need to provide the codebase or target file. The system then generates a detailed, actionable explanation covering the architecture, data flow paths, design rationale, and potential modification risks associated with the system.

Use a structured code explanation tool during onboarding, when exploring unfamiliar code, or before modifying features you don't fully understand. It maps data flows and dependencies to reveal exactly what would break if the system is changed.