Menu

Individual skill

domain-modeling

Use when pinning down domain terminology, maintaining the domain model, or when a term conflicts or needs sharpening.

.devin/skills/domain-modeling/SKILL.md

Read pinned source

Source commit b0e8ce89a19fac880251dc3ea1babfeb4503a4fe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Sep 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Domain modeling

## Contract

| Field | Bound contract |
|---|---|
| Trigger | Pinning down domain terminology, maintaining the domain model, or a term conflict/sharpening need |
| Authority | Reversible local: writes only the named glossary artifacts, `CONTEXT.md` at the repository root, `CONTEXT-MAP.md`, and per-context `CONTEXT.md` files beside their context source; rollback is version control or undo. No remote mutation. |
| Side effect | Lazily creates or updates `CONTEXT.md` / `CONTEXT-MAP.md` glossaries and per-context `CONTEXT.md` files; no other file, VCS, credential, or remote change. |
| Done | Each resolved term recorded in `CONTEXT.md` with rejected synonyms; glossary stays canonical and implementation-free. |

## Inputs

Required: the term, conflict, or fuzzy usage to resolve from the current design conversation, plus the human ruling when a conflict needs one. Optional: an existing `CONTEXT.md` or `CONTEXT-MAP.md` (absence is normal; files are created lazily) and the implementation source behind a term (when absent or unreadable, skip and report the code cross-check). Scope is limited to terms in the current design work unless the invocation requests a repository-wide glossary sweep.