Enforce consistent domain terminology and record architectural decisions as ADRs.
npx skills add https://github.com/Flowm/dotfiles --skill domain-modeling-flowm
Please help me install this Agent Skill. Skill: domain-modeling Source: https://github.com/Flowm/dotfiles/tree/main/home/.agents/skills/domain-modeling Command: npx skills add https://github.com/Flowm/dotfiles --skill domain-modeling-flowm
This Skill solves the pervasive issue of inconsistent domain terminology, unrecorded high-impact architectural decisions, and misalignment between a team's shared ubiquitous language and actual code implementation, which leads to confusion, rework, and avoidable technical debt.
Ask the AI to define consistent ubiquitous language for your project's core domain entities and record the decision to use event sourcing for order processing as an ADR.
High-intent search queries and answers about installing and using this skill.
Yes, a living domain glossary is required to maintain shared vocabulary, while structured architecture decision records capture irreversible choices. Together they enforce consistency between domain model definitions and actual codebase behavior.
Enforcing ubiquitous language involves challenging conflicting domain terms in real time, proposing precise canonical terminology, and updating a living domain glossary to ensure teams share a consistent vocabulary. This eliminates confusion and rework caused by misaligned definitions.
Create architecture decision records only for high-impact choices that are hard to reverse, surprising without context, and involve real trade-offs. This targeted documentation approach captures critical architectural decisions while avoiding unnecessary documentation overhead.
The best way to align domain models with code is cross-referencing domain discussions against existing code to catch contradictions. This validation process ensures implemented behavior matches the agreed-upon domain model and ubiquitous language.
Domain-driven design resolves terminology conflicts by defining terms like Order, Invoice, and Customer consistently across ordering, billing, and fulfillment teams. It maintains a shared domain glossary to prevent misalignment between different bounded contexts.
Yes, a living domain glossary is required to maintain shared vocabulary, while structured architecture decision records capture irreversible choices. Together they enforce consistency between domain model definitions and actual codebase behavior.
yash-gargExtract and standardize domain terminology into a DDD-style glossary.
CuriousLearnerDocument system architecture and technical decisions with diagrams and ADRs.
FrantssCreate and maintain domain glossaries and architectural decision records in Markdown.
JohannesKoningsStandardize domain terminology and document architectural decisions in software projects.
