darthlinuxer Architecture Decision Framework
🧠 MCP Tool Available: Use Sequential Thinking for complex problem-solving in this domain. Break down decisions, debug chains, or design processes into structured reasoning steps.
"Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
🎯 Selective Reading Rule
Read ONLY files relevant to the request! Check the content map, find what you need.
| File | Description | When to Read |
|---|---|---|
| context-discovery.md | Questions to ask, project classification | Starting architecture design |
| trade-off-analysis.md | ADR templates, trade-off framework | Documenting decisions |
| pattern-selection.md | Decision trees, anti-patterns | Choosing patterns |
| examples.md | MVP, SaaS, Enterprise examples | Reference implementations |
| patterns-reference.md | Quick lookup for patterns | Pattern comparison |
🔗 Related Skills
| Skill | Use For |
|---|---|
@[skills/database-design] |
Database schema design |
@[skills/api-patterns] |
API design patterns |
@[skills/deployment-procedures] |
Deployment architecture |
Core Principle
"Simplicity is the ultimate sophistication."
- Start simple
- Add complexity ONLY when proven necessary
- You can always add patterns later
- Removing complexity is MUCH harder than adding it
Validation Checklist
Before finalizing architecture:
- Requirements clearly understood
- Constraints identified
- Each decision has trade-off analysis
- Simpler alternatives considered
- ADRs written for significant decisions
- Team expertise matches chosen patterns