Domain Modeling
fossasia/eventyay-interpretation
Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.
Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
Install Implementing Domain Driven Design
$ npx skills add ciembor/agent-rules-books --skill implementing-domain-driven-design -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ciembor/agent-rules-books implementing-domain-driven-design --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ciembor/agent-rules-books.git skills-src && mkdir -p .claude/skills && cp -r skills-src/implementing-domain-driven-design .claude/skills/implementing-domain-driven-design && rm -rf skills-srcUse ~/.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/
Install the "implementing-domain-driven-design" agent skill from https://github.com/ciembor/agent-rules-books/tree/main/implementing-domain-driven-design into .claude/skills/implementing-domain-driven-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-domain-driven-design", 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 install https://github.com/ciembor/agent-rules-books/tree/main/implementing-domain-driven-designType 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.
$ npx skills add ciembor/agent-rules-books --skill implementing-domain-driven-design -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ciembor/agent-rules-books implementing-domain-driven-design --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ciembor/agent-rules-books.git skills-src && mkdir -p .agents/skills && cp -r skills-src/implementing-domain-driven-design .agents/skills/implementing-domain-driven-design && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "implementing-domain-driven-design" agent skill from https://github.com/ciembor/agent-rules-books/tree/main/implementing-domain-driven-design into .agents/skills/implementing-domain-driven-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-domain-driven-design", 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.
$ npx skills add ciembor/agent-rules-books --skill implementing-domain-driven-design -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ciembor/agent-rules-books implementing-domain-driven-design --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ciembor/agent-rules-books.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/implementing-domain-driven-design .cursor/skills/implementing-domain-driven-design && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "implementing-domain-driven-design" agent skill from https://github.com/ciembor/agent-rules-books/tree/main/implementing-domain-driven-design into .cursor/skills/implementing-domain-driven-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-domain-driven-design", 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 https://github.com/ciembor/agent-rules-books.git --path implementing-domain-driven-design--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ciembor/agent-rules-books --skill implementing-domain-driven-design -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ciembor/agent-rules-books implementing-domain-driven-design --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ciembor/agent-rules-books.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/implementing-domain-driven-design .gemini/skills/implementing-domain-driven-design && rm -rf skills-srcUse ~/.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/
Install the "implementing-domain-driven-design" agent skill from https://github.com/ciembor/agent-rules-books/tree/main/implementing-domain-driven-design into .gemini/skills/implementing-domain-driven-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-domain-driven-design", 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.
$ gh skill install ciembor/agent-rules-books implementing-domain-driven-designInstalls 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).
$ npx skills add ciembor/agent-rules-books --skill implementing-domain-driven-design -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ciembor/agent-rules-books.git skills-src && mkdir -p .github/skills && cp -r skills-src/implementing-domain-driven-design .github/skills/implementing-domain-driven-design && rm -rf skills-srcUse ~/.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/
Install the "implementing-domain-driven-design" agent skill from https://github.com/ciembor/agent-rules-books/tree/main/implementing-domain-driven-design into .github/skills/implementing-domain-driven-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-domain-driven-design", 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.
$ npx skills add ciembor/agent-rules-books --skill implementing-domain-driven-design -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ciembor/agent-rules-books implementing-domain-driven-design --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ciembor/agent-rules-books.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/implementing-domain-driven-design .opencode/skills/implementing-domain-driven-design && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "implementing-domain-driven-design" agent skill from https://github.com/ciembor/agent-rules-books/tree/main/implementing-domain-driven-design into .opencode/skills/implementing-domain-driven-design/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementing-domain-driven-design", 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
implementing-domain-driven-design- GitHub stars
- 2.9k
- Token cost
- ~201 tokens
- SKILL.md length
- 57 words
- Files
- 4
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
- Tasks that involve Domain-driven design
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Implementing Domain Driven Design is an agent skill from ciembor/agent-rules-books. Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
Its SKILL.md is about 200 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `implementing-domain-driven-design.md`, `implementing-domain-driven-design.mini.md` and `implementing-domain-driven-design.nano.md`).
It sits in Development, covering Domain-driven design. The repository describes itself as: AGENTS.md rules / skills for AI coding agents: Codex, Cursor & Claude Code. Inspired by Clean Code, Refactoring, DDD, Clean Architecture and DDIA programming books. The licence is MIT.
When your agent uses it
- Tasks that involve Domain-driven design
Example prompts
- “/implementing-domain-driven-design”
What it can do on your machine
Read from SKILL.md and the folder at commit 893a88a. 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
Implementing Domain Driven Design loads about 201 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 57 words of instructions outside code blocks.
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 ciembor/agent-rules-books at commit 893a88a, republished under its MIT licence (© ciembor). 57 words, ~201 tokens.
Download SKILL.mdSave it as
.claude/skills/implementing-domain-driven-design/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- implementing-domain-driven-design
- description
- Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
- license
- MIT
Implementing Domain-Driven Design Skill
Use this skill when a task involves implementing DDD in code: aggregate boundaries, invariants, repositories, domain events, application services, modules, factories, or bounded-context integration.
Before making design or code decisions, read and apply implementing-domain-driven-design.mini.md. Use implementing-domain-driven-design.md only as a deeper reference when the mini rules are not enough for the current implementation tradeoff.
© ciembor, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files in implementing-domain-driven-design of ciembor/agent-rules-books.
- SKILL.md
- implementing-domain-driven-design.md
- implementing-domain-driven-design.mini.md
- implementing-domain-driven-design.nano.md
Open the folder on GitHubat commit 893a88a
Compare with similar skills
Implementing Domain Driven Design 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Implementing Domain Driven Design this skillciembor/agent-rules-books | 2.9k | — | ~201 | Automated safety check: Pass | MIT | |
| Domain Modelingfossasia/eventyay-interpretation | 1.6k | 31 repos | ~821 | Automated safety check: Pass | Apache-2.0 | |
| Architecture Governancezai-org/ZCode | 7.5k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Evolutionary Modular Architecturetech-leads-club/agent-skills | 7k | — | ~3.7k | Automated safety check: Pass | CC-BY-4.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Domain Modeling and Glossarywindmill-labs/windmill | 18k | — | ~622 | Automated safety check: Pass | Custom licence |
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.
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.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
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.
Ddd
swamp-club/swamp
Domain Driven Design guidance for TypeScript/Deno codebases.
More from ciembor/agent-rules-books
All 14 skills in this repoPatterns of Enterprise Application Architecture
ciembor/agent-rules-books
Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or…
A Philosophy of Software Design
ciembor/agent-rules-books
Apply John Ousterhout-inspired software design rules when reducing complexity, designing module boundaries, or reviewing APIs and abstractions.
Clean Architecture Rules
ciembor/agent-rules-books
Apply Robert C. Martin-inspired architecture rules when separating business policy from frameworks, databases, UI, or infrastructure details.
Clean Code Rules
ciembor/agent-rules-books
Apply Robert C. Martin-inspired clean code rules when improving readability, naming, function design, responsibilities, or testable everyday code.
Code Complete Construction Rules
ciembor/agent-rules-books
Apply Steve McConnell-inspired construction rules when implementing routines, variables, classes, control flow, defensive code, or tests.
Data-Intensive Design Rules
ciembor/agent-rules-books
Apply Martin Kleppmann-inspired data-system rules when designing reliability, scalability, consistency, replication, transactions, streams, or schema evolution.
Related
Categories
Questions about Implementing Domain Driven Design
What does Implementing Domain Driven Design do?
Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations. Implementing Domain Driven Design is an agent skill from ciembor/agent-rules-books. Apply Vaughn Vernon-inspired implementation DDD rules when building aggregates, domain events, repositories, application services, or context integrations.
When should I use Implementing Domain Driven Design?
Implementing Domain Driven Design fits situations like: tasks that involve Domain-driven design.
How do I install Implementing Domain Driven Design in Claude Code?
Run `npx skills add ciembor/agent-rules-books --skill implementing-domain-driven-design -a claude-code`. Or copy the skill folder (implementing-domain-driven-design in ciembor/agent-rules-books) into .claude/skills/implementing-domain-driven-design in your project. Claude Code loads it when a task matches its description.
How do I install Implementing Domain Driven Design in Codex?
Run `npx skills add ciembor/agent-rules-books --skill implementing-domain-driven-design -a codex`. Or copy the skill folder (implementing-domain-driven-design in ciembor/agent-rules-books) into .agents/skills/implementing-domain-driven-design in your project. Codex loads it when a task matches its description.
Can I use Implementing Domain Driven Design 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 ciembor/agent-rules-books --skill implementing-domain-driven-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/implementing-domain-driven-design, .gemini/skills/implementing-domain-driven-design, .github/skills/implementing-domain-driven-design and .opencode/skills/implementing-domain-driven-design in your project.
What does Implementing Domain Driven Design need to run?
SKILL.md names no scripts, command-line tools or credentials: Implementing Domain Driven Design is instructions for the agent only.
Does Implementing Domain Driven Design 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 Implementing Domain Driven Design 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 Implementing Domain Driven Design use?
Implementing Domain Driven Design is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Implementing Domain Driven Design use?
About 201 tokens (SKILL.md is roughly 804 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 Implementing Domain Driven Design?
Skills that share tags, products or a category with Implementing Domain Driven Design: Domain Modeling (fossasia/eventyay-interpretation, 1.6k stars), Architecture Governance (zai-org/ZCode, 7.5k stars), Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementing Domain Driven Design?
ciembor (a GitHub user) maintains it in ciembor/agent-rules-books, which has 2,927 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 10, 2026.
Source: ciembor/agent-rules-books on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.