Develop domain terminology and maintain Architecture Decision Records (ADRs).
npx skills add https://github.com/voidrot/agents --skill domain-modeling-voidrot
Please help me install this Agent Skill. Skill: domain-modeling Source: https://github.com/voidrot/agents/tree/main/skills/meta/domain-modeling Command: npx skills add https://github.com/voidrot/agents --skill domain-modeling-voidrot
This Skill aids in refining project domain terminology, maintaining a glossary, resolving overloaded concepts, and documenting architecture decisions as Architecture Decision Records (ADRs).
Use the domain-modeling skill to define a new term for the project context in the 'CONTEXT.md' file.
High-intent search queries and answers about installing and using this skill.
To document architecture decisions, you create and maintain Architecture Decision Records (ADRs) that capture technical choices, rationale, and consequences. This ensures clarity and consistency across your project by providing a structured rationale recording mechanism.
Domain modeling is the process of developing and refining project-specific terminology to resolve overloaded concepts. You need it when domain language becomes ambiguous, requiring a glossary to establish consistent terms across technical teams.
To define a new term, you edit the glossary files, specifically adding your project context definitions to the 'CONTEXT.md' file. This action clarifies terminology and maintains the domain language for your technical project.
Yes, you can use domain modeling to resolve overloaded concepts by maintaining a project glossary. It aids in refining project domain terminology, ensuring that ambiguous terms are clarified and consistently applied across the architecture.
The best way to maintain ADRs and a glossary is to integrate domain modeling into your design decisions, editing both ADR and glossary files consistently. This records choices and rationale while simultaneously clarifying overloaded terminology.
silaslopes100Convert raw product ideation data into structured user personas and customer journey maps.
bacocoTranslate approved product requirements into structured architecture design documents.
nselugaCollaboratively define and standardize project domain terminology and record architectural decisions.
dgkngkAnalyze requirements, evaluate trade-offs, and document architectural decisions with ADRs.
