skills.rest
sanjanb
sanjanbCOMMUNITY
Explore all skills by this author →
GitHub

domain-modeling

Build and maintain project domain glossaries and architectural decision records.

1|Updated Jul 23, 2026
Search Tags:#domain modeling#adr#domain-driven design#glossary#bounded context#ubiquitous language#architecture decisions
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill domain-modeling-sanjanb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/mp-domain-modeling
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill domain-modeling-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Domain terminology drifts and architectural decisions get forgotten as projects grow, leaving future readers guessing why the code looks the way it does. This Skill actively sharpens a project's domain model during design sessions by challenging fuzzy terms, stress-testing concepts with concrete scenarios, and recording decisions the moment they crystallize. ## Core Features & Use Cases - Ubiquitous Language Management: Maintains an opinionated CONTEXT.md glossary with canonical terms and explicitly avoided synonyms, updated inline as terms are resolved. - Architectural Decision Records: Creates lightweight ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Multi-Context Support: Handles both single-context repos (one root CONTEXT.md) and multi-context repos via a CONTEXT-MAP.md that maps bounded contexts and their relationships. - Use Case: While designing an ordering system, the user says "account" ambiguously. The Skill challenges the term, distinguishes Customer from User, updates CONTEXT.md immediately, and offers an ADR when the team decides contexts communicate via domain events instead of synchronous HTTP. ## Quick Start Ask the agent to help define the domain language for your project and record any significant architectural decisions as ADRs.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema
How do I create a ubiquitous language glossary for my project?▼

Create a CONTEXT.md file at the repo root defining each domain term in one or two sentences, with avoided synonyms listed under an _Avoid_ line. Update it inline whenever a term is resolved during design discussions rather than batching changes.

When should I write an architectural decision record?▼

Write an ADR only when all three conditions hold: the decision is hard to reverse, it is surprising without context, and it resulted from a real trade-off between genuine alternatives. Skip ADRs for easily reversed or obvious decisions.

How do I handle multiple bounded contexts in one repository?▼

Create a CONTEXT-MAP.md at the repo root listing each context, where it lives, and how contexts relate to each other. Each context gets its own CONTEXT.md and can have its own docs/adr/ directory for context-specific decisions.

What format should an ADR follow?▼

ADRs live in docs/adr/ with sequential numbering like 0001-slug.md. The minimal format is a title plus one to three sentences covering context, decision, and rationale; optional sections like Status or Considered Options are added only when they add genuine value.

What are the limitations of a CONTEXT.md glossary?▼

CONTEXT.md is strictly a glossary and must not contain implementation details, specs, or scratch notes. It should only include terms specific to the project's domain, not general programming concepts like timeouts or error types.

Related Skills

Explore More Software Engineering Skills→
ishandutta2007ishandutta2007
13

Skill: Grill with Docs

Stress-test plans against CONTEXT.md terminology and ADR decisions.

Community
Intermediate
a35506322a35506322

grill-with-docs

Stress-test project plans against domain documentation, codebase, and ADRs.

Community
Intermediate
AvistianAvistian

domain-modeling

Build and maintain project glossaries and architectural decision records during design sessions.

Community
Intermediate
taiyousan15taiyousan15

sdd-event-storming

Guide Event Storming workshops and generate Markdown domain reports.

Community
Advanced