domain-modeling

Maintain a CONTEXT.md glossary to standardize project terminology.

3|Updated Apr 1, 2026

Search Tags:#documentation #vocabulary #glossary #terminology #domain-modeling #CONTEXT.md

Ready to run

npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill domain-modeling-vtgiang-dotcom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/vtgiang-dotcom/Solo-Code-Harness/tree/main/.gemini/antigravity/skills/domain-modeling
Command: npx skills add https://github.com/vtgiang-dotcom/Solo-Code-Harness --skill domain-modeling-vtgiang-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain a single source of truth for project vocabulary by anchoring terms in CONTEXT.md, reducing ambiguity and vocabulary drift across code, docs, and conversations.

Core Features & Use Cases

Glossary discipline: define and standardize terms, ensuring every term maps to a precise definition with clear relationships and avoidances.
Onboarding and consistency: streamline onboarding by providing a canonical vocabulary, enabling consistent naming and interpretation across teams.
Domains and naming: handle fuzzy domains, multiple names for the same concept, and the introduction of new modules with a living glossary.

Quick Start

Create or update a CONTEXT.md entry for a new term as soon as it crystallizes.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

How do I maintain a shared glossary to standardize project terminology?▼

To standardize project terminology, maintain a single CONTEXT.md glossary that anchors terms with precise definitions, clear relationships, and flagged ambiguities to resolve naming drift across teams.

What is the best way to resolve domain modeling ambiguities during onboarding?▼

Resolving domain modeling ambiguities during onboarding requires a canonical vocabulary glossary that defines fuzzy terms, standardizes multiple names for the same concept, and clarifies relationships to ensure consistent interpretation.

How do I create a CONTEXT.md file for project vocabulary?▼

Create a CONTEXT.md file by lazily initializing it when a new term crystallizes, structuring entries with language rules, term relationships, and flagged ambiguities to maintain a single source of truth.

When do I need a living glossary for domain shifts and renaming?▼

You need a living glossary for domain shifts when terms are fuzzy, concepts are renamed, or new modules are introduced, ensuring the project vocabulary remains consistent across code, docs, and conversations.

Does domain modeling glossary discipline work without external dependencies?▼

Yes, glossary discipline works without external dependencies by enforcing CONTEXT.md structure internally, relying solely on markdown formatting to document language rules, relationships, and ambiguities.

Why does vocabulary drift happen in cross-team collaboration?▼

Vocabulary drift happens in cross-team collaboration when multiple names describe the same concept without a canonical glossary, causing inconsistent naming and interpretation across code and documentation.