mcpField
D
ddd-context-mapping

ddd-context-mapping

github.com/sickn33Development48.7k123 installsUpdated today
Repository

About ddd-context-mapping

ddd-context-mapping is a skill for designing relationships and boundaries between bounded contexts in systems with integrations. It guides teams through dependency direction, relationship patterns, contract ownership, translation rules, and coupling risks.

Key features

  1. 01Map context pairs and dependency direction
  2. 02Choose integration relationship patterns
  3. 03Define translation and ownership boundaries
  4. 04Record failure handling and versioning
  5. 05Identify coupling risks and mitigations

Use cases

  1. 01Plan integrations between domain contexts
  2. 02Design anti-corruption layers for migrations
  3. 03Clarify contract ownership across services
  4. 04Document fallback behavior and versioning policies

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill ddd-context-mapping

After installing, type/ddd-context-mappingin Claude Code to confirm it loaded.

Bundled filesreferences/context-map-patterns.md

Details

From the project README

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

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.

Comments

Markdown supported