architect-reviewer

Review system designs and architectural patterns for scalability and maintainability.

30|7|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/saeed-vayghan/gemini-agent-skills --skill architect-reviewer-saeed-vayghan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-reviewer
Source: https://github.com/saeed-vayghan/gemini-agent-skills/tree/main/.gemini/skills/architect-reviewer
Command: npx skills add https://github.com/saeed-vayghan/gemini-agent-skills --skill architect-reviewer-saeed-vayghan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of ensuring robust, scalable, and maintainable system architectures by providing expert review and validation of design decisions and technical choices.

Core Features & Use Cases

  • System Design Validation: Assesses architectural patterns, component boundaries, and data flow for soundness.
  • Scalability and Performance Analysis: Evaluates a system's ability to handle growth and meet performance targets.
  • Technology Stack Evaluation: Reviews the appropriateness and viability of chosen technologies.
  • Use Case: A startup is designing its core platform. This Skill can review their proposed microservices architecture, ensuring it aligns with best practices for scalability and maintainability before significant development investment.

Quick Start

Use the architect-reviewer skill to assess the scalability and maintainability of the proposed system architecture.

Frequently Asked Questions about architect-reviewer

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

FAQPage Schema
How do I validate my system design for scalability and maintainability?

To validate system design for scalability and maintainability, you can review architectural patterns, component boundaries, and data flow to assess their soundness against your growth targets and performance requirements.

What is the best way to evaluate a proposed microservices architecture before development?

Evaluating a proposed microservices architecture involves analyzing system context and design documents to ensure component boundaries and technology choices align with best practices for scalability and maintainability.

Can I use an architecture review to assess technical debt and evolution potential?

Yes, an architecture review assesses technical debt and evolution potential by analyzing your system context, technology choices, and constraints to provide strategic recommendations for improvement.

What context do I need to provide for a system design validation?

For system design validation, you must provide context on system purpose, scale requirements, constraints, team structure, technology preferences, and evolution plans to receive accurate strategic recommendations.

How does a technology stack evaluation determine if my chosen technologies are appropriate?

A technology stack evaluation determines appropriateness by reviewing the viability of chosen technologies against your architectural patterns, maintainability needs, and long-term system evolution plans.

When should I not use automated architectural pattern analysis?

Automated architectural pattern analysis should not be used when you lack defined system context, scale requirements, or technology preferences, as strategic recommendations require these inputs to assess soundness accurately.