ddd-context-mapping
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
Best use case
ddd-context-mapping is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
Teams using ddd-context-mapping should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ddd-context-mapping/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ddd-context-mapping Compares
| Feature / Agent | ddd-context-mapping | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# DDD Context Mapping ## Use this skill when - Defining integration patterns between bounded contexts. - Preventing domain leakage across service boundaries. - Planning anti-corruption layers during migration. - Clarifying upstream and downstream ownership for contracts. ## Do not use this skill when - You have a single-context system with no integrations. - You only need internal class design. - You are selecting cloud infrastructure tooling. ## Instructions 1. List all context pairs and dependency direction. 2. Choose relationship patterns per pair. 3. Define translation rules and ownership boundaries. 4. Add failure modes, fallback behavior, and versioning policy. If detailed mapping structures are needed, open `references/context-map-patterns.md`. ## Output requirements - Relationship map for all context pairs - Contract ownership matrix - Translation and anti-corruption decisions - Known coupling risks and mitigation plan ## Examples ```text Use @ddd-context-mapping to define how Checkout integrates with Billing, Inventory, and Fraud contexts, including ACL and contract ownership. ``` ## Limitations - This skill does not replace API-level schema design. - It does not guarantee organizational alignment by itself. - It should be revisited when team ownership changes.
Related Skills
threat-mitigation-mapping
Map identified threats to appropriate security controls and mitigations. Use when prioritizing security investments, creating remediation plans, or validating control effectiveness.
hig-project-context
Create or update a shared Apple design context document that other HIG skills use to tailor guidance.
context7-auto-research
Automatically fetch latest library/framework documentation for Claude Code via Context7 API
context-window-management
Strategies for managing LLM context windows including summarization, trimming, routing, and avoiding context rot Use when: context window, token limit, context management, context engineering, long...
context-optimization
Apply compaction, masking, and caching strategies
context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems.
context-management-context-save
Use when working with context management context save
context-management-context-restore
Use when working with context management context restore
context-fundamentals
Understand what context is, why it matters, and the anatomy of context in agent systems
context-driven-development
Use this skill when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md, and...
context-degradation
Recognize patterns of context failure: lost-in-middle, poisoning, distraction, and clash
context-compression
Design and evaluate compression strategies for long-running sessions