architecture-patterns

This skill covers foundational architectural approaches for structuring software systems at scale. It walks through monolithic, microservices, event-driven, serverless, clean, and domain-driven architectures—each with use cases, trade-offs, and implementation guidance. A decision tree helps you pick the right pattern based on team size, deployment autonomy, audit requirements, and load variability.

Architecture Patterns helps you choose the right structural approach—from monoliths to microservices to event-driven systems—based on your team size, scalability needs, and domain complexity.

AI-generated summary based on this skill's SKILL.md

★ 19 ⁮ 5 MIT updated 2026-01-20 by miles990

Install

miles990/claude-software-skills/architecture-patterns · repository language: TypeScript

Manual (git clone) CLI (skillfed)

git clone https://github.com/miles990/claude-software-skills
cp -r claude-software-skills/software-design/architecture-patterns ~/.claude/skills/architecture-patterns

npx skillfed install miles990/claude-software-skills/architecture-patterns

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

What software architecture patterns are explained in architecture-patterns?

architecture-patterns covers foundational architectural approaches for structuring software systems at scale, including monolithic, microservices, event-driven, serverless, clean, and domain-driven architectures. Each pattern includes use cases, trade-offs, and implementation guidance to help you understand when and how to apply them.

How do I choose the right architecture for my project?

architecture-patterns includes a decision tree to help you pick the right pattern based on team size, deployment autonomy, audit requirements, and load variability. The skill walks through the trade-offs of each approach so you can match your system's constraints and goals to the most suitable architecture.

When should I use microservices vs. monolith?

architecture-patterns explains when to adopt microservices architecture versus monolithic approaches. Microservices suit scenarios requiring independent deployment, team autonomy, and varied scaling needs, while monoliths work better for smaller teams, simpler domains, and tightly coupled features. The skill helps you evaluate your specific constraints.

What is the strangler fig pattern for legacy migration?

architecture-patterns covers the strangler fig pattern as a modular approach to migrating legacy systems. This pattern lets you incrementally replace pieces of an old system with new code without a risky big-bang rewrite, reducing migration risk and allowing gradual adoption of modern architecture.

How do clean architecture and domain-driven design principles work?

architecture-patterns guides you through designing system structure using clean architecture layers with dependency inversion and domain-driven design (DDD) principles. These approaches emphasize isolating business logic from infrastructure, making systems more testable, maintainable, and aligned with domain complexity.

What patterns help design scalable systems and boost team productivity?

architecture-patterns compares architecture patterns for scalability and team productivity, covering event-driven, serverless, hexagonal, and modular monolith structures. It explains how each pattern affects deployment speed, system responsiveness, team autonomy, and operational complexity so you can optimize for your priorities.

SKILL.md

rendered from the published skill — quoted content, verbatim