Skill

ddd-context-mapping

From antigravity-bundle-ddd-evented-architecture

Maps relationships between bounded contexts and defines integration contracts using DDD context mapping patterns. Use for service integrations, anti-corruption layers, and ownership clarification.

backend

api-development

npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-bundle-ddd-evented-architecture

Popularity

Parent stars

37,904

Parent forks

6,202

Shared by

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/antigravity-bundle-ddd-evented-architecture:ddd-context-mapping

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

- Defining integration patterns between bounded contexts.

Supporting Files

references/context-map-patterns.md

SKILL.md

53 lines · ~395 tokens

Similar Skills

ddd-context-mapping

38.0k

Maps relationships between bounded contexts and defines integration contracts using DDD context mapping patterns. Use for service integrations, anti-corruption layers, and ownership clarification.

1 file

antigravity-awesome-skills

context-mapping

Maps relationships between bounded contexts using DDD patterns (ACL, OHS, PL, shared kernel). Generates Context Mapper DSL (CML), Mermaid/PlantUML diagrams after event storming.

5 files7 tools

enterprise-architecture

system-decomposition

Break complex systems into bounded contexts with DDD. Map business capabilities to service boundaries, define ubiquitous language, assess cohesion/coupling. Use when refactoring monoliths or designing new architectures.

5 tools

system-design

Stats

LanguagePython

Parent stars37,904

Parent forks6,202

MaintenanceExcellent

Last CommitMay 16, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

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.