domain-modeling

Extract entities, attributes, and relationships into a glossary.md and Mermaid ER diagram.

Updated Feb 3, 2026

Search Tags:#domain modeling #vocabulary #glossary #naming conventions #entity-relationship #protected terms

Ready to run

npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill domain-modeling-dhruvinrsoni

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/dhruvinrsoni/agentskills-garden/tree/main/skills/10-discovery/domain-modeling
Command: npx skills add https://github.com/dhruvinrsoni/agentskills-garden --skill domain-modeling-dhruvinrsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill establishes a clear, consistent, and protected vocabulary for your project's domain, preventing naming conflicts and ensuring a shared understanding among all team members and AI agents.

Core Features & Use Cases

Entity & Relationship Mapping: Identifies and defines core concepts and how they relate.
Glossary Creation: Generates a central glossary.md file for all terms.
Protected Terms: Designates critical terms that must never be renamed, ensuring stability.
Use Case: Before starting development, use this Skill to define terms like "Customer," "Order," and "Product," ensuring everyone agrees on their meaning and that "Order" is never accidentally renamed to "Purchase."

Quick Start

Use the domain-modeling skill to extract entities and relationships from the project requirements document.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema

How do I create a domain model glossary from project requirements?▼

Generating a domain model glossary involves extracting entities, attributes, and relationships from project requirements to produce a central `glossary.md` file. This establishes a single source of truth for project vocabulary and prevents naming conflicts.

What are protected terms in domain modeling and why are they important?▼

Protected terms in domain modeling are critical vocabulary words designated as immutable to prevent renaming conflicts. They ensure stability by locking in core concepts so they are never accidentally renamed during development.

Can I generate an entity-relationship diagram from conversation transcripts?▼

Yes, you can generate an entity-relationship diagram from conversation transcripts. The process extracts entities and relationships from the transcripts and outputs a Mermaid ER diagram to visually map your domain model.

What is the best way to establish naming conventions for a software project?▼

The best way to establish naming conventions is to build a canonical domain model that defines core concepts and their relationships. Creating a central glossary ensures all team members and AI agents share a consistent vocabulary.

How do I resolve ambiguous terms in my project domain model?▼

To resolve ambiguous terms in your project domain model, extract and map entities from your requirements to establish a canonical vocabulary. This process addresses ambiguous terms directly and locks in definitions within a shared glossary.

Do I need a domain model before starting software development?▼

You need a domain model before starting software development to ensure all team members agree on core term meanings. Defining terms like "Customer" and "Order" early prevents naming conflicts and establishes a single source of truth.