Mmcp.market

domain-modeling skill

by rohitg00·rohitg00/pro-workflow·2.9k stars

Build the project's shared language and bounded contexts before writing code, so names stay consistent and the agent stops paraphrasing domain concepts. Produces a CONTEXT.md glossary and decision records. Use at the start of a project or feature, or when the codebase and the people describing it speak different languages.

A100/100content scan

Is the domain-modeling skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the domain-modeling skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/rohitg00/pro-workflow.git /tmp/pro-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/pro-workflow/skills/domain-modeling ~/.claude/skills/domain-modeling
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

domain-modeling

Most misbuilds start as a language gap: the agent is dropped into a project and left to infer the jargon, so it uses twenty words where the domain has one. A shared language closes the gap. When code, conversation, and the model all draw from the same vocabulary, names line up, navigation gets cheaper, and the model spends fewer tokens reasoning because it has a tighter language to reason in.

Method

words, list the nouns and verbs that carry domain meaning - the concepts a newcomer would have to ask about. Prefer the user's word over a synonym you like better.

  1. Harvest the terms. From the request, the codebase, and the user's own

not a dictionary definition. If two terms blur together, force the distinction or collapse them - ambiguity here becomes inconsistent names in code.

  1. Pin each one. Write a one-line definition in the project's own language,

different parts of the system, that is a boundary. Name each context and note which terms belong to it. A term that means two things is two terms.

  1. Draw the boundaries. Where the same word means different things in

questioned later, write a short decision record: context, choice, alternatives rejected, why.

  1. Record the hard calls. When a modeling choice was contested or will be

Outputs

term - what it means in this project. Grouped by bounded context when there is more than one. Point every future session at this file. On re-run, add new terms and update definitions that changed; do not rewrite the file wholesale.

  • CONTEXT.md - the shared-language glossary. One term per line:

short enough to read in fifteen seconds.

  • Bounded-context sketch - the contexts and which terms live in each,

modeling calls only. Read the directory first and number from the highest existing record so two records never collide. Skip the obvious ones.

  • Decision records in docs/decisions/NNNN-slug.md for the contested

Guardrails

not framed on a wall.

  • The glossary is for the model as much as the human - write it to be loaded,

rename it.

  • Do not invent terms the project does not use. Reflect the domain; do not

nothing is worse than none. Prune terms that fall out of use.

  • Keep it small and current. A glossary that lists everything and updates

Where it fits

Run this before plan-interrogate on a new area, or let plan-interrogate call back here when it hits terms it cannot pin. The CONTEXT.md this produces is the same file plan-interrogate emits - one shared-language artifact, two ways in.

More skills from rohitg00/pro-workflow

  • Aagent-teamsCoordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
  • Aauto-setupAuto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
  • Abatch-orchestrationDecompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
  • Cbug-captureCapture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
  • Acompact-guardSmart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
  • Acontext-engineeringMaster the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
  • Acontext-optimizerOptimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.
  • Acost-trackerTrack session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.
  • Adesign-engineeringApply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an animation", "polish the UI", "review this component".
  • AdeslopRemove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
  • Afile-watcherConfigure file watching hooks to auto-react to config changes, env file updates, and dependency modifications. Use to set up reactive workflows.
  • Aimprove-architectureAudit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture.

All agent skills → · MCP servers