Ddd Context Mapping

1---
2name: ddd-context-mapping
3description: Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
4risk: safe
5source: self
6tags: [ddd, context-map, anti-corruption-layer, integration]
7---
8 
9# DDD Context Mapping
10 
11## Use this skill when
12 
13- Defining integration patterns between bounded contexts.
14- Preventing domain leakage across service boundaries.
15- Planning anti-corruption layers during migration.
16- Clarifying upstream and downstream ownership for contracts.
17 
18## Do not use this skill when
19 
20- You have a single-context system with no integrations.
21- You only need internal class design.
22- You are selecting cloud infrastructure tooling.
23 
24## Instructions
25 
261. List all context pairs and dependency direction.
272. Choose relationship patterns per pair.
283. Define translation rules and ownership boundaries.
294. Add failure modes, fallback behavior, and versioning policy.
30 
31If detailed mapping structures are needed, open `references/context-map-patterns.md`.
32 
33## Output requirements
34 
35- Relationship map for all context pairs
36- Contract ownership matrix
37- Translation and anti-corruption decisions
38- Known coupling risks and mitigation plan
39 
40## Examples
41 
42```text
43Use @ddd-context-mapping to define how Checkout integrates with Billing,
44Inventory, and Fraud contexts, including ACL and contract ownership.
45```
46 
47## Limitations
48 
49- This skill does not replace API-level schema design.
50- It does not guarantee organizational alignment by itself.
51- It should be revisited when team ownership changes.
52