domain-modeling

Maintain a centralized glossary and document architectural decisions in Markdown.

110|4|Updated Jul 19, 2016

Search Tags:#architecture #adr #domain-driven design #glossary #ubiquitous language #modeling

Ready to run

npx skills add https://github.com/deathbeam/dotfiles --skill domain-modeling-deathbeam

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the drift between a project's conceptual model and its implementation by enforcing a rigorous, shared vocabulary and documenting critical architectural decisions.

Core Features & Use Cases

Ubiquitous Language Enforcement: Actively challenges vague terminology and maintains a canonical glossary in CONTEXT.md.
Architectural Decision Records (ADR): Provides a structured framework for recording high-stakes design trade-offs.
Use Case: When a team is debating whether to call an entity a Customer or a Client, this skill forces a decision, defines the term, and ensures the codebase reflects that choice.

Quick Start

Use the domain-modeling skill to define the term Order and record an architectural decision regarding our event-sourcing strategy.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

How do I maintain a consistent ubiquitous language across a multi-context repository?▼

To maintain ubiquitous language across a multi-context repository, use this skill to manage a centralized glossary in CONTEXT.md, enforcing consistent terminology and challenging vague definitions.

What is the best way to document architectural decisions for domain-driven design?▼

The best way to document architectural decisions for domain-driven design is using Architectural Decision Records (ADRs), which this skill structures to record high-stakes design trade-offs and clear rationale.

How do you resolve terminology drift between a project's conceptual model and implementation?▼

To resolve terminology drift between a conceptual model and implementation, enforce a rigorous shared vocabulary by defining canonical terms in a glossary and ensuring the codebase reflects those choices.

Does this domain modeling approach require specific formats for architectural decision records?▼

Yes, this domain modeling approach requires adherence to specific Markdown formats for context definitions and ADRs to ensure long-term maintainability across single or multi-context repositories.

When should I use an architectural decision record instead of general documentation?▼

You should use an architectural decision record when documenting high-stakes design trade-offs and critical architectural choices, providing a structured framework for clear rationale rather than informal notes.