Skip to content
Agentmart
Submit a tool

domain-modeling

Use when project terminology or domain boundaries need refinement.

Skill by wayne930242

IndexedMIT★ 2
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/wayne930242-domain-modeling

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when project terminology or domain boundaries need refinement.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/domain-modeling

What's inside

Skill name
domain-modeling
Description
Use when project terminology or domain boundaries need refinement.
License
MIT
Instructions
45 lines in SKILL.md · view on GitHub

Files (3)

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

SKILL.md (first lines)

# Domain Modeling

Actively reconcile the user's language, the project's glossary, and code. Return
confirmed terms and decisions to the caller's artifact, or in the reply when
there is none.

## Discipline

1. Read the applicable `CONTEXT.md`; follow `CONTEXT-MAP.md` when the repository
   has multiple domain contexts.
2. Surface conflicts between the user's term, glossary definition, and code.
   Sharpen vague or overloaded terms into one canonical meaning.
3. Stress-test relationships and boundaries with concrete edge-case scenarios.
4. Check asserted behavior against code. Let the user decide when current code
   and intended domain truth disagree.
5. Record a confirmed term immediately in `CONTEXT.md`, using
   [CONTEXT-FORMAT.md](CONTEXT-FORMAT.md). Keep the glossary
   free of implementation detail.
6. Offer an ADR only when it meets the criteria in
   [ADR-FORMAT.md](ADR-FORMAT.md).

## Carry the model into code

- Use the confirmed ubiquitous language in identifiers, tests, errors, and
  public contracts within its bounded context.
- Keep domain invariants in the domain model. UI, transport, persistence, and
  orchestration layers call the model instead of reimplementing its rules.
- Translate external schemas, persistence records, and another context's
  vocabulary at explicit adapter seams; do not let them become the internal
  domain model by accident.
- Use tactical DDD patterns only when they clarify real domain rules. Reserve
  entities, aggregates, value objects, and repositories for genuine domain concepts.
- Return to Align when implementation reveals a domain
  contradiction. Do not encode an unconfirmed model silently.

Create the glossary or ADR directory only when there is confirmed knowledge to
record. Domain modeling is complete when language, boundaries, invariants,
adapters, code, and tests express the same confirmed model.

---

Adapted from [mattpocock/skills](https://github.com/mattpocock/skills)
`domain-modeling` (MIT License, Copyright (c) 2026 Matt Pocock).

From wayne930242/aaaav, MIT.

More from wayne930242/aaaav

Signals

Stars
2
Forks
1
Open issues
0
Last commit (this folder)
Oct 21, 2026 (8 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from wayne930242

Cite this page

domain-modeling skill. Agent Mart. https://agentmart.dev/skills/wayne930242-domain-modeling (last updated 2026-10-24)