architecture
Architectural reasoning framework: requirements analysis, trade-off evaluation, and ADR-based decision documentation. NOT a pattern catalog, but a thinking framework. Use when designing system architecture, choosing patterns, or making structural decisions.
When & Why to Use This Skill
This Claude skill provides a comprehensive architectural reasoning framework designed to guide developers through requirements analysis, systematic trade-off evaluations, and formal ADR (Architecture Decision Record) documentation. It ensures that system design decisions are data-driven, well-documented, and aligned with long-term project goals rather than just following arbitrary patterns.
Use Cases
- System Design Planning: Conduct deep-dive analysis of project requirements and constraints to establish a solid architectural foundation for new services.
- Trade-off Evaluation: Compare competing technical solutions, frameworks, or patterns to identify the most effective approach based on specific project constraints.
- ADR Documentation: Generate and maintain Architecture Decision Records to capture the rationale behind critical structural choices for future maintenance and team alignment.
- Design Validation: Utilize structured checklists to audit existing architectures for simplicity, scalability, and alignment with team expertise.
| name | architecture |
|---|---|
| description | Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design. |
| allowed-tools | Read, Glob, Grep |
Architecture Decision Framework
"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