← LeaderboardThe Skill Leaderboard

ddd-context-mapping

Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

ddd-context-mapping

Start a fresh conversation. Replace the highlighted placeholders.

Use ddd-context-mapping to map the bounded contexts in [system description], defining relationship patterns, contract ownership, translation/anti-corruption decisions, and coupling-risk mitigations; include integration failure and versioning policies.

Required inputs

  • [system description]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: ddd-context-mappingdescription: Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.metadata:   aas-risk: safe  aas-source: self  aas-tags: '[ddd, context-map, anti-corruption-layer, integration]'  aas-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

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.
ddd-context-mapping by sickn33 · The Skill Leaderboard