skills.rest
LLLLimbo
LLLLimboCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-patterns

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

Updated Jan 5, 2026
Search Tags:#ddd#architecture-patterns#domain-driven-design#clean-architecture#hexagonal-architecture#backend-architecture
One-click install
npx skills add https://github.com/LLLLimbo/Skills --skill architecture-patterns-llllimbo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/LLLLimbo/Skills/tree/main/backend-development/architecture-patterns
Command: npx skills add https://github.com/LLLLimbo/Skills --skill architecture-patterns-llllimbo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps software teams design scalable, maintainable backend systems by applying proven architecture patterns such as Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

Core Features & Use Cases

  • Structured guidance: provides clear, repeatable patterns for organizing codebases and boundaries.
  • Pattern coverage: covers Clean Architecture, Hexagonal Architecture, and Domain-Driven Design with examples and best practices.
  • Use Case: when refactoring a monolith or designing a new backend service, follow the patterns to create modular, testable components and explicit boundaries.

Quick Start

Plan and implement a backend service skeleton that applies Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to define domain models, application services, and ports/adapters.

Frequently Asked Questions about architecture-patterns

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

FAQPage Schema
What is the best way to structure a backend using Clean Architecture and Domain-Driven Design?▼

Hexagonal Architecture organizes backend systems into ports and adapters, separating the core domain from external concerns. It ensures application services remain isolated, creating modular and testable components with explicit boundaries for complex applications.

When do I need bounded contexts and rich domain models in backend architecture?▼

Clean Architecture differs from Hexagonal Architecture in structure by emphasizing dependency inversion through layered boundaries, while Hexagonal focuses on ports and adapters. Both patterns organize codebases to isolate the domain core and create modular, testable backend components.

When should I not use Domain-Driven Design for a backend service?▼

Hexagonal Architecture organizes backend systems into ports and adapters, separating the core domain from external concerns. It ensures application services remain isolated, creating modular and testable components with explicit boundaries for complex applications.

What is the best way to structure a backend using Clean Architecture and Domain-Driven Design?▼

You should not use Domain-Driven Design when a backend service lacks complex business logic, as the overhead of bounded contexts and rich domain models provides little value. It is best suited for scalable systems requiring explicit boundaries and maintainable components.

Related Skills

Explore More Software Engineering Skills→
undertextundertext

spdd-analysis

Analyze business requirements and codebase context to generate strategic REASONS Canvas context.

Community
Advanced
SaiyedMuhammadAnasMaududiSaiyedMuhammadAnasMaududi

architecture-patterns

blueprint for designing/maintaining complex business applications with a focus on maintainability and testability through separation of concerns and strict dependency rules. It leverages the concept of layers, where the core business logic is isolated from external details like databases and user interfaces. The result is code that is modular, easier to debug and evolvebba.

Community
Advanced
DVNghiemDVNghiem
20

clean-architecture

Apply Clean Architecture boundaries to isolate domain logic from infrastructure.

Community
Advanced
Axel-DaMageAxel-DaMage
2

microservices-architect

Design microservices architectures by decomposing monolithic applications into bounded contexts.

Community
Advanced