domain-modeling

Create and maintain domain models with glossary management and ADRs.

7|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/carl10086/ys-powers --skill domain-modeling-carl10086
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/carl10086/ys-powers/tree/main/skills/domain-modeling
Command: npx skills add https://github.com/carl10086/ys-powers --skill domain-modeling-carl10086

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the common issue of architectural drift and linguistic ambiguity in complex software projects by enforcing a rigorous, living domain model.

Core Features & Use Cases

  • Glossary Management: Maintains a canonical CONTEXT.md to ensure consistent terminology across the codebase.
  • Architectural Decision Records (ADR): Provides a structured, lightweight framework for documenting high-stakes technical trade-offs.
  • Use Case: When a team is debating whether to use event sourcing or a traditional CRUD approach, this skill guides the documentation of the decision and its rationale to prevent future confusion.

Quick Start

Use the domain-modeling skill to analyze the current project terminology and propose a canonical definition for the term order status.

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 to resolve terminology ambiguity?

You can maintain a ubiquitous language glossary by enforcing a canonical CONTEXT.md file. This ensures consistent terminology across the codebase and prevents linguistic ambiguity in complex domain-driven design projects.

What is the best way to document architectural decisions for high-stakes technical trade-offs?

The best way to document architectural decisions is using Architectural Decision Records (ADRs). This provides a structured, lightweight framework to record design trade-offs and rationale, preventing future confusion and architectural drift.

How do I record the decision rationale when debating event sourcing versus a CRUD approach?

To record the decision rationale for event sourcing versus CRUD, use the architectural decision recording framework. It guides the documentation of high-stakes technical trade-offs and their underlying context to ensure traceability.

Do I need specific Markdown templates for domain modeling and ADR management?

Yes, you need established Markdown templates for context definitions and ADRs. Adhering to these templates ensures consistency and traceability when maintaining your project's domain model and ubiquitous language.

When should I use domain-driven design documentation to prevent architectural drift?

You should use domain-driven design documentation when complex software projects face architectural drift. Enforcing a rigorous, living domain model resolves linguistic ambiguity and documents critical design trade-offs.

How to analyze existing project terminology and propose a canonical definition for domain terms?

To analyze project terminology and propose canonical definitions, use the domain modeling skill. It operates within software development lifecycles to evaluate current terms and update the glossary, resolving linguistic ambiguity.