Agent skill · product strategy · sickn33
ddd-context-mapping
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
Why this skill is useful
Provides specific patterns and rules for defining integration contracts between bounded contexts that the AI wouldn't reliably generate on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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 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.
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/ddd-context-mapping--bc2497