Defines integration contracts and bounded context relationships for robust software architecture.
Install
mkdir -p .claude/skills/ddd-context-mapping && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14336" && unzip -o skill.zip -d .claude/skills/ddd-context-mapping && rm skill.zipInstalls to .claude/skills/ddd-context-mapping
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.Key capabilities
- →Define integration patterns between bounded contexts
- →Prevent domain leakage across service boundaries
- →Plan anti-corruption layers during migration
- →Clarify upstream and downstream ownership for contracts
- →List context pairs and their dependency direction
How it works
The skill guides the user through listing context pairs, choosing relationship patterns, defining translation rules, and establishing ownership boundaries. It also addresses failure modes, fallback behavior, and versioning policies.
Inputs & outputs
When to use ddd-context-mapping
- →Planning service integration
- →Defining anti-corruption layers
- →Mapping domain boundaries
About this skill
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.
When not to use it
- →When a single-context system with no integrations is present
- →When only internal class design is needed
- →When selecting cloud infrastructure tooling
Limitations
- →Does not replace API-level schema design
- →Does not guarantee organizational alignment by itself
- →Should be revisited when team ownership changes
How it compares
This skill provides a structured approach to defining context relationships and integration contracts, which is more formal than ad-hoc integration planning.
Compared to similar skills
ddd-context-mapping side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ddd-context-mapping (this skill) | 0 | 1mo | No flags | Intermediate |
| architecture-patterns | 55 | 2mo | No flags | Advanced |
| kotlin-multiplatform | 32 | 3mo | Review | Advanced |
| nodejs-best-practices | 28 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by bg-szy
View all by bg-szy →You might also like
architecture-patterns
wshobson
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
kotlin-multiplatform
vitorpamplona
Platform abstraction decision-making for Amethyst KMP project. Guides when to abstract vs keep platform-specific, source set placement (commonMain, jvmAndroid, platform-specific), expect/actual patterns. Covers primary targets (Android, JVM/Desktop, iOS) with web/wasm future considerations. Integrates with gradle-expert for dependency issues. Triggers on: abstraction decisions ("should I share this?"), source set placement questions, expect/actual creation, build.gradle.kts work, incorrect placement detection, KMP dependency suggestions.
nodejs-best-practices
davila7
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
workflow-orchestration-patterns
wshobson
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
java-pro
sickn33
Master Java 21+ with modern features like virtual threads, pattern matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java development, microservices architecture, or performance optimization.
arm-cortex-expert
sickn33
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and peripheral drivers.