domain-modeling

Model business domains using DDD patterns to define entities, value objects, aggregates, domain events, and domain services.

5|Updated Feb 3, 2026

Search Tags:#domain-driven-design #aggregate #entity #value-object #domain-modeling #domain-event #domain-service

Ready to run

npx skills add https://github.com/elct9620/ai-coding-skills --skill domain-modeling-elct9620

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/elct9620/ai-coding-skills/tree/main/skills/domain-modeling
Command: npx skills add https://github.com/elct9620/ai-coding-skills --skill domain-modeling-elct9620

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain-driven design patterns help translate complex business rules into a clear, maintainable domain model that guides code structure and boundaries.

Core Features & Use Cases

Entity: an object with a stable identity and lifecycle.
Value Object: immutable attributes, compared by value rather than reference.
Aggregate: a consistency boundary that groups related entities and value objects under a root.
Domain Service: stateless operations that don't fit neatly into an entity or value object.
Domain Event: a record of a significant past occurrence to trigger integrations or reactions.
Bounded Context: explicit separation of models to prevent cross-context leakage.

Quick Start

Define your domain concepts by creating entities, value objects, aggregates, and domain events within a coherent bounded context.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

How do I model domain logic using Domain-Driven Design patterns?▼

Model domain logic using DDD patterns by defining entities, value objects, aggregates, domain events, and domain services within a bounded context. This approach translates complex business rules into a coherent, maintainable domain model that guides code structure and enforces consistency boundaries.

When should I use an aggregate root versus a domain service?▼

Use an aggregate root to group related entities and value objects under a consistency boundary. Use a domain service for stateless operations that do not fit neatly into an entity or value object, ensuring business logic remains cohesive and properly distributed across the domain model.

What is the difference between an entity and a value object in domain modeling?▼

In domain modeling, an entity is an object with a stable identity and lifecycle, whereas a value object represents immutable attributes compared by value rather than reference. Choosing correctly ensures the domain model accurately reflects real-world business constraints.

How do I prevent model leakage across different bounded contexts?▼

Prevent model leakage across bounded contexts by defining explicit separations between models. Bounded contexts enforce boundaries that stop domain concepts from bleeding into unrelated areas, maintaining the integrity and consistency of each domain model.

Can I use domain events to trigger integrations between separate bounded contexts?▼

Yes, domain events record significant past occurrences to trigger integrations or reactions across bounded contexts. They provide a mechanism for coordinating domain logic and system workflows without tightly coupling the underlying domain models.

Do I need prior DDD knowledge to apply these domain modeling patterns?▼

Applying domain modeling patterns requires understanding DDD concepts like aggregates, entities, value objects, and bounded contexts. The Skill guides pattern selection, invariant enforcement, and boundary rules, making it suitable for software engineers designing domain-centric systems.