Senior Architect

**Quick judgment**: This is a strong, opinionated architecture assistant for real-world codebases. It’s especially useful when you can point it at a repository and want concrete diagrams, dependency analysis, and structured decision support rather than high-level theory. **Where it excels** - Turning existing project structure into architecture diagrams (Mermaid/PlantUML/ASCII) for quick documentation and discussion. - Detecting architecture issues through dependency analysis (coupling, circular deps, outdated packages) across several popular language ecosystems. - Providing an architecture “health check” that identifies patterns, layer violations, and large/mixed-concern modules with clear recommendations. - Guiding database and architecture-pattern choices with pragmatic workflows tuned for typical web/backend systems. **Key risks / limitations** - Heuristics may misclassify patterns or layers in unconventional project layouts or less common stacks, so results should be reviewed by a human architect. - Performance on very large monorepos may be constrained by Python-based scanning and analysis. - Focus is on mainstream stacks and web/backend architectures; highly specialized or niche environments may not be well-covered. **Recommended scenarios** - Teams needing quick, repeatable architecture documentation and reviews for medium-to-large TypeScript/JavaScript, Python, Go, or Rust services. - Organizations wanting to add architecture and dependency checks into CI/CD pipelines via JSON reports. - Architects evaluating monolith vs microservices, database options, or refactoring roadmaps and wanting structured, codified workflows rather than ad-hoc discussions.