full-scan

You can map modules by running a macro-level codebase scan that classifies core, infrastructure, and business modules. This generates a structured project structure document defining module distribution and layered boundaries for architecture planning.

Generating a project structure document for team handoffs is best handled by automating macro-level codebase scanning. This identifies module types and overall layered boundaries, producing a structured project overview that clarifies architecture for new team members.

Macro-level code scanning identifies third-party libraries and business modules by applying glossary rules to classify module types. It evaluates the codebase to distinguish external dependencies from core infrastructure and business logic, defining the overall layered boundaries.

Yes, you can use this macro code scan for game development architecture reviews. It automates project structure mapping to identify module types and layer boundaries, outputting structured documentation that supports architecture evaluation and planning in game development projects.

You need a separate module analyzer when deeper analysis of internal module details is required. A full codebase scan provides a macro view of module types and boundaries, while a detailed module analyzer inspects the internal logic without cluttering the macro architecture overview.

Yes, the project structure document includes boundary definitions for architecture planning. The automated scanning process ensures macro-level module classification using glossary rules and outputs structured documentation detailing module distribution and the overall layered boundaries of the codebase.