{"enrichment":{"faq":[{"a":"architecture-patterns teaches Clean Architecture by organizing code into concentric layers\u2014entities, use cases, interface adapters, and frameworks\u2014where dependencies point inward toward the domain core. This approach isolates business logic from infrastructure, making systems testable and maintainable. You'll learn practical directory structures and how to keep your backend independent of frameworks, databases, and UI concerns.","q":"How do I structure backend code using clean architecture?"},{"a":"architecture-patterns explains Hexagonal Architecture as a pattern where your application core (domain logic) connects to the outside world through ports (interfaces) and adapters (implementations). Ports define contracts for external dependencies like databases or APIs; adapters implement those contracts. This design enables you to swap technologies without touching core logic, making your backend highly testable and loosely coupled.","q":"What are hexagonal architecture ports and adapters?"},{"a":"architecture-patterns covers Domain-Driven Design (DDD) patterns including bounded contexts, aggregates, entities, and value objects. DDD aligns code structure with business domains, using rich domain models to encode business rules directly. You'll learn how to identify domain boundaries, model complex business logic, and organize microservices or monolithic systems around domain concepts rather than technical layers.","q":"How does domain-driven design structure backend systems?"},{"a":"architecture-patterns clarifies that Clean Architecture and Hexagonal Architecture share the same core principle\u2014isolating domain logic from external concerns\u2014but emphasize different aspects. Clean Architecture focuses on layered dependency flow (inward-pointing); Hexagonal emphasizes symmetrical ports and adapters on all sides. Both achieve testability and maintainability; choose based on your team's mental model and system complexity.","q":"What's the difference between clean arch and hexagonal?"},{"a":"architecture-patterns guides refactoring by first identifying domain boundaries and separating business logic from infrastructure. Apply dependency inversion to decouple layers, introduce repository patterns for data access, and extract domain models. For microservices decomposition, use DDD bounded contexts to define service boundaries. Incremental refactoring\u2014starting with high-value, loosely-coupled modules\u2014reduces risk while improving testability.","q":"How do I refactor a monolithic app using these patterns?"},{"a":"architecture-patterns teaches that entities are domain objects with unique identities and lifecycles; value objects are immutable, identity-less objects representing domain concepts (like Money or Address); aggregates are clusters of entities and value objects treated as single units for consistency. These patterns help you build rich, expressive domain models that encode business rules directly, making backends more maintainable and aligned with domain language.","q":"What are value objects, entities, and aggregates in DDD?"}],"shadow_tags":["layered-design","separation-of-concerns","testability-first","domain-modeling","adapter-pattern","business-logic-isolation","framework-agnostic","consistency-boundaries","inversion-of-control"],"summary_rewrite":"Master three foundational backend architecture approaches\u2014Clean Architecture, Hexagonal Architecture, and Domain-Driven Design\u2014to structure systems for testability, maintainability, and scalability. Each pattern teaches dependency management, separation of concerns, and technology-agnostic core logic through practical examples and directory structures."},"files":[{"bytes":15164,"path":"bundled/skills/architecture-patterns/SKILL.md","sha256":"bfab0b9bd2521a86eeb47edc7ef939adcd7f60666c996d7461e6cb73c18327d3","url":"https://skillfed.io/files/foryourhealth111-pixel/Vibe-Skills/architecture-patterns/de218a39/SKILL.md"}],"id":"foryourhealth111-pixel/Vibe-Skills/architecture-patterns","links":{"html":"https://skillfed.io/foryourhealth111-pixel/Vibe-Skills/architecture-patterns","md":"https://skillfed.io/foryourhealth111-pixel/Vibe-Skills/architecture-patterns.md","repo":"https://github.com/foryourhealth111-pixel/Vibe-Skills"},"meta":{"agents_supported":[],"first_seen":"2026-07-28","forks":184,"language":"Python","last_updated":"2026-07-22","license":"Apache-2.0","name":"architecture-patterns","publisher":"foryourhealth111-pixel","stars":2494},"relations":{"similar":[{"id":"HermeticOrmus/LibreUIUX-Claude-Code/architecture-patterns"},{"id":"secondsky/claude-skills/architecture-patterns"},{"id":"organvm/a-i--skills/social-media-api-integration"},{"id":"llama-farm/llamafarm/rag-skills"},{"id":"jackjin1997/ClawForge/ddd"},{"id":"organvm/a-i--skills/agent-swarm-orchestrator"},{"id":"arpitg1304/robotics-agent-skills/robotics-software-principles"},{"id":"personamanagmentlayer/pcl/ai-architect-expert"},{"id":"organvm/a-i--skills/posse-distribution-architecture"},{"id":"zrt-ai-lab/opencode-skills/uni-agent"}]},"slug":{"owner":"foryourhealth111-pixel","repo":"Vibe-Skills","skill":"architecture-patterns"},"version":"de218a39"}