Agent skill

Domain Modeling

by fossasia in fossasia/eventyay-interpretation

Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.

Apache-2.0Auto-check passedDevelopment

Install Domain Modeling

skills CLI

$ npx skills add fossasia/eventyay-interpretation --skill domain-modeling -a claude-code

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

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation 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/fossasia/eventyay-interpretation.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/fossasia/eventyay-interpretation/tree/dev/.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/fossasia/eventyay-interpretation/tree/dev/.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 fossasia/eventyay-interpretation --skill domain-modeling -a codex

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

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation 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/fossasia/eventyay-interpretation.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/fossasia/eventyay-interpretation/tree/dev/.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 fossasia/eventyay-interpretation --skill domain-modeling -a cursor

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

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation 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/fossasia/eventyay-interpretation.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/fossasia/eventyay-interpretation/tree/dev/.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/fossasia/eventyay-interpretation.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 fossasia/eventyay-interpretation --skill domain-modeling -a gemini-cli

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

GitHub CLI

$ gh skill install fossasia/eventyay-interpretation 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/fossasia/eventyay-interpretation.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/fossasia/eventyay-interpretation/tree/dev/.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 fossasia/eventyay-interpretation 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 fossasia/eventyay-interpretation --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/fossasia/eventyay-interpretation.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/fossasia/eventyay-interpretation/tree/dev/.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 fossasia/eventyay-interpretation --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 fossasia/eventyay-interpretation 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/fossasia/eventyay-interpretation.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/fossasia/eventyay-interpretation/tree/dev/.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: 1.6k
Used in: 31 other repos
Token cost: ~821 tokens
SKILL.md length: 400 words
Files: 3
Skills in repo: 38
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.

Works in 3 steps: Hard to reverse — the cost of changing… → Surprising without context — a future… → The result of a real trade-off — there…
The user wants to pin down domain terminology
SKILL.md covers 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 fossasia/eventyay-interpretation. Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

Its SKILL.md is about 820 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. The repository describes itself as: A plugin for live interpretation of video streams. The licence is Apache-2.0.

When your agent uses it

The user wants to pin down domain terminology
A ubiquitous language
Record an architectural decision
Another skill needs to maintain the domain model

Example prompts

“/domain-modeling”

Workflow steps

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

Hard to reverse — the cost of changing your mind later is meaningful
Surprising without context — a future reader will wonder "why did they do it this way?"
The result of a real trade-off — there were genuine alternatives and you picked one for specific reasons

What it can do on your machine

Read from SKILL.md and the folder at commit 1ca0139. 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 821 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 400 words of instructions outside code blocks.

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

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 fossasia/eventyay-interpretation at commit 1ca0139, republished under its Apache-2.0 licence (© fossasia). 400 words, ~821 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: Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

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, and writing the glossary and decisions down the moment they crystallise. (Merely reading CONTEXT.md for vocabulary is not this skill — that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)

File structure

Most repos have a single context:

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

If a CONTEXT-MAP.md exists at the root, the repo has multiple contexts. The map points to where each one lives:

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

Create files lazily — only when you have something to write. If no CONTEXT.md exists, create one when the first term is resolved. If no docs/adr/ exists, create it when the first ADR is needed.

During the session

Challenge against the glossary

When the user uses a term that conflicts with the existing language in 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 the boundaries between concepts.

Show full SKILL.md (171 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?"

Update CONTEXT.md inline

When a term is resolved, update CONTEXT.md right there. Don't batch these up — capture them as they happen. Use the format in CONTEXT-FORMAT.md.

CONTEXT.md should be totally devoid of implementation details. Do not treat CONTEXT.md as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.

Offer ADRs sparingly

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

Hard to reverse — the cost of changing your mind later is meaningful
Surprising without context — a future reader will wonder "why did they do it this way?"
The result of a real trade-off — there were genuine alternatives and you picked one for specific reasons

If any of the three is missing, skip the ADR. Use the format in ADR-FORMAT.md.

Files

SKILL.md and 2 other files in .agents/skills/domain-modeling of fossasia/eventyay-interpretation.

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

Open the folder on GitHubat commit 1ca0139

Used in 32 other repositories

We found 40 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 31 other GitHub owners. This page covers the copy in fossasia/eventyay-interpretation, which our catalogue first saw on October 7, 2026.

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 skillfossasia/eventyay-interpretation	1.6k	31 repos	~821	Automated safety check: Pass	Apache-2.0	4 days ago
Architecture Governancezai-org/ZCode	7.6k	—	~1.2k	Automated safety check: Pass	Apache-2.0	11 days ago
Evolutionary Modular Architecturetech-leads-club/agent-skills	7k	—	~3.7k	Automated safety check: Pass	CC-BY-4.0	yesterday
Domain Modelingbrim-borium/spotify_sdk	166	5 repos	~806	Automated safety check: Pass	Apache-2.0	yesterday
Domain Modeling and Glossarywindmill-labs/windmill	18k	—	~622	Automated safety check: Pass	Custom licence	today
Dddswamp-club/swamp	646	—	~1.4k	Automated safety check: Pass	Custom licence	today

Similar skills

Architecture Governance
zai-org/ZCode
Apply the repository's architecture policy to code changes by generating a bounded context package, checking module and layer boundaries, and reporting baseline-aware violations.
7.6k GitHub stars~1.2k tokensUpdated 11 days ago
DevelopmentAuto-check passed
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 yesterday
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
Domain Modeling and Glossary
windmill-labs/windmill
Actively challenges vague or conflicting terminology as you design, and keeps a living domain glossary file up to date in real time.
18k GitHub stars~622 tokensUpdated today
DevelopmentAuto-check passed
Ddd
swamp-club/swamp
Domain Driven Design guidance for TypeScript/Deno codebases.
646 GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed
Migration Path
AxonIQ/AxonFramework
Create a new Axon Framework 4→5 migration path documentation page.
3.6k GitHub stars~594 tokensUpdated today
DevelopmentAuto-check passed

Questions about Domain Modeling

What does Domain Modeling do?

Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation. Domain Modeling is an agent skill from fossasia/eventyay-interpretation. Build and sharpen a project's domain model.

When should I use Domain Modeling?

Domain Modeling fits situations like: the user wants to pin down domain terminology; A ubiquitous language; record an architectural decision; another skill needs to maintain the domain model.

How do I install Domain Modeling in Claude Code?

Run `npx skills add fossasia/eventyay-interpretation --skill domain-modeling -a claude-code`. Or copy the skill folder (.agents/skills/domain-modeling in fossasia/eventyay-interpretation) 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 fossasia/eventyay-interpretation --skill domain-modeling -a codex`. Or copy the skill folder (.agents/skills/domain-modeling in fossasia/eventyay-interpretation) 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 fossasia/eventyay-interpretation --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 Apache-2.0 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 821 tokens (SKILL.md is roughly 3.3k 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: Architecture Governance (zai-org/ZCode, 7.6k stars), Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars), Domain Modeling (brim-borium/spotify_sdk, 166 stars) and Domain Modeling and Glossary (windmill-labs/windmill, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Domain Modeling?

fossasia (a GitHub organization) maintains it in fossasia/eventyay-interpretation, which has 1,551 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 5, 2026.

Source: fossasia/eventyay-interpretation 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

File structure

During the session

Challenge against the glossary

Sharpen fuzzy language

Discuss concrete scenarios

Cross-reference with code

Update CONTEXT.md inline

Offer ADRs sparingly

Files

Used in 32 other repositories

Compare with similar skills

Similar skills

More from fossasia/eventyay-interpretation

Related

Questions about Domain Modeling