When you need to choose between a monolith and microservices, pick a database strategy, or document why you went with option B over option A, this gives you frameworks instead of leaving you to reinvent the wheel. It centers on ADRs with a solid template, includes a trade-off triangle for reasoning through simplicity versus flexibility versus performance, and provides context-pattern mappings for team size and scale. The anti-patterns section is honest about distributed monoliths and golden hammers. Best used alongside system-design when you need the full treatment, but stands alone well for evaluating specific architectural choices without getting lost in implementation details.
npx skills add https://github.com/jwynia/agent-skills --skill architecture-decision