domain-modeling

Define and refine domain models with terminology and architectural decisions.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Lev-it/lev-skills --skill domain-modeling-lev-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-modeling
Source: https://github.com/Lev-it/lev-skills/tree/main/.claude/skills/domain-modeling
Command: npx skills add https://github.com/Lev-it/lev-skills --skill domain-modeling-lev-it

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps in defining and refining the domain model of a project, ensuring clear and consistent terminology and aiding in architectural decision-making.

Core Features & Use Cases

  • Domain Modeling: Collaboratively build and refine the project's domain model.
  • Terminology Clarification: Resolve conflicts and improve the clarity of domain terminology.
  • Architectural Decisions: Record and document architectural decisions with ADRs.
  • Use Case: When starting a new project, use this Skill to establish a solid domain model that will serve as a foundation for the project's development.

Quick Start

Use the domain-modeling skill to create a new context for your project, 'Ordering', and define the key terms and relationships within it.

Frequently Asked Questions about domain-modeling

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

FAQPage Schema
How do I establish a ubiquitous language and refine domain terminology for a new software project?

To establish a ubiquitous language, collaboratively define and refine domain terminology by resolving conflicts and clarifying key terms. This structured approach ensures consistent domain modeling across the project.

What is the best way to document architectural decisions during domain modeling?

The best way to document architectural decisions is by recording them as Architectural Decision Records (ADRs). This ensures that the context and reasoning behind structural choices are clearly captured and maintained.

How do I create a context map for a specific domain like 'Ordering'?

To create a context map, define a new bounded context for your domain, such as 'Ordering', and collaboratively map out the key terms and relationships within that specific domain boundary.

Do I need prior experience in domain-driven design to use this domain modeling approach?

Active collaboration is required to effectively define and refine the domain model. While the approach is structured for precision, having foundational knowledge of domain modeling concepts helps clarify terminology and architectural decisions.

When should I use context mapping versus simply defining a domain model?

Context mapping is used when you need to define relationships and boundaries between multiple domain areas. Simply defining a domain model focuses on establishing the core terminology and foundational structure of a single bounded context.

Why does domain terminology clarification require active collaboration?

Domain terminology clarification requires active collaboration because resolving conflicts and improving clarity demands structured input from all stakeholders. This ensures the resulting ubiquitous language is precise and accurately reflects the domain.