Agent skill · product strategy · borghei
senior-architect
System architecture design and review. Use when designing architecture, evaluating microservices vs monolith, writing ADRs, choosing a database, planning for scalability, reviewing system design, or generating architecture diagrams.
Why this skill is useful
Adds 3 executable scripts for architecture diagram generation, dependency analysis, and architectural pattern detection that extend the AI's capabilities.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Senior Architect Architecture design and analysis tools for making informed technical decisions: visualize system structure, analyze dependencies and coupling, detect architectural patterns, and run decision workflows for databases, patterns, and monolith-vs-microservices trade-offs. Core Capabilities Diagram generation — produce component, layer, and deployment diagrams in Mermaid, PlantUML, or ASCII from a project directory. Dependency analysis — map the dependency tree, score coupling (0-100), and detect circular dependencies across npm, pip, Poetry, Go modules, and Cargo. Pattern detection — assess an existing codebase for layered/MVC/hexagonal/clean/microservices patterns, layer violations, god classes, and mixed concerns. Database selection — match data characteristics, scale, and consistency needs to SQL/NoSQL options with an ADR template. Pattern & topology selection — choose an architecture pattern by team size, deployment, and data-boundary requirements. Monolith vs microservices — apply decision checklists and a modular-monolith-first hybrid strategy. When to Use Designing a new system or refactoring existing architecture. Evaluating microservices vs monolith, or choosing a database. Writing an ADR, planning for scalability, or reviewing a system design. Generating architecture diagrams for documentation or team review. Clarify First Before generating diagrams or an assessment, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Project root — the codebase directory to analyze (drives pattern detection, dependency scoring, and diagram contents) [ ] Diagram type & format — component / layer / deployment in Mermaid / PlantUML / ASCII (sets what the generator emits) [ ] Architecture decision in question — e.g. database choice or monolith vs microservices (selects the decision workflow and ADR) Stop rule: ask only the 2-3 that most change the output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/senior-architect