architecture-design

name	Architecture Design
description	Evaluate system design, recommend refactors, review boundaries and coupling. Use when: Evaluating a new feature design before implementation, choosing between implementation approaches, reviewing component boundaries, or creating architectural decision records. Also use when refactoring existing code for maintainability. Don't use when: Reviewing a specific PR's code changes (use code-review). Don't use for debugging runtime failures (use debug-troubleshooting). Don't use for Kubernetes manifest or infrastructure design (use the appropriate ops skill). Don't use for writing tests (use testing-strategies). Outputs: Architecture analysis document with current state assessment, recommendations with tradeoffs, and incremental migration steps.
requires	[]

Architecture Design

Routing

Use This Skill When

• Evaluating a new feature design before implementation
• Choosing between two or more implementation approaches
• Refactoring existing code to improve maintainability
• Reviewing system boundaries and interfaces
• Creating an ADR (Architectural Decision Record)
• Someone asks "how should we build this?" or "should we refactor this?"

Don't Use This Skill When

• Reviewing a specific PR diff → use code-review
• Debugging a runtime error → use debug-troubleshooting
• Designing Kubernetes manifests or Flux config → use ops skills
• Writing or designing test cases → use testing-strategies
• The question is about deployment process → use gitops-deploy

Analysis Framework

1. Understand Current State