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