Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

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 When to Use This skill is applicable to execute the workflow or actions described in the overview. Limitations Use this skill only when the task clearly matches the scope described above. Do not treat the output as a substitute for environment specific validation, testing, or expert review. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.