architecture-patterns

Architect backend systems using Clean Architecture, Hexagonal Architecture, and DDD patterns.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mporenta/airflow --skill architecture-patterns-mporenta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/mporenta/airflow/tree/main/.claude/skills/architecture-patterns
Command: npx skills add https://github.com/mporenta/airflow --skill architecture-patterns-mporenta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Backend architects and engineers often face challenges designing scalable, maintainable services. This Skill consolidates Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to guide structure, boundaries, and collaboration across teams.

Core Features & Use Cases

  • Clear separation of concerns using layered architecture to keep business logic independent from frameworks.
  • Flexible, testable designs via ports and adapters, domain models, and explicit boundaries that enable easy substitution of implementations.
  • Use Case: Refactor a monolithic service into modular, independently deployable components while preserving business rules and improving testability.

Quick Start

Assess your current backend, then map Clean Architecture, Hexagonal Architecture, and DDD concepts to your modules to begin the refactor.

Frequently Asked Questions about architecture-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I separate business logic from frameworks when architecting backend systems?

Separate business logic from frameworks by applying Clean Architecture and Hexagonal Architecture patterns, which enforce layered boundaries and keep domain models independent. This ensures maintainability and testability.

What's the best way to refactor a monolith into modular components while preserving business rules?

Refactor a monolith by mapping Clean Architecture and DDD concepts to your modules, establishing explicit boundaries and ports and adapters to isolate business rules. This improves testability and evolvability.

How does Hexagonal Architecture with ports and adapters improve backend testability?

Hexagonal Architecture improves testability by using ports and adapters to isolate the core domain model from external dependencies, allowing easy substitution of implementations and independent testing of business logic.

When do I need Domain-Driven Design for designing new backend services?

You need Domain-Driven Design when establishing architecture standards across teams or designing new services that require rich domain models and explicit boundaries to maintain complex business rules and evolvability.

Can I use this to establish architecture standards across multiple development teams?

Yes, you can establish architecture standards across teams by applying structured backend architecture patterns like Clean Architecture, Hexagonal Architecture, and DDD to enforce consistent boundaries and collaboration.