aa71e76eb9
- Add date_added to all 950+ skills for complete tracking - Update version to 6.5.0 in package.json and README - Regenerate all indexes and catalog - Sync all generated files Features from merged PR #150: - Stars/Upvotes system for community-driven discovery - Auto-update mechanism via START_APP.bat - Interactive Prompt Builder - Date tracking badges - Smart auto-categorization All skills validated and indexed. Made-with: Cursor
53 lines
1.5 KiB
Markdown
53 lines
1.5 KiB
Markdown
---
|
|
name: ddd-context-mapping
|
|
description: "Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns."
|
|
risk: safe
|
|
source: self
|
|
tags: "[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
|
|
|
|
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.
|