explain-architecture

Project architecture explanation involves consulting documentation directories and using code analysis tools to identify subsystems, their boundaries, responsibilities, and design rationale. It clarifies how specific components work and why certain technical implementations were chosen.

Finding design rationale and constraints for a specific component requires searching documentation directories and analyzing code. This identifies the component's boundaries, responsibilities, and the architectural decisions and risks that shaped its implementation.

Navigating architecture documentation and ADRs involves searching documentation directories and using code analysis to locate relevant architectural concepts and component responsibilities. This approach guides you directly to the design rationale and key code files.

Identifying subsystem boundaries and responsibilities by just reading code is insufficient. You must also consult documentation directories to understand the design rationale, risks, and constraints that define the architecture of the project.

Explaining software architecture using only documentation misses the actual implementation context. Limitations arise because a complete explanation requires using code analysis tools to accurately identify component boundaries, responsibilities, and constraints within the codebase.