Skill

ddd-context-mapping

Maps relationships between bounded contexts in DDD and defines integration contracts, anti-corruption layers, ownership, and risks.

backend

api-development

From antigravity-bundle-ddd-evented-architecture

Install

Run in your terminal

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

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

references/context-map-patterns.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

hybrid-cloud-networking

1 file

Configures VPN and dedicated connections like Direct Connect, ExpressRoute, Interconnect for secure on-premises to AWS, Azure, GCP, OCI hybrid networking.

cloud-infrastructure

33.0k

Stats

Parent Repo Stars30781

Parent Repo Forks5140

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View 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

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.