ddd-context-mapping
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
IT & Software Development[dddanti-corruption-layercontext-mapdddintegrationintegration]
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.
Details
| Source | self |
|---|---|
| License | — |
| Risk label | safe ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md, references/context-map-patterns.md |
| Added | 2026-02-27 |
Related skills
architect-review
Master software architect specializing in modern architecture
architecture
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
architecture-decision-records
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
architecture-patterns
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
c4-architecture-c4-architecture
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
c4-code
Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure.