Architecture Decision Framework

1---
2name: architecture
3description: Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
4allowed-tools: Read, Glob, Grep
5---
6 
7# Architecture Decision Framework
8 
9> "Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
10 
11## 🎯 Selective Reading Rule
12 
13**Read ONLY files relevant to the request!** Check the content map, find what you need.
14 
15| File | Description | When to Read |
16|------|-------------|--------------|
17| `context-discovery.md` | Questions to ask, project classification | Starting architecture design |
18| `trade-off-analysis.md` | ADR templates, trade-off framework | Documenting decisions |
19| `pattern-selection.md` | Decision trees, anti-patterns | Choosing patterns |
20| `examples.md` | MVP, SaaS, Enterprise examples | Reference implementations |
21| `patterns-reference.md` | Quick lookup for patterns | Pattern comparison |
22 
23---
24 
25## 🔗 Related Skills
26 
27| Skill | Use For |
28|-------|---------|
29| `@[skills/database-design]` | Database schema design |
30| `@[skills/api-patterns]` | API design patterns |
31| `@[skills/deployment-procedures]` | Deployment architecture |
32 
33---
34 
35## Core Principle
36 
37**"Simplicity is the ultimate sophistication."**
38 
39- Start simple
40- Add complexity ONLY when proven necessary
41- You can always add patterns later
42- Removing complexity is MUCH harder than adding it
43 
44---
45 
46## Validation Checklist
47 
48Before finalizing architecture:
49 
50- [ ] Requirements clearly understood
51- [ ] Constraints identified
52- [ ] Each decision has trade-off analysis
53- [ ] Simpler alternatives considered
54- [ ] ADRs written for significant decisions
55- [ ] Team expertise matches chosen patterns
56