architecture-patterns

Guide backend teams through Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designing maintainable, scalable backend architectures is hard.

Core Features & Use Cases

  • Guides software teams through Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to address boundary design, dependency rules, and testability.
  • Applies to building new services, refactoring monoliths, and debugging architecture cycles.
  • Provides actionable patterns and best practices for organizing domain logic, ports/adapters, and aggregates.

Quick Start

Apply these patterns to structure a new service boundary or refactor an existing system for clear, maintainable boundaries.

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 design boundaries in Clean Architecture for a new backend service?

Clean Architecture structures backend services by enforcing dependency rules to separate domain logic from external interfaces. This skill guides you in organizing domain boundaries and ports to ensure maintainability and testability.

How do I refactor a monolith using Domain-Driven Design aggregates?

Refactoring a monolith with Domain-Driven Design involves defining clear aggregate boundaries to isolate business logic. This skill provides practical patterns for structuring aggregates and domain boundaries to untangle tightly coupled systems.

When do I need Hexagonal Architecture for backend systems?

Hexagonal Architecture is needed when you must isolate core business logic from external dependencies like databases or APIs. This skill helps implement ports and adapters to swap infrastructure components without modifying the domain.

Can I use these architecture patterns to debug architectural cycles and dependency violations?

Yes, these architecture patterns help debug dependency cycles by establishing strict rules for boundary interactions. This skill provides structured directory layouts and dependency guidelines to identify and resolve architectural violations.

Does this guidance apply to microservices or just refactoring monoliths?

This architecture guidance applies to both building new microservices and refactoring existing monoliths. It addresses boundary design, dependency rules, and testability across various backend scenarios to deliver robust systems.