Builds and maintains project domain glossaries and architecture decision records.
npx skills add https://github.com/Suge8/skills --skill domain-modeling-suge8
Please help me install this Agent Skill. Skill: domain-modeling Source: https://github.com/Suge8/skills/tree/main/workflow/domain-modeling Command: npx skills add https://github.com/Suge8/skills --skill domain-modeling-suge8
High-intent search queries and answers about installing and using this skill.
Maintain a CONTEXT.md file at the repository root that defines each domain term in one or two sentences and lists synonyms to avoid. Update it inline as terms are resolved during design discussions rather than batching changes.
Write an ADR only when three conditions hold: the decision is hard to reverse, it would surprise a future reader without context, and it came from a genuine trade-off between alternatives. Skip ADRs for easily reversible or obvious choices.
Create a CONTEXT-MAP.md at the repository root listing each context, its location, and its relationships such as published events or shared types. Each context then keeps its own CONTEXT.md glossary and context-specific docs/adr/ directory.
An ADR is a sequentially numbered Markdown file in docs/adr/ with a short title and one to three sentences covering context, decision, and rationale. Optional sections like status, considered options, and consequences are added only when they add real value.
No. CONTEXT.md is strictly a glossary of domain terms and should contain no implementation details, specifications, or design decisions. Those belong in ADRs or other documentation, keeping the glossary focused on language only.
StChiotisExtract domain knowledge from interviews into documentation files.
MDSIXONEBuild and maintain project domain glossaries and architectural decision records.
camercuValidates plans against project domain language and updates CONTEXT.md and ADRs inline.
taiyousan15Guide Event Storming workshops and generate Markdown domain reports.
