architect-review

Analyze software architectures for integrity, scalability, and architectural decisions.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill architect-review-chicanoandres702
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-review
Source: https://github.com/chicanoandres702/SentientAIBrowser/tree/main/.agents/workflows/architect-review
Command: npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill architect-review-chicanoandres702

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineers need rigorous assessments of software architectures to ensure scalability, maintainability, and alignment with modern patterns.

Core Features & Use Cases

  • Comprehensive architectural review and guidance for microservices, DDD, EDA, and clean architecture.
  • Assessment of system designs for scalability, reliability, and maintainability across distributed systems.
  • Guidance for architectural decisions with documented considerations and recommended practices.

Quick Start

Analyze the given software design and provide an end-to-end architectural assessment covering boundaries, patterns, and non-functional requirements.

Frequently Asked Questions about architect-review

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

FAQPage Schema
How do I review microservice boundaries in a distributed system?

To review microservice boundaries, analyze your software architecture to ensure distributed system components have proper separation of concerns, scalability, and adherence to clean architecture principles. This process assesses bounded contexts and service interactions to verify architectural integrity.

How does domain-driven design apply to architecture decision records?

Domain-driven design applies to architecture decision records by documenting the rationale behind bounded context mappings and event-driven interactions. You create actionable records that capture SOLID principles adherence and recommended practices for maintaining system scalability and maintainability.

What is the best way to assess event-driven architecture for scalability?

The best way to assess event-driven architecture for scalability is to perform a comprehensive architectural review focusing on non-functional requirements. Analyze the design to ensure reliable event routing, maintainability across distributed systems, and alignment with clean architecture principles.

Can I use clean architecture principles for code changes across large distributed systems?

Yes, you can apply clean architecture principles to guide code changes across large distributed systems. Reviewing changes against SOLID principles ensures that modifications maintain architectural integrity, support scalability, and do not violate existing microservice boundaries or bounded contexts.

When should I not use event-driven design in microservices?

You should avoid event-driven design in microservices when a comprehensive architectural review reveals that strict consistency requirements outweigh the benefits of decoupled scalability. If bounded contexts require synchronous transactional integrity, event-driven patterns may introduce unacceptable complexity.