Domain Modeling
fossasia/eventyay-interpretation
Build and sharpen a project's domain model. An agent skill from fossasia/eventyay-interpretation.
Detailed methodology for DDD (Domain-Driven Design) bounded context identification, context map creation, and event storming execution.
Install Ddd Context Mapping
$ npx skills add revfactory/harness-100 --skill ddd-context-mapping -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 ddd-context-mapping --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/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/ddd-context-mapping .claude/skills/ddd-context-mapping && 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 "ddd-context-mapping" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/ddd-context-mapping into .claude/skills/ddd-context-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ddd-context-mapping", 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/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/ddd-context-mappingType 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 revfactory/harness-100 --skill ddd-context-mapping -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 ddd-context-mapping --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/ddd-context-mapping .agents/skills/ddd-context-mapping && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ddd-context-mapping" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/ddd-context-mapping into .agents/skills/ddd-context-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ddd-context-mapping", 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 revfactory/harness-100 --skill ddd-context-mapping -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 ddd-context-mapping --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/ddd-context-mapping .cursor/skills/ddd-context-mapping && 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 "ddd-context-mapping" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/ddd-context-mapping into .cursor/skills/ddd-context-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ddd-context-mapping", 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/revfactory/harness-100.git --path en/23-microservice-designer/.claude/skills/ddd-context-mapping--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 revfactory/harness-100 --skill ddd-context-mapping -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 ddd-context-mapping --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/ddd-context-mapping .gemini/skills/ddd-context-mapping && 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 "ddd-context-mapping" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/ddd-context-mapping into .gemini/skills/ddd-context-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ddd-context-mapping", 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 revfactory/harness-100 ddd-context-mappingInstalls 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 revfactory/harness-100 --skill ddd-context-mapping -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/ddd-context-mapping .github/skills/ddd-context-mapping && 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 "ddd-context-mapping" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/ddd-context-mapping into .github/skills/ddd-context-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ddd-context-mapping", 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 revfactory/harness-100 --skill ddd-context-mapping -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 ddd-context-mapping --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/23-microservice-designer/.claude/skills/ddd-context-mapping .opencode/skills/ddd-context-mapping && 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 "ddd-context-mapping" agent skill from https://github.com/revfactory/harness-100/tree/main/en/23-microservice-designer/.claude/skills/ddd-context-mapping into .opencode/skills/ddd-context-mapping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ddd-context-mapping", 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
ddd-context-mapping- GitHub stars
- 1.3k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 239 words
- Files
- 1
- Skills in repo
- 464
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Detailed methodology for DDD (Domain-Driven Design) bounded context identification, context map creation, and event storming execution.
- Works in 4 steps: Domain Event Collection → Command -> Event Mapping → Aggregate Identification → …
- Bounded context
- SKILL.md covers Event Storming Procedure, Context Map Relationship Types, Aggregate Design Principles and Ubiquitous Language Dictionary…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ddd Context Mapping is an agent skill from revfactory/harness-100. Detailed methodology for DDD (Domain-Driven Design) bounded context identification, context map creation, and event storming execution. Use this skill for 'bounded context', 'DDD', 'domain modeling', 'event storming', 'context map', 'aggregate design', 'ubiquitous language', and other domain analysis tasks. Enhances the domain analysis capabilities of domain-analyst and service-architect. Note: infrastructure deployment and code implementation are outside the scope of this skill.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Domain-driven design. The licence is Apache-2.0.
When your agent uses it
- Bounded context
- Domain modeling
- Aggregate design
- Ubiquitous language
Example prompts
- “bounded context”
- “domain modeling”
- “event storming”
- “/ddd-context-mapping”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8e8d35c. 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 (its code samples are markdown).
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
Ddd Context Mapping loads about 1.3k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 239 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 revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 239 words, ~1,293 tokens.
Download SKILL.mdSave it as
.claude/skills/ddd-context-mapping/SKILL.md (or your agent's skills folder).- name
- ddd-context-mapping
- description
- Detailed methodology for DDD (Domain-Driven Design) bounded context identification, context map creation, and event storming execution. Use this skill for 'bounded context', 'DDD', 'domain modeling', 'event storming', 'context map', 'aggregate design', 'ubiquitous language', and other domain analysis tasks. Enhances the domain analysis capabilities of domain-analyst and service-architect. Note: infrastructure deployment and code implementation are outside the scope of this skill.
DDD Context Mapping — Domain-Driven Design Context Mapping Guide
Systematic methodology from bounded context identification to context map creation.
Event Storming Procedure
Phase 1: Domain Event Collection
Rule: Express in past tense verbs
Examples: "Order was created", "Payment was approved", "Shipping was initiated"
Collection order:
1. List events from core business flows in chronological order
2. Add exception/failure events
3. Add external system eventsPhase 2: Command -> Event Mapping
[User/System] -> {Command} -> [Aggregate] -> <<Domain Event>>
[Customer] -> {Create Order} -> [Order] -> <<Order was created>>
[Payment System] -> {Approve Payment} -> [Payment] -> <<Payment was approved>>Phase 3: Aggregate Identification
Aggregate boundary criteria:
1. Transactional consistency boundary — groups of objects that must change together
2. Invariant protection — units that enforce business rules
3. Concurrency boundary — units that manage conflicts during concurrent accessPhase 4: Bounded Context Derivation
| Signal | Meaning |
|---|---|
| Same word with different meanings | Context separation needed (e.g., "Account" = user account vs. financial account) |
| Owned by different teams | Organizational boundary = context boundary |
| Different change cadences | Independent deployment needed -> separate |
| Different data stores | Technical boundary = context boundary |
Context Map Relationship Types
| Relationship | Symbol | Description | Example |
|---|---|---|---|
| Shared Kernel | SK | Shared domain model | Two teams using the same Entity |
| Customer-Supplier | C/S | Upstream/downstream relationship | Order (upstream) -> Shipping (downstream) |
| Conformist | CF | Downstream accepts upstream model as-is | Accepting external API model |
| Anti-Corruption Layer | ACL | Insert model translation layer | Integration with legacy system |
| Open Host Service | OHS | Provide public protocol | Public REST API |
| Published Language | PL | Shared language (schema) | Protobuf/Avro schema |
| Separate Ways | SW | Independent operation | Integration unnecessary |
| Partnership | P | Equal collaboration | Joint development by two teams |
Context Map Example:
+---------------+ OHS/PL +-----------------+
| Order Mgmt | ---------------> | Payment Process |
| (Order BC) | | (Payment BC) |
+-------+-------+ +--------+--------+
| C/S | C/S
v v
+---------------+ ACL +-----------------+
| Shipping Mgmt | <--------------- | External PG |
| (Shipping BC) | | (3rd Party) |
+---------------+ +-----------------+Aggregate Design Principles
Sizing Criteria
Prefer small aggregates:
+-- Minimize transaction scope -> reduce concurrency conflicts
+-- Reduce memory usage
+-- Shrink change impact scope
Exceptions (larger aggregates allowed):
+-- Invariants span multiple entities
+-- Atomic consistency is absolutely required
+-- Cannot be replaced with eventual consistencyInter-aggregate Reference Rules
OK - ID reference: Order.customerId (only holds the Customer aggregate's ID)
NO - Direct reference: Order.customer (directly holds the Customer object)
Reasons:
1. Respects aggregate boundaries
2. Transaction isolation
3. Enables independent storage usageUbiquitous Language Dictionary Template
| Term | Context | Definition | Synonyms | Confusion/Antonyms |
|------|---------|-----------|----------|-------------------|
| Order | Order Management | Customer's product purchase request | Purchase order | Distinct from Cart |
| Account | User Management | Loginable user unit | User | Distinct from financial account |
| Account | Settlement Management | Settlement target financial account | Bank account | Distinct from user account |Service Decomposition Anti-patterns
| Anti-pattern | Symptoms | Resolution |
|---|---|---|
| Nanoservice | Service is too small, only 1-2 APIs | Merge related services |
| Distributed Monolith | All services in synchronous call chains | Switch to event-driven async |
| CRUD Service | Acts as DB proxy without domain logic | Internalize domain logic |
| God Service | Excessive responsibilities in one service | Re-decompose based on bounded contexts |
| Shared DB | Multiple services using the same tables | Separate data ownership |
© revfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in en/23-microservice-designer/.claude/skills/ddd-context-mapping of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Compare with similar skills
Ddd Context Mapping 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 |
|---|---|---|---|---|---|---|
| Ddd Context Mapping this skillrevfactory/harness-100 | 1.3k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Domain Modelingfossasia/eventyay-interpretation | 1.6k | 29 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 revfactory/harness-100
All 464 skills in this repoAnti Bot Analyzer
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
API Security Checklist
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
Arg Parser Generator
revfactory/harness-100
Methodology for systematically designing and generating CLI tool argument parser structures.
Audience Segmentation
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
Audio Storytelling
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
Related
Categories
Questions about Ddd Context Mapping
What does Ddd Context Mapping do?
Detailed methodology for DDD (Domain-Driven Design) bounded context identification, context map creation, and event storming execution. Ddd Context Mapping is an agent skill from revfactory/harness-100. Detailed methodology for DDD (Domain-Driven Design) bounded context identification, context map creation, and event storming execution.
When should I use Ddd Context Mapping?
Ddd Context Mapping fits situations like: bounded context; domain modeling; aggregate design; ubiquitous language.
How do I install Ddd Context Mapping in Claude Code?
Run `npx skills add revfactory/harness-100 --skill ddd-context-mapping -a claude-code`. Or copy the skill folder (en/23-microservice-designer/.claude/skills/ddd-context-mapping in revfactory/harness-100) into .claude/skills/ddd-context-mapping in your project. Claude Code loads it when a task matches its description.
How do I install Ddd Context Mapping in Codex?
Run `npx skills add revfactory/harness-100 --skill ddd-context-mapping -a codex`. Or copy the skill folder (en/23-microservice-designer/.claude/skills/ddd-context-mapping in revfactory/harness-100) into .agents/skills/ddd-context-mapping in your project. Codex loads it when a task matches its description.
Can I use Ddd Context Mapping 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 revfactory/harness-100 --skill ddd-context-mapping -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ddd-context-mapping, .gemini/skills/ddd-context-mapping, .github/skills/ddd-context-mapping and .opencode/skills/ddd-context-mapping in your project.
What does Ddd Context Mapping need to run?
SKILL.md names no scripts, command-line tools or credentials: Ddd Context Mapping is instructions for the agent only.
Does Ddd Context Mapping 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 Ddd Context Mapping 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 Ddd Context Mapping use?
Ddd Context Mapping is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ddd Context Mapping use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Ddd Context Mapping?
Skills that share tags, products or a category with Ddd Context Mapping: 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 Ddd Context Mapping?
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,290 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.