Agent skill

Domain Modeling

Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts.

MITAuto-check passedDevelopment

Install Domain Modeling

skills CLI

$ npx skills add iurysza/module-graph --skill domain-modeling -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph domain-modeling --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/domain-modeling .claude/skills/domain-modeling && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "domain-modeling" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/domain-modeling into .claude/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/iurysza/module-graph/tree/main/.agents/skills/domain-modeling

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add iurysza/module-graph --skill domain-modeling -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph domain-modeling --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/domain-modeling .agents/skills/domain-modeling && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "domain-modeling" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/domain-modeling into .agents/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iurysza/module-graph --skill domain-modeling -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph domain-modeling --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/domain-modeling .cursor/skills/domain-modeling && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "domain-modeling" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/domain-modeling into .cursor/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/iurysza/module-graph.git --path .agents/skills/domain-modeling

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add iurysza/module-graph --skill domain-modeling -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph domain-modeling --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/domain-modeling .gemini/skills/domain-modeling && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "domain-modeling" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/domain-modeling into .gemini/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install iurysza/module-graph domain-modeling

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add iurysza/module-graph --skill domain-modeling -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/domain-modeling .github/skills/domain-modeling && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "domain-modeling" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/domain-modeling into .github/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iurysza/module-graph --skill domain-modeling -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install iurysza/module-graph domain-modeling --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/domain-modeling .opencode/skills/domain-modeling && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "domain-modeling" agent skill from https://github.com/iurysza/module-graph/tree/main/.agents/skills/domain-modeling into .opencode/skills/domain-modeling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "domain-modeling", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: domain-modeling
GitHub stars: 419
Token cost: ~1.2k tokens
SKILL.md length: 523 words
Files: 3
Skills in repo: 16
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts.

Works in 3 steps: Hard to reverse—the cost of changing the… → Surprising without context—a future… → The result of a real trade-off—genuine…
Clarifying terminology
SKILL.md covers Artifact home, File structure and During the session
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Domain Modeling is an agent skill from iurysza/module-graph. Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts. Use when clarifying terminology, bounded contexts, or durable design decisions.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `ADR-FORMAT.md` and `CONTEXT-FORMAT.md`).

It sits in Development, covering Domain-driven design, Architecture decision records and Diagrams. The repository describes itself as: A Gradle Plugin for visualizing your project's structure, powered by mermaidjs. The licence is MIT.

When your agent uses it

Clarifying terminology
Bounded contexts
Durable design decisions

Example prompts

“Use the domain-modeling skill to maintain project domain language, context maps, diagrams, and architectural decisions under ai-artifacts”
“/domain-modeling”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Hard to reverse—the cost of changing the decision later is meaningful.
Surprising without context—a future reader will wonder why it was done this way.
The result of a real trade-off—genuine alternatives existed and one was chosen for specific reasons.

What it can do on your machine

Read from SKILL.md and the folder at commit 15b0135. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Domain Modeling loads about 1.2k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 523 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~51
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from iurysza/module-graph at commit 15b0135, republished under its MIT licence (© iurysza). 523 words, ~1,165 tokens.

Download SKILL.mdSave it as .claude/skills/domain-modeling/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: domain-modeling
description: Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts. Use when clarifying terminology, bounded contexts, or durable design decisions.
metadata.category: planning-architecture

Domain Modeling

Actively build and sharpen the project's domain model as you design. This is the active discipline—challenging terms, inventing edge-case scenarios, visualizing relationships, and writing the glossary and decisions down when they crystallize. Merely reading ai-artifacts/CONTEXT.md for vocabulary is not this skill; this skill is for changing the model, not just consuming it.

Artifact home

Keep agent-authored project knowledge under ai-artifacts/. This includes context glossaries, context maps, ADRs, plans, specs, analyses, reports, reviews, and other Markdown primarily created for or by an LLM.

Use another location only when the user or repository explicitly requires it, such as a human-facing README.md or established product documentation. Do not relocate existing documentation unless asked.

Embed ASCII or Mermaid diagrams directly in the Markdown they explain. Do not create standalone diagram files.

File structure

Most repositories have a single context:

text

/
├── ai-artifacts/
│   ├── CONTEXT.md
│   └── docs/
│       └── adr/
│           ├── 0001-event-sourced-orders.md
│           └── 0002-postgres-for-write-model.md
└── src/

If ai-artifacts/CONTEXT-MAP.md exists, the repository has multiple contexts:

text

/
├── ai-artifacts/
│   ├── CONTEXT-MAP.md
│   ├── docs/
│   │   └── adr/                      ← system-wide decisions
│   └── src/
│       ├── ordering/
│       │   ├── CONTEXT.md
│       │   └── docs/adr/             ← context-specific decisions
│       └── billing/
│           ├── CONTEXT.md
│           └── docs/adr/
└── src/                              ← application source code

ai-artifacts/src/ mirrors the source tree only to make context ownership obvious. Application code remains in the repository's real source directories.

Create files lazily—only when there is something worth recording. Create ai-artifacts/CONTEXT.md when the first term is resolved. Create an ADR directory when the first qualifying decision is made. Create ai-artifacts/CONTEXT-MAP.md only when the project has multiple genuine contexts.

During the session

Challenge against the glossary

When the user uses a term that conflicts with the relevant CONTEXT.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y—which is it?"

Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account'—do you mean the Customer or the User? Those are different things."

Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about boundaries between concepts.

Show full SKILL.md (222 more words)Show less

Cross-reference with code

When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible—which is right?"

Visualize the model

Include an embedded diagram when boundaries, relationships, states, or flows are easier to understand visually.

Use Mermaid for graphs, state transitions, sequences, and multi-context relationships.
Use ASCII art for small structures or when plain-text portability matters more.
Use domain terms from the glossary.
Show the domain model, not classes, framework components, or incidental infrastructure.
Keep the diagram beside the prose it clarifies.

Update context artifacts inline

When a term or relationship is resolved, update the relevant file under ai-artifacts/ immediately. Do not batch resolved domain knowledge. Use CONTEXT-FORMAT.md.

A CONTEXT.md is a glossary, not a spec, scratch pad, or implementation guide. Its diagrams may show conceptual relationships, boundaries, and states, but must not contain implementation details.

Offer ADRs sparingly

Only offer to create an ADR when all three are true:

Hard to reverse—the cost of changing the decision later is meaningful.
Surprising without context—a future reader will wonder why it was done this way.
The result of a real trade-off—genuine alternatives existed and one was chosen for specific reasons.

If any condition is missing, skip the ADR. Use ADR-FORMAT.md.

Files

SKILL.md and 2 other files in .agents/skills/domain-modeling of iurysza/module-graph.

SKILL.md
ADR-FORMAT.md
CONTEXT-FORMAT.md

Open the folder on GitHubat commit 15b0135

Compare with similar skills

Domain Modeling next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Domain Modeling compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Domain Modeling this skilliurysza/module-graph	419	—	~1.2k	Automated safety check: Pass	MIT	yesterday
Evolutionary Modular Architecturetech-leads-club/agent-skills	7k	—	~3.7k	Automated safety check: Pass	CC-BY-4.0	18 days ago
Domain Modelingbrim-borium/spotify_sdk	166	5 repos	~806	Automated safety check: Pass	Apache-2.0	2 days ago
Design Doc MermaidSpillwaveSolutions/design-doc-mermaid	175	1 repos	~5.6k	Automated safety check: Pass	None	1 mo ago
Domain Modelingvinvcn/mattpocock-skills-zh-CN	4.7k	—	~505	Automated safety check: Pass	MIT	10 days ago
Opencharttryopendata/skills	142	—	~11k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Evolutionary Modular Architecture
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
7k GitHub stars~3.7k tokensUpdated 18 days ago
DevelopmentAuto-check passed
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
166 GitHub starsUsed in 5 repos~806 tokens
DevelopmentAuto-check passed
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
175 GitHub starsUsed in 1 repo~5.6k tokens
DevelopmentAuto-check passed
Domain Modeling
vinvcn/mattpocock-skills-zh-CN
构建并打磨项目的领域模型。适用于讨论 codebase 术语、编写或编辑 CONTEXT.md，或记录或编辑 ADR. An agent skill from vinvcn/mattpocock-skills-zh-CN.
4.7k GitHub stars~505 tokensUpdated 10 days ago
DevelopmentAuto-check passed
Openchart
tryopendata/skills
Generates OpenChart (https://github.com/tryopendata/openchart) chart, table, graph, sankey, tilemap, and geo map specs from data, and guides editorial design decisions.
142 GitHub stars~11k tokensUpdated 2 mo ago
DevelopmentAuto-check passed
Architecture Decisions and ADRs
first-fluke/oh-my-agent
Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.
1.3k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed

Questions about Domain Modeling

What does Domain Modeling do?

Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts. Domain Modeling is an agent skill from iurysza/module-graph. Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts.

When should I use Domain Modeling?

Domain Modeling fits situations like: clarifying terminology; bounded contexts; durable design decisions.

How do I install Domain Modeling in Claude Code?

Run `npx skills add iurysza/module-graph --skill domain-modeling -a claude-code`. Or copy the skill folder (.agents/skills/domain-modeling in iurysza/module-graph) into .claude/skills/domain-modeling in your project. Claude Code loads it when a task matches its description.

How do I install Domain Modeling in Codex?

Run `npx skills add iurysza/module-graph --skill domain-modeling -a codex`. Or copy the skill folder (.agents/skills/domain-modeling in iurysza/module-graph) into .agents/skills/domain-modeling in your project. Codex loads it when a task matches its description.

Can I use Domain Modeling in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iurysza/module-graph --skill domain-modeling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/domain-modeling, .gemini/skills/domain-modeling, .github/skills/domain-modeling and .opencode/skills/domain-modeling in your project.

What does Domain Modeling need to run?

SKILL.md names no scripts, command-line tools or credentials: Domain Modeling is instructions for the agent only.

Does Domain Modeling access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Domain Modeling safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Domain Modeling use?

Domain Modeling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Domain Modeling use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Domain Modeling?

Skills that share tags, products or a category with Domain Modeling: Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars), Domain Modeling (brim-borium/spotify_sdk, 166 stars), Design Doc Mermaid (SpillwaveSolutions/design-doc-mermaid, 175 stars) and Domain Modeling (vinvcn/mattpocock-skills-zh-CN, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Domain Modeling?

iurysza (a GitHub user) maintains it in iurysza/module-graph, which has 419 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 7, 2026.

Source: iurysza/module-graph on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Domain Modeling

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Domain Modeling

Artifact home

File structure

During the session

Challenge against the glossary

Sharpen fuzzy language

Discuss concrete scenarios

Cross-reference with code

Visualize the model

Update context artifacts inline

Offer ADRs sparingly

Files

Compare with similar skills

Similar skills

More from iurysza/module-graph

Related

Questions about Domain Modeling