Build and maintain project domain glossaries and architectural decision records.
npx skills add https://github.com/wenyue/SmartKit --skill domain-modeling-wenyue
Please help me install this Agent Skill. Skill: domain-modeling Source: https://github.com/wenyue/SmartKit/tree/main/skills/domain-modeling Command: npx skills add https://github.com/wenyue/SmartKit --skill domain-modeling-wenyue
CONTEXT.md glossary that pins down canonical domain terms, flags conflicting usage, and lists words to avoid. - 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 linking per-context glossaries and ADRs. - Use Case: While designing a billing feature, the user says "account" ambiguously; the skill challenges the term, resolves it to "Customer", updates CONTEXT.md inline, and offers an ADR when the team picks event-based communication between Ordering and Billing. ## Quick Start Ask the assistant to use the domain-modeling skill to sharpen the domain language and record architectural decisions for your project.High-intent search queries and answers about installing and using this skill.
Create a CONTEXT.md file at the repo root listing canonical domain terms with one or two sentence definitions and words to avoid. Update it inline whenever a term is resolved during design discussions, keeping it free of implementation details.
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. If any condition is missing, skip the ADR.
Place a CONTEXT-MAP.md at the repo root listing each context, its location, and its relationships with other contexts. Each context keeps its own CONTEXT.md glossary and context-specific docs/adr directory for local decisions.
A glossary contains only terms specific to the project's domain with tight definitions of what each term is. General programming concepts, implementation details, and design decisions do not belong in CONTEXT.md.
An ADR is a sequentially numbered Markdown file in docs/adr containing 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 genuine value.
DoubleslashSEExtract domain models, business rules, and data flows from existing codebases.
stacksjsBuilds and sharpens a Stacks project's domain language through CONTEXT.md glossaries and ADRs.
a35506322Stress-test project plans against domain documentation, codebase, and ADRs.
taiyousan15Guide Event Storming workshops and generate Markdown domain reports.