architecture

Topics in the source

• Architecture Decision Framework
• 🎯 Selective Reading Rule
• 🔗 Related Skills
• Core Principle
• Validation Checklist

"Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale." 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 | -- | Skill | Use For | |-------|---------| | @[skills/database-design] | Database schema design | | @[skills/api-patterns] | API design patterns | | @[skills/deployment-procedures] | Deployment architecture | -- "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 -- Before finalizing architecture: [ ] Requirements clearly understood [ ] Constraints identified [ ] Each decision has trade-off analysis [

This is an excerpt. Refer to the complete source and its current requirements.