architecture-reviewer
Review software architecture for SOLID principles, design patterns, scalability, and maintainability. Use when evaluating system design or planning refactoring.
Best use case
architecture-reviewer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Review software architecture for SOLID principles, design patterns, scalability, and maintainability. Use when evaluating system design or planning refactoring.
Teams using architecture-reviewer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/architecture-reviewer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How architecture-reviewer Compares
| Feature / Agent | architecture-reviewer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Review software architecture for SOLID principles, design patterns, scalability, and maintainability. Use when evaluating system design or planning refactoring.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Architecture Reviewer Skill
システムアーキテクチャを評価し、設計改善を提案するスキルです。
## 概要
SOLID原則、デザインパターン、マイクロサービス設計等の観点からアーキテクチャをレビューします。
## 主な機能
- **SOLID原則評価**: 単一責任、開放閉鎖、リスコフ置換等
- **デザインパターン**: 適切なパターンの適用状況
- **レイヤー分離**: プレゼンテーション、ビジネス、データ層
- **依存性管理**: 依存性注入、循環依存の検出
- **スケーラビリティ**: 水平・垂直スケーリング
- **マイクロサービス**: サービス境界、通信パターン
- **データベース設計**: 正規化、インデックス、パーティショニング
## 使用方法
```
このアーキテクチャをレビュー：
[アーキテクチャ図またはコード]
評価項目:
- SOLID原則
- スケーラビリティ
- 保守性
```
## レビュー観点
### 1. SOLID原則
**単一責任原則（SRP）**:
```typescript
// ❌ 複数の責任
class User {
saveToDatabase() {}
sendEmail() {}
generateReport() {}
}
// ✅ 単一責任
class User {}
class UserRepository {
save(user: User) {}
}
class EmailService {
send(to: string) {}
}
class ReportGenerator {
generate(user: User) {}
}
```
**依存性逆転（DIP）**:
```python
# ❌ 具象に依存
class UserService:
def __init__(self):
self.db = MySQLDatabase() # 具象クラス
# ✅ 抽象に依存
class UserService:
def __init__(self, database: DatabaseInterface):
self.db = database # インターフェース
```
### 2. レイヤー構造
```
┌─────────────────────────────┐
│ Presentation Layer │ UI, API Endpoints
├─────────────────────────────┤
│ Application Layer │ Use Cases, Orchestration
├─────────────────────────────┤
│ Domain Layer │ Business Logic, Entities
├─────────────────────────────┤
│ Infrastructure Layer │ Database, External APIs
└─────────────────────────────┘
```
### 3. マイクロサービス設計
```
推奨パターン:
- API Gateway: 単一エントリーポイント
- Service Discovery: 動的サービス検出
- Circuit Breaker: 障害の連鎖防止
- Event Sourcing: イベント駆動
- CQRS: コマンドとクエリの分離
```
## 出力例
```markdown
# アーキテクチャレビュー結果
## 総合評価: B+
### 良好な点
✅ クリーンアーキテクチャの採用
✅ 適切な依存性注入
✅ レイヤー分離が明確
### 改善点
#### [HIGH] 循環依存の存在
**場所**: OrderService ↔ PaymentService
**影響**: テスタビリティの低下、デプロイの複雑化
**推奨**: イベント駆動アーキテクチャに変更
#### [MEDIUM] 単一責任原則違反
**場所**: UserController
**問題**: 認証、認可、ビジネスロジックが混在
**推奨**: 責務を分離
### アーキテクチャ提案
1. **イベント駆動への移行**: サービス間の結合度削減
2. **CQRS導入**: 読み書きの分離で性能向上
3. **キャッシュ層追加**: Redis で頻繁な読み取り最適化
```
## バージョン情報
- スキルバージョン: 1.0.0
- 最終更新: 2025-01-22Related Skills
athena-pr-reviewer
PROACTIVELY USED when reviewing a PR, branch, or Jira story. Handles code review against requirements and provides actionable feedback.
astro-architecture
Technical architecture for Astro lead generation websites. Use when setting up new projects, configuring build tools, or establishing project foundations. For images use astro-images skill. For SEO use astro-seo skill.
assessing-architecture-quality
Use when assessing codebase architecture and you feel pressure to soften critique, lead with strengths, or frame problems diplomatically - provides evidence-based critical assessment resisting relationship and economic pressures
architecture
Comprehensive system architecture design and implementation workflow that orchestrates expert analysis, technical decision-making, and architectural pattern selection using the integrated toolset. Handles everything from initial system analysis to implementation-ready technical specifications.
architecture-workshop
Framework for designing new architectural mechanisms when existing patterns don't fit
architecture-validator
Validate hexagonal architecture (Domain, Application, Infrastructure, Presentation). Use when creating new files in src/, reorganizing code, or when the user requests architecture validation.
architecture-validation
Dynamically validate codebase compliance with architectural decisions and constraints
architecture-to-json
Guide for extracting architectural diagrams, flowcharts, and sequence diagrams into a structured JSON format. Use this skill when you need to transform a visual or textual description of a system architecture or workflow into a clear, structured JSON representation.
architecture-tech-lead
This skill should be used when the user asks to 'review my architecture', 'improve testability', 'refactor for testing', 'reduce mocking in tests', 'too many mocks', 'extract pure functions', 'functional core imperative shell', 'design a feature', 'evaluate approaches', 'make code more testable', 'domain modeling', 'DDD design', 'bounded contexts', 'too much coupling', or needs architectural validation for Java/Spring Boot or TypeScript/Next.js codebases. Use for design decisions, not implementation.
architecture-synthesis
Generate a reference architecture specification from analyzed frameworks. Use when (1) designing a new agent framework based on prior art, (2) defining core primitives (Message, State, Tool types), (3) specifying interface protocols, (4) creating execution loop pseudocode, or (5) producing architecture diagrams and implementation roadmaps.
architecture-strategist
Use this agent when analyzing code changes from an architectural perspective, evaluating system design decisions, or ensuring changes align with established architectural patterns. Triggers on requests like "architecture review", "design evaluation", "system architecture analysis".
architecture-status
Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps). Use when the user asks "What's our architecture status?", "Show architecture documentation", "How many ADRs do we have?", "What decisions are documented?", "Architecture health check", or wants an overview/summary of documentation state. Do NOT use for listing team members (use list-members), creating new documents (use create-adr), or conducting reviews (use architecture-review or specialist-review).