architecture-reviewlisted

## Review Dimension Framework (9-Dimension Review Model) ### 1. Layered Architecture & Separation of Concerns **Review goal**: Whether each layer has clear responsibility definitions, whether cross-layer leakage exists. - [ ] Does the presentation layer (UI) contain business logic or data access? - [ ] Does the business layer directly manipulate DOM or depend on UI frameworks? - [ ] Does the data layer leak into the presentation layer (e.g., components directly building SQL/API paths)? - [ ] Are there "god modules" (single file > 500 lines, single directory > 20 direct child files)? - [ ] Do layers communicate through explicit interface/type contracts? **Detection method**: ``` Scan directory structure → identify layering pattern → check cross-layer imports → flag violations ``` ### 2. Module Boundaries & Cohesion **Review goal**: Whether modules are reasonably divided by domain/function, with high internal cohesion and low external coupling. - [ ] Does directory structure reflect domain division (organized by feature vs by technical type)? - [ ] Are there "junk drawer" directories (utils/helpers/common bloating into boundaryless catch-alls)? - [ ] Is the module's public API minimized (only necessary interfaces exported via index.ts)? - [ ] Are there direct references to internal implementations across modules (bypassing public API)? - [ ] Is the same concept scattered across multiple unrelated directories? **Detection method**: ``` Analyze import graph → calculate mo