This one walks you through the major architectural patterns with practical decision criteria. It covers monoliths, microservices, event-driven systems, serverless, Clean Architecture, DDD, and hexagonal architecture with actual code examples showing event sourcing and port-adapter patterns. The decision tree is helpful: team under 10 people, stay monolithic; need audit trails, consider event sourcing; unpredictable load, look at serverless. It's honest about the pitfalls too, like prematurely jumping to microservices or building a distributed monolith. Good reference when you're past the prototyping stage and need to make architecture decisions that will stick around for a while.
npx -y skills add miles990/claude-software-skills --skill architecture-patterns --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
cursor/plugins
metabase/metabase
metabase/metabase
telagod/code-abyss
github/awesome-copilot
DietrichGebert/ponytail