skills.rest
guardiatechnology
guardiatechnologyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

kata-domain-model

Produce a DDD domain model with entities, aggregates, and events.

Updated Sep 3, 2025
Search Tags:#domain modeling#ddd#bounded context#ubiquitous language#cloud events#integration events#entity aggregates
One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-domain-model
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kata-domain-model
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-domain-model
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-domain-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you discover, structure, and persist a Domain-Driven Design (DDD) domain model for a specific feature or module, turning ambiguous business knowledge into a complete canonical set of entity and event documents.

Core Features & Use Cases

  • Guided domain discovery: transforms directives and open questions into a domain description, business rules, and system boundaries.
  • Ubiquitous language and context mapping: defines consistent terminology and maps bounded contexts using a context map pattern.
  • Canonical persistence workflow: produces distributed outputs for entity catalog files and integration events, delegating actual persistence to other katas/tools.

Example Use Case

Model a bounded context for "scheduled transfers" where accountants schedule transfers, supervisors approve them, and a scheduler triggers execution on the scheduled date, including lifecycle states, invariants, use cases, and CloudEvents integration event types.

Quick Start

Ask the AI to run the Domain Modeling (DDD) workflow for your module by providing the bounded context name, domain description, and CloudEvents module, and answer any missing questions about actors, boundaries, and triggers.

Frequently Asked Questions about kata-domain-model

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

FAQPage Schema
How do I design a DDD domain model with bounded contexts and ubiquitous language?▼

Designing a DDD domain model requires guided discovery to define ubiquitous language, map bounded contexts, and specify entity aggregates and use cases. The workflow transforms ambiguous business knowledge into a complete canonical set of entity and event documents with lifecycle states and invariants.

What is the best way to define bounded context mapping for a new module?▼

Bounded context mapping is best defined by applying a context map pattern alongside ubiquitous language definition. This approach establishes consistent terminology and explicit system boundaries, ensuring clear separation between domain modules and their integration points.

Can I generate CloudEvents integration event types as part of domain modeling?▼

Yes, generating CloudEvents integration event types is a core part of this domain modeling workflow. The process conforms to lex-cloudevents requirements, producing distributed outputs for integration events that align with your entity catalog and bounded context design.

How do I specify entity aggregates and invariants for a bounded context?▼

Specifying entity aggregates and invariants involves defining lifecycle states and business rules through guided discovery. The workflow produces complete entity specifications that conform to lex-entities and codex-entities requirements, including ACL boundary handling and hotspot identification.

Does this domain modeling workflow support persisting artifacts to Notion?▼

Yes, the workflow persists distributed domain modeling artifacts via kata-feature-designs-docs with downstream consolidation into Notion. It produces distributed outputs for entity catalog files and integration events, delegating actual persistence to other katas and tools.

When do I need to identify ACL boundary handling and hotspots in domain modeling?▼

ACL boundary handling and hotspot identification are needed when designing a feature or module within a complex bounded context. They should be specified during entity and aggregate definition to ensure system boundaries are protected and performance risks are mitigated.

Related Skills

Explore More Software Engineering Skills→
DGouronDGouron
41

ddd

Guide teams to split domains into bounded contexts and define a ubiquitous language.

Community
Intermediate
guardiatechnologyguardiatechnology

kata-events-doc

Generate canonical CloudEvents documentation for Guardia bounded contexts and modules.

Official
Advanced
arthur-debertarthur-debert

lex-primer

Review .lex files for structural correctness and syntax rules.

Community
Basic
SSiertsemaSSiertsema

ddd-strategic-modeling

Identify bounded contexts and subdomain classifications to produce context maps with relationships and ubiquitous language.

Community
Advanced