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
- •List all context pairs and dependency direction.
- •Choose relationship patterns per pair.
- •Define translation rules and ownership boundaries.
- •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.
🏰 Rei Skills — Curated by Rootcastle Engineering & Innovation | Batuhan Ayrıbaş
Engineering Beyond Boundaries | admin@rootcastle.com