How does it handle architectural trade-offs?

It provides a standardized Trade-off Analysis Template to compare options based on complexity, scalability, and team familiarity to justify design decisions.

Does this skill provide folder structure recommendations?

Yes, it offers specific directory templates for both layer-based (simple) and feature-based (modular) project organizations.

How does it help in choosing the right pattern?

It includes a selection guide that recommends specific patterns based on project size (lines of code) and the number of developers on the team.

What architecture patterns are included in this skill?

The skill provides guidance on Layered Architecture, Clean Architecture, Hexagonal (Ports & Adapters), Event-Driven Architecture, and CQRS.

Software Architecture Patterns

Name: Software Architecture Patterns
Author: OrdinalDragons

byOrdinalDragons

Developer Tools

Provides expert guidance on selecting and implementing software architecture patterns and project structures.

About

The Architecture Patterns skill enables Claude to act as a senior technical architect by providing structured frameworks for system design and codebase organization. It offers a curated catalog of industry-standard patterns—including Clean Architecture, Hexagonal, and CQRS—alongside a decision-making guide tailored to project scale and team size. By utilizing this skill, developers can ensure long-term maintainability and scalability through standardized directory structures and formal trade-off analysis templates.

Key Features

Pattern selection matrix based on project scale and team size
Guidance on Event-Driven and CQRS implementations for complex domains
Optimized directory structure templates for feature-based or layer-based projects
Formal trade-off analysis framework for documenting design decisions
Implementation guides for Clean, Hexagonal, and Layered architectures
0 GitHub stars

Use Cases

Refactoring a legacy codebase into a more testable Hexagonal or Clean Architecture
Setting up the initial directory structure for a new enterprise-scale application
Evaluating whether to use a Modular Monolith versus Microservices for a growing team

About

Key Features

Pattern selection matrix based on project scale and team size
Guidance on Event-Driven and CQRS implementations for complex domains
Optimized directory structure templates for feature-based or layer-based projects
Formal trade-off analysis framework for documenting design decisions
Implementation guides for Clean, Hexagonal, and Layered architectures
0 GitHub stars

Use Cases

Refactoring a legacy codebase into a more testable Hexagonal or Clean Architecture
Setting up the initial directory structure for a new enterprise-scale application
Evaluating whether to use a Modular Monolith versus Microservices for a growing team