skills.rest
jackjin1997
jackjin1997COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ddd

Guide Domain-Driven Design with strategic and tactical patterns.

11|2|Updated Feb 3, 2026
Search Tags:#ddd#software architecture#bounded context#domain-driven-design#event sourcing#aggregate design
One-click install
npx skills add https://github.com/jackjin1997/ClawForge --skill ddd-jackjin1997
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ddd
Source: https://github.com/jackjin1997/ClawForge/tree/main/skills/ddd
Command: npx skills add https://github.com/jackjin1997/ClawForge --skill ddd-jackjin1997

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance on Domain-Driven Design (DDD) principles and patterns, enabling developers and architects to effectively model complex business domains and design resilient software architectures.

Core Features & Use Cases

  • Strategic Design: Understand and apply concepts like Core Domains, Supporting Domains, Generic Domains, Bounded Contexts, and Context Mapping.
  • Tactical Design: Implement key patterns including Entities, Value Objects, Aggregates, Domain Services, Domain Events, Repositories, and Factories.
  • Architectural Patterns: Explore and apply patterns like Hexagonal Architecture, Onion Architecture, CQRS, Event Sourcing, and Saga patterns.
  • Use Case: When designing a new microservice for an e-commerce platform, use this Skill to define clear Bounded Contexts for Order Management and Inventory, ensuring consistency and maintainability.

Quick Start

Use the ddd skill to understand the principles of strategic design and identify sub-domain types.

Frequently Asked Questions about ddd

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

FAQPage Schema
How do I define Bounded Contexts when modeling a complex software architecture?▼

Bounded Contexts are defined by applying strategic Domain-Driven Design principles to map Core, Supporting, and Generic sub-domains. This approach ensures clear boundaries, consistency, and maintainability across complex software systems.

What's the best way to design Aggregates and Value Objects in domain-driven design?▼

Design Aggregates and Value Objects using tactical DDD patterns to model business logic accurately. This ensures data consistency and transactional integrity by grouping related Entities and Value Objects into cohesive boundaries.

When do I need Event Sourcing and CQRS patterns for scalable software?▼

Event Sourcing and CQRS are needed when building scalable software requiring high performance and detailed audit trails. These architectural patterns separate read and write operations, storing state changes as a sequence of domain events.

Can I use Hexagonal Architecture to isolate domain logic in microservices?▼

Hexagonal Architecture isolates domain logic by placing application ports and adapters at the system's boundaries. This DDD-aligned pattern ensures core business rules remain independent from infrastructure and framework concerns.

How does the Saga pattern handle distributed transactions across Bounded Contexts?▼

The Saga pattern manages distributed transactions across Bounded Contexts by orchestrating a sequence of local transactions. It compensates for failures by emitting domain events, ensuring eventual consistency without distributed locks.

Do I need Context Mapping to integrate multiple sub-domains in software architecture?▼

Context Mapping is required to integrate multiple sub-domains by defining explicit translation boundaries between Bounded Contexts. It identifies team relationships and integration points, preventing tight coupling and semantic conflicts.

Related Skills

Explore More Software Engineering Skills→
dandudzidandudzi
2

domain-driven-design

Assesses the viability of Domain-Driven Design for complex business domains.

Community
Advanced
MrPointerMrPointer
2

applying-architecture-patterns

Implement Clean Architecture, Hexagonal Architecture, and Domain-Driven Design for backend systems.

Community
Advanced
Axel-DaMageAxel-DaMage
2

microservices-architect

Design microservices architectures by decomposing monolithic applications into bounded contexts.

Community
Advanced
joaquimscostajoaquimscosta
21

domain-driven-design

Apply Domain-Driven Design patterns to model complex domains with bounded contexts and aggregates.

Community
Advanced