architecture-patterns

Design backend architectures using Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/agigante80/forge-kit --skill architecture-patterns-agigante80
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/agigante80/forge-kit/tree/main/plugins/forge-kit-backend/skills/architecture-patterns
Command: npx skills add https://github.com/agigante80/forge-kit --skill architecture-patterns-agigante80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and enforce scalable backend architectures by applying established patterns (Clean Architecture, Hexagonal Architecture, and Domain-Driven Design) to improve maintainability, testability, and adaptability.

Core Features & Use Cases

  • Clear architectural boundaries: Entities/Use Cases/Adapters and Ports/Adapters separation to decouple business rules from infrastructure.
  • Pattern catalog and guidance: Provides canonical structures for Clean, Hexagonal, and DDD architectures with concrete folder layouts and examples.
  • Practical refactoring support: Guides migration from monoliths to modular, testable components while preserving domain logic.

Quick Start

Define your domain boundaries and scaffold a core domain with ports and adapters using Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

Frequently Asked Questions about architecture-patterns

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

FAQPage Schema
How do I design backend architecture using Clean Architecture and Domain-Driven Design?

To design backend architecture with Clean Architecture and Domain-Driven Design, define domain boundaries and scaffold a core domain using ports and adapters to decouple business rules from infrastructure.

What is the best way to refactor a monolith into Hexagonal Architecture?

The best way to refactor a monolith into Hexagonal Architecture is to guide migration from monolithic structures to modular, testable components while preserving domain logic and enforcing clear architectural boundaries.

Can I apply Ports and Adapters to standardize architecture across multiple teams?

Yes, you can apply Ports and Adapters to standardize architecture across teams by enforcing canonical directory structures and integration patterns for Clean, Hexagonal, and DDD architectures.

How does Hexagonal Architecture improve backend maintainability and testability?

Hexagonal Architecture improves backend maintainability and testability by separating entities, use cases, and adapters, which decouples business rules from infrastructure and ensures scalable systems.

When should I use Domain-Driven Design for a new backend project?

You should use Domain-Driven Design for a new backend project when you need to improve maintainability, testability, and adaptability by establishing clear architectural boundaries between business rules and infrastructure.