code-investigator

To investigate code architecture and trace data flow, you locate the entry point and follow component interactions across UI, logic, and data layers. This clarifies design decisions and tradeoffs without quoting code line-by-line.

Understanding design decisions in an unfamiliar codebase requires tracing the code path from entry to outcome. This reveals the rationale behind component structures, potential tradeoffs, and edge cases handled within the architecture.

To troubleshoot where data is validated, trace the data flow across application layers. Locating component responsibilities and interactions pinpoints exactly where validation occurs and how it is enforced.

You can get an explanation of how authentication works without reading every line of code by tracing the specific code path. It enforces reading real code to document the overall flow, interactions, and edge cases abstractly.

An investigator approach focuses on component interactions instead of individual lines to explain how the system operates holistically. Identifying layer responsibilities and design rationale provides a clearer architectural overview than line-by-line reading.