Architecture Review

What it does

This skill analyzes architectural designs for potential risks, inefficiencies, and adherence to best practices using AI-powered insights. It systematically evaluates codebases by gathering context (project structure, dependencies, data flow), assessing design principles (SOLID, DRY, YAGNI, Separation of Concerns), checking for anti-patterns (God Class/Module, Spaghetti Code, Circular Dependencies), and evaluating non-functional requirements (Scalability, Maintainability, Security). Finally, it generates a structured review report summarizing findings, strengths, concerns, recommendations, and potential trade-offs.

When to use it

• When reviewing new architectural designs for a project.
• To proactively identify potential issues in existing codebases.
• During code reviews to provide more comprehensive feedback beyond basic syntax or logic errors.
• To assess the scalability and maintainability of specific service layers (e.g., src/services/).
• When seeking suggestions for improving architectural patterns and reducing technical debt.

Key capabilities

• Architecture Context Gathering: Identifies project structure, key components, dependencies, and data flow.
• Design Principle Evaluation: Checks adherence to SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion), DRY, YAGNI, and Separation of Concerns.
• Anti-Pattern Detection: Identifies common anti-patterns like God Class/Module, Spaghetti Code, Circular Dependencies, and Leaky Abstractions.
• Non-Functional Requirement Assessment: Evaluates the architecture against requirements for Scalability, Maintainability, Testability, Security, Performance, and Observability.
• Report Generation: Creates a structured report with a summary, strengths, concerns (prioritized), recommendations, and trade-offs.

Example prompts

• "Review the architecture of src/services/ for scalability and maintainability."
• "Analyze this codebase for SOLID principle violations."
• "Check this design for common anti-patterns like God Classes or Circular Dependencies."

Tips & gotchas

• The skill relies on understanding the project's structure, so providing clear context is crucial.
• Not all identified issues are equally important; prioritize based on your specific needs and constraints.
• Consider the trade-offs involved in architectural changes – the skill will attempt to highlight these as well.