Architecture Review

# 🏗 Architecture Review Playbook

## 🎯 Purpose

Use this playbook to perform a comprehensive review of a software system's architecture.

It is designed for software engineers, architects, tech leads, engineering managers, and engineering teams who want AI to provide actionable architectural feedback rather than generic suggestions.

This playbook works well for:

* Greenfield projects
* Existing applications
* Microservices
* Monoliths
* Frontend applications
* Mobile applications
* Cloud-native systems
* AI-powered applications

---

# ✅ When to Use

Use this playbook when you want to:

* Review an existing architecture
* Design a new system
* Validate architectural decisions
* Identify scalability risks
* Improve maintainability
* Reduce technical debt
* Prepare for production
* Review another team's design
* Prepare for an architecture review meeting

---

# 📥 Inputs Required

Provide as much context as possible.

## Business Context

* What problem does the system solve?
* Who are the users?
* Expected traffic
* Business priorities

---

## Technology Stack

Example:

* React
* Flutter
* Angular
* Spring Boot
* .NET
* Node.js
* PostgreSQL
* MongoDB
* Redis
* Kafka
* Kubernetes
* AWS
* Azure

---

## Current Architecture

Provide:

* Architecture diagram
* Folder structure
* Deployment diagram
* Component diagram
* Service boundaries

---

## Functional Requirements

Examples:

* Authentication
* Payments
* Search
* Reporting
* Notifications

---

## Non-Functional Requirements

Examples:

* Performance
* Scalability
* Security
* Availability
* Disaster Recovery
* Cost
* Accessibility
* Compliance

---

## Constraints

Examples:

* Budget
* Timeline
* Existing technology
* Team size
* Cloud provider
* Regulatory requirements

---

## Current Pain Points

Examples:

* Slow builds
* High latency
* Difficult deployments
* Poor developer experience
* Memory issues
* Tight coupling

---

# 🚀 Copy-Paste Prompt