Start a fresh conversation. Replace the highlighted placeholders.
Use ddd-context-mapping to map integrations among [bounded contexts], delivering context relationships, contract ownership, translation and anti-corruption decisions, failure handling, versioning, and coupling risks.
Required inputs
[bounded contexts]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: ddd-context-mappingdescription: "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns."risk: safesource: selftags: "[ddd, context-map, anti-corruption-layer, integration]"date_added: "2026-02-27"
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
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.