domain-modeling

Develop domain terminology and maintain Architecture Decision Records (ADRs).

Updated Jul 7, 2026

Search Tags:#domain modeling #glossary #terminology #decision documentation #architecture decision records

Ready to run

npx skills add https://github.com/voidrot/agents --skill domain-modeling-voidrot

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill aids in refining project domain terminology, maintaining a glossary, resolving overloaded concepts, and documenting architecture decisions as Architecture Decision Records (ADRs).

Core Features & Use Cases

Domain Language Development: Build and clarify project-specific terminology.
Architecture Decision Documentation: Create and maintain ADRs for significant technical decisions.
Use Case: Utilize this Skill during design decisions to document architecture choices, rationale, and consequences, ensuring clarity and consistency across the project.

Quick Start

Use the domain-modeling skill to define a new term for the project context in the 'CONTEXT.md' file.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

How do I document architecture decisions and record technical rationale for my project?▼

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.

What is domain modeling and when do I need to build a project glossary?▼

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.

How do I define a new domain term and add it to the project glossary?▼

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.

Can I use this approach to resolve overloaded concepts in software engineering?▼

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.

What is the best way to maintain Architecture Decision Records alongside a terminology glossary?▼

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.