senior-architect

Generates architecture diagrams, analyzes dependencies, and assesses project structure for technical decisions.

2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill senior-architect-bryanpinheiro77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senior-architect
Source: https://github.com/BryanPinheiro77/FinanceBot-BackEnd/tree/main/.agents/skills/senior-architect
Command: npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill senior-architect-bryanpinheiro77

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Making sound architecture decisions requires understanding your current codebase structure, dependency health, and the trade-offs between patterns like monoliths and microservices. This Skill automates that analysis and provides structured decision workflows so you can evaluate options with evidence instead of guesswork. ## Core Features & Use Cases - Architecture Diagram Generation: Scans a project directory and produces component, layer, or deployment diagrams in Mermaid, PlantUML, or ASCII format. - Dependency Analysis: Parses package.json, requirements.txt, pyproject.toml, go.mod, or Cargo.toml to detect circular dependencies, compute a coupling score, and flag problematic packages. - Architecture Assessment: Detects patterns (layered, MVC, hexagonal, clean, microservices), finds god classes and oversized files, and reports layer violations with recommendations. - Decision Workflows: Provides step-by-step guides for database selection, architecture pattern selection, and monolith-vs-microservices decisions, plus reference docs covering 9 architecture patterns. - Use Case: Before refactoring a growing codebase, run the project architect script to confirm the detected pattern, check for layer violations, then generate a Mermaid diagram to share the current state with your team. ## Quick Start Analyze my project in the current directory to detect its architecture pattern, check for circular dependencies, and generate a Mermaid component diagram.

Frequently Asked Questions about senior-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an architecture diagram from my project?▼

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

How do I detect circular dependencies in a codebase?▼

Run the dependency analyzer with the --check circular flag. It builds a graph of internal module imports and uses depth-first search to find cycles, reporting each circular chain such as auth to user to permissions to auth.

Should I choose a monolith or microservices architecture?▼

Choose a monolith for small teams under ten developers, unclear domain boundaries, and rapid iteration needs. Choose microservices when teams own services end-to-end, independent deployment is critical, and scaling requirements differ per component. A modular monolith is a common hybrid starting point.

Which package managers does the dependency analyzer support?▼

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 parses direct and dev dependencies from whichever manifest file it detects.

What architectural patterns can the project architect detect?▼

It detects layered, MVC, hexagonal, clean, microservices, modular monolith, and feature-based patterns by matching directory names and file indicators against pattern signatures. It reports the best match with a confidence percentage.

When should I not use event sourcing or CQRS?▼

Avoid event sourcing for simple CRUD applications without audit requirements, since storage grows indefinitely and queries become complex. Avoid CQRS when read and write models are nearly identical or the read/write ratio is balanced, as the added synchronization complexity is not justified.