domain-modeling

Detect and resolve contradictions between business language, code, and documentation.

Updated May 3, 2026

Search Tags:#architecture #documentation #refactoring #domain-driven design #glossary #terminology

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves ambiguity and contradictions between business terminology, product documentation, and the actual implementation in code, ensuring that developers and stakeholders share a precise, unified vocabulary.

Core Features & Use Cases

Terminology Auditing: Identifies overloaded terms and conflicting definitions across codebases and documentation.
Glossary Management: Establishes a single source of truth for canonical terms, boundaries, and aliases.
Decision Support: Provides a structured framework to determine when a terminology change requires a formal Architecture Decision Record (ADR).

Quick Start

Analyze the current project terminology and identify contradictions between our API schemas and the product glossary.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

How do I resolve contradictions between business terminology and code in domain-driven design?▼

Domain modeling resolves contradictions by auditing overloaded terms across codebases and documentation, establishing a centralized glossary as a single source of truth for canonical terms, boundaries, and aliases.

When do I need a centralized glossary for software architecture refactoring?▼

A centralized glossary is needed when ambiguous product documentation and code implementation cause technical debt, requiring precise domain modeling to align shared project terminology and formalize architectural boundaries.

How do I audit overloaded terms across API schemas and product documentation?▼

Terminology auditing identifies conflicting definitions across API schemas and product documentation, refining shared project terminology to ensure developers and stakeholders share a unified vocabulary.

Does a terminology change require a formal Architecture Decision Record?▼

A terminology change requires a formal Architecture Decision Record when it impacts architectural boundaries, using a structured decision support framework to formalize evidence-based definitions and prevent technical debt.

What is the best way to align project language with code and documentation intent?▼

Aligning project language with code requires detecting and resolving contradictions between business language and implementation, applying domain-driven design to establish evidence-based definitions and precise domain modeling.