skills.rest
chichex
chichexCOMMUNITY
Explore all skills by this author →
GitHub

domain-modeling

Maintain project domain models via CONTEXT.md glossary and ADR files.

2|Updated Jul 13, 2026
Search Tags:#architecture#documentation#adr#glossary#modeling#domain-driven-design
One-click install
npx skills add https://github.com/chichex/skills --skill domain-modeling-chichex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/chichex/skills/tree/main/claude/domain-modeling
Command: npx skills add https://github.com/chichex/skills --skill domain-modeling-chichex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of domain drift and architectural ambiguity by providing a structured, disciplined way to maintain a project's glossary and decision records.

Core Features & Use Cases

  • Glossary Management: Maintains a centralized CONTEXT.md to ensure consistent terminology across the codebase.
  • Architectural Decision Records (ADR): Provides a lightweight framework for documenting high-impact, hard-to-reverse technical decisions.
  • Use Case: When a team is debating whether to use a specific event-driven pattern, this skill helps evaluate the trade-offs and formally record the decision if it meets the criteria for an ADR.

Quick Start

Use the domain-modeling skill to review the current project glossary and check if the proposed architectural change qualifies for a new ADR.

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 centralized glossary for domain-driven design projects?▼

Maintain a centralized glossary by documenting project domain models in a CONTEXT.md file, ensuring consistent terminology across the codebase. This structured approach prevents domain drift and aligns team vocabulary.

When should I create an architectural decision record for a technical trade-off?▼

Create an architectural decision record when debating high-impact, hard-to-reverse technical trade-offs like adopting an event-driven pattern. ADRs provide a lightweight framework to formally evaluate and document these decisions.

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

The best way to prevent domain drift is combining a centralized project glossary with architectural decision records. This structured documentation enforces strict terminology alignment and tracks high-impact technical decisions.

How do I format architectural decision records and glossary files correctly?▼

Format architectural decision records and glossary files by adhering to zero-contamination principles and specific formatting standards for CONTEXT.md and ADR files. This disciplined structure ensures documentation clarity.

Does this domain modeling approach work for software projects needing strict terminology alignment?▼

Yes, domain modeling applies directly to software development projects requiring strict terminology alignment. It maintains a centralized glossary and records high-impact technical decisions to resolve architectural ambiguity.

Related Skills

Explore More Software Engineering Skills→
musujmusuj

phase-1-schema

Define project terminology, entities, relationships, and data structures.

Community
Intermediate
HaydernCenterpointHaydernCenterpoint

shared-language

Create or update CONTEXT.md glossaries and ADRs for domain language and architectural decisions.

Community
Intermediate
acme-skunkworksacme-skunkworks

documentation-and-adrs

Automate creation and management of ADRs and project documentation.

Official
Advanced
yash-gargyash-garg

domain-modeling

Resolve ambiguous domain terminology and record architectural decisions in CONTEXT.md and ADR formats.

Community
Intermediate