senior-architect

Run the architecture diagram generator script with your project path and choose a format: Mermaid, PlantUML, or ASCII. It scans directories, detects components and their import relationships, and outputs component, layer, or deployment diagrams.

Run the dependency analyzer script on the project directory with the circular check option. It builds an internal module import graph, runs depth-first cycle detection, and reports each circular dependency chain it finds.

Choose microservices when teams can own services end-to-end, independent deployment is critical, and domain boundaries are well understood. For small teams or unclear boundaries, start with a modular monolith and extract services only when scaling or deployment needs diverge.

The analyzer supports npm and yarn via package.json, pip via requirements.txt, Poetry via pyproject.toml, Go via go.mod, and Rust via Cargo.toml. It auto-detects the package manager from files present in the project root.

It detects layered, MVC, hexagonal, clean, microservices, modular monolith, and feature-based patterns by matching directory names and file indicators against pattern signatures. Each detection includes a confidence score based on structural evidence.

Static analysis infers patterns from directory names and import statements, so it can misclassify unconventional structures and cannot evaluate runtime behavior or business context. Treat its confidence scores and recommendations as a starting point for human review.