rohitg00/domain-modeling
skills/domain-modeling/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add rohitg00/pro-workflow domain-modelingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 19, 2026, 6:07 AM182.1s1 file scanned
SKILL.md
- name:
- domain-modeling
- description:
- 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.
- user-invocable:
- true
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
- Harvest the terms. From the request, the codebase, and the user's own 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.
- Pin each one. Write a one-line definition in the project's own language, not a dictionary definition. If two terms blur together, force the distinction or collapse them - ambiguity here becomes inconsistent names in code.
- Draw the boundaries. Where the same word means different things in 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.
- Record the hard calls. When a modeling choice was contested or will be questioned later, write a short decision record: context, choice, alternatives rejected, why.
Outputs
CONTEXT.md- the shared-language glossary. One term per line: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.- Bounded-context sketch - the contexts and which terms live in each, short enough to read in fifteen seconds.
- Decision records in
docs/decisions/NNNN-slug.mdfor the contested modeling calls only. Read the directory first and number from the highest existing record so two records never collide. Skip the obvious ones.
Guardrails
- The glossary is for the model as much as the human - write it to be loaded, not framed on a wall.
- Do not invent terms the project does not use. Reflect the domain; do not rename it.
- Keep it small and current. A glossary that lists everything and updates nothing is worse than none. Prune terms that fall out of use.
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.
Related Skills
rohitg00/writing-guidelines
documentation
VerifiedTrustedCommunity
Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy", "draft the docs", "word this error".
2,619SKILL.mdUpdated Jul 19, 2026
rohitg00/tdd
development
VerifiedTrustedCommunity
Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when implementing a feature or fixing a bug where correctness matters and a test can pin the behavior. Says "TDD", "test first", "red green refactor", "write the test first".
2,619SKILL.mdUpdated Jul 19, 2026
rohitg00/skill-router
tools
VerifiedTrustedCommunity
The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow".
2,619SKILL.mdUpdated Jul 19, 2026
rohitg00/improve-architecture
development
VerifiedTrustedCommunity
Audit 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.
2,619SKILL.mdUpdated Jul 19, 2026