ddd

Standardize domain concepts and glossary across the ikigai project.

Updated Jun 3, 2026

Search Tags:#architecture #ddd #domain-driven #ubiquitous-language #domain-modeling #bounded-contexts

Ready to run

npx skills add https://github.com/mgreenly/ikigai --skill ddd-mgreenly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ddd
Source: https://github.com/mgreenly/ikigai/tree/main/.claude/library/ddd
Command: npx skills add https://github.com/mgreenly/ikigai --skill ddd-mgreenly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns team understanding of the domain by establishing a shared glossary, consistent terminology, and clear boundaries to reduce ambiguity across code, docs, and conversations within the ikigai project.

Core Features & Use Cases

Ubiquitous Language: Establishes a consistent vocabulary across REPL, memory, persistence, and UI layers to prevent misinterpretation.
Bounded Contexts & Entities: Defines core domain models and boundaries to structure modules and ensure clear ownership.
Architectural Guidance: Provides patterns for modeling, invariants, and governance that improve system coherence and maintainability.

Quick Start

Define the project’s core domain terms in your codebase and unify your terminology across UI, docs, and tests.

Frequently Asked Questions about ddd

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

FAQPage Schema

How do I establish a ubiquitous language for domain modeling across my project?▼

To establish a ubiquitous language for domain modeling, define core domain terms in your codebase to unify terminology across REPL, memory, persistence, and UI layers, preventing misinterpretation.

What is the best way to define bounded contexts and core entities for scalable architecture?▼

Defining bounded contexts and core entities requires establishing clear module boundaries and domain models to ensure clear ownership and structure, improving system coherence and maintainability.

Why do I need a shared glossary for domain-driven design in software engineering?▼

A shared glossary for domain-driven design aligns team understanding of the domain by establishing consistent terminology and clear boundaries, reducing ambiguity across code, docs, and conversations.

Can I apply domain-driven design patterns to REPL, memory, and persistence layers?▼

Yes, you can apply domain-driven design patterns to REPL, memory, and persistence layers by establishing a consistent vocabulary and defining invariants across these components to prevent misinterpretation.

Does domain-driven design require frontmatter metadata for naming and context boundaries?▼

Yes, domain-driven design requires frontmatter metadata to satisfy requirements for naming, core entities, invariants, and context boundaries through a shared design vocabulary.