architect-reviewer

Evaluate system designs to validate architectural decisions and patterns.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Tnemo65/template --skill architect-reviewer-tnemo65
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-reviewer
Source: https://github.com/Tnemo65/template/tree/main/.cursor/skills/11-system-design/architect-reviewer
Command: npx skills add https://github.com/Tnemo65/template --skill architect-reviewer-tnemo65

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers and architects validate architectural decisions, assess patterns, and ensure designs meet scalability, security, and maintainability goals across complex systems.

Core Features & Use Cases

  • Architecture pattern validation and trade-off analysis across monolithic, microservices, and event-driven designs.
  • Scalability, security, maintainability, and evolution assessment with actionable recommendations.
  • Architecture artifacts review, integration strategies, and documentation quality checks.

Quick Start

Provide the system context and goals, then invoke the reviewer to produce a prioritized architectural improvement plan.

Frequently Asked Questions about architect-reviewer

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

FAQPage Schema
How do I review system designs to validate microservices architecture decisions?

To review system designs for microservices, provide your system context and goals to generate a prioritized architectural improvement plan. The evaluation validates component boundaries, data flow, and integration patterns to ensure your architecture meets scalability and security goals.

What is the best way to assess technical debt and scalability in an architecture review?

Assessing technical debt and scalability during an architecture review involves evaluating your system's evolution potential and deployment architecture. This process provides actionable recommendations to improve maintainability and validate that your current design patterns can handle growth.

Can I use this to evaluate security and data flows across event-driven architectures?

Yes, you can evaluate security and data flows across event-driven architectures by applying the reviewer to your design artifacts. It analyzes component boundaries and security constraints to validate integration strategies within complex, event-driven system contexts.

How do I analyze trade-offs between monolithic and microservices integration patterns?

Analyzing trade-offs between monolithic and microservices integration patterns requires evaluating your architecture artifacts against system goals. The review validates pattern decisions, checks documentation quality, and outputs actionable recommendations for optimizing your system's structure.

Does this architecture review work for both research and production deployment contexts?

Yes, this architecture review works for both research and production deployment contexts. It evaluates system designs by analyzing component boundaries, data flow, and security constraints to provide actionable recommendations regardless of your environment's maturity.

Why should I validate component boundaries and data flow before deploying microservices?

Validating component boundaries and data flow before deploying microservices prevents architectural misalignment and security vulnerabilities. The review identifies technical debt early and provides actionable recommendations to ensure your system design supports long-term evolution.