domain-modeling

Maintains a centralized glossary in CONTEXT.md and records architectural decisions via ADRs.

63|9|Updated Jun 15, 2025

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

Ready to run

npx skills add https://github.com/willdady/platypus --skill domain-modeling-willdady

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of domain drift and ambiguous terminology in software projects, ensuring that the code and the team's shared language remain perfectly aligned.

Core Features & Use Cases

Ubiquitous Language Enforcement: Actively challenges vague terminology and maintains a canonical glossary in CONTEXT.md.
Architectural Decision Recording: Provides a structured, disciplined approach to documenting high-stakes technical trade-offs via ADRs.
Use Case: When a team is debating whether a specific entity should be called a Customer or a User, this skill forces a decision, records the definition, and ensures it is consistently applied across the codebase.

Quick Start

Use the domain-modeling skill to review our current terminology and document the decision to use PostgreSQL for our write model.

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 ubiquitous language glossary for domain-driven design?▼

To maintain a ubiquitous language glossary, use this skill to manage a centralized CONTEXT.md file that records canonical definitions and challenges vague terminology, ensuring technical implementation aligns with business concepts. It enforces consistent naming across the codebase through iterative refinement of context files.

What is the best way to record architectural decisions to prevent domain drift?▼

Recording architectural decisions to prevent domain drift is best achieved through structured ADRs that document high-stakes technical trade-offs. This skill provides a disciplined approach to capturing these decisions, ensuring the team's shared language and code remain perfectly aligned over time.

How do I resolve terminology debates like whether to use Customer or User in a domain model?▼

To resolve terminology debates like Customer versus User, this skill forces a decision, records the chosen definition in a canonical glossary, and ensures the selected term is consistently applied across the codebase. It actively challenges ambiguous terminology to maintain alignment.

When do I need to document architectural decisions with ADRs?▼

You need to document architectural decisions with ADRs when facing high-stakes technical trade-offs that impact the domain model. This skill enforces a structured approach to recording these decisions, preventing future ambiguity and ensuring alignment between business concepts and technical implementation.

Does domain-driven design documentation require specific formatting standards?▼

Domain-driven design documentation requires consistent adherence to defined formatting standards for terminology management and ADRs. This skill maintains the project's domain model by enforcing these standards across context files, ensuring the canonical glossary and architectural decisions remain structured and accessible.