skills.rest
pd-phuc
pd-phucCOMMUNITY
Explore all skills by this author →
GitHub

domain-modeling

Build and maintain project domain glossaries and architectural decision records.

Updated Aug 5, 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/pd-phuc/laravel-template --skill domain-modeling-pd-phuc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/pd-phuc/laravel-template/tree/main/.claude/skills/domain-modeling
Command: npx skills add https://github.com/pd-phuc/laravel-template --skill domain-modeling-pd-phuc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose track of domain terminology and the reasoning behind architectural choices, leading to inconsistent language in code and repeated debates about settled decisions. This Skill actively builds a ubiquitous language glossary (CONTEXT.md) and records architectural decision records (ADRs) as they crystallize during design discussions. ## Core Features & Use Cases - Ubiquitous Language Management: Challenges conflicting or fuzzy terms, proposes canonical vocabulary, and updates CONTEXT.md inline with opinionated definitions and avoided synonyms. - Architectural Decision Records: Offers ADRs only when decisions are hard to reverse, surprising without context, and the result of real trade-offs, using a minimal numbered format in docs/adr/. - Multi-Context Support: Handles single-context repos with one CONTEXT.md or multi-context repos via a CONTEXT-MAP.md describing bounded contexts and their relationships. - Use Case: While designing an ordering system, the user says "account" ambiguously; the Skill asks whether they mean Customer or User, records the resolved term in CONTEXT.md, and drafts an ADR when the team picks event-sourced orders over a CRUD model. ## Quick Start Ask the AI to help define the domain terminology for your project and record the key 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 listing domain terms with one-to-two sentence definitions and avoided synonyms. Update it inline whenever a term is resolved during design discussions, keeping it free of implementation details.

When should I write an architectural decision record?▼

Write an ADR only when a decision is hard to reverse, surprising without context, and the result of a genuine trade-off between alternatives. Skip ADRs for easily reversible or obvious choices to avoid documentation noise.

What format should an ADR use?▼

ADRs live in docs/adr/ with sequential numbering like 0001-slug.md. A minimal ADR 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 value.

How do I handle domain language across multiple bounded contexts?▼

Use a CONTEXT-MAP.md at the repo root listing each context, its location, and its relationships, with a separate CONTEXT.md per context. The map records integration patterns such as domain events or shared types between contexts.

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

CONTEXT.md is a glossary only 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→
nikbrunnernikbrunner

dev-util-glossary

Extract and formalize domain terminology from conversations into GLOSSARY.md.

Community
Intermediate
slussetslusset
1

domain-modeling

Translate user stories into a formal domain model with entities, value objects, and state machines.

Community
Advanced
meirmmeirm
29

validating-business-logic-against-code

Map documented business rules to code evidence and categorize their implementation status.

Community
Advanced
cameronraysmithcameronraysmith
14

preferences-collaborative-modeling

Facilitate EventStorming, Domain Storytelling, and Example Mapping workshops to surface domain structure.

Community
Advanced