Architecture Patterns

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.

skills.sh installs: 280
GitHub stars: 26
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add miles990/claude-software-skills --skill architecture-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

Architecture Patterns

Overview

Architecture patterns provide proven solutions for structuring software systems. Choosing the right architecture is crucial for scalability, maintainability, and team productivity.

Patterns

Monolithic Architecture

Description: Single deployable unit containing all application functionality.

Key Features:

Simple deployment and development
Shared database and memory
Straightforward debugging

Use Cases:

MVPs and startups
Small teams (< 10 developers)
Simple domain logic

Best Practices:

src/
├── modules/          # Feature-based organization
│   ├── users/
│   ├── orders/
│   └── products/
├── shared/           # Cross-cutting concerns
└── infrastructure/   # External services