# Map Bounded Context Relationships

Unclear service boundaries cause domain leakage and fragile integrations. This skill maps relationships, contract ownership, translations, failures, and versioning policies.

## Install

```bash
npx skillstore add sickn33/ddd-context-mapping
```

## Metadata

- Status: approved
- Slug: sickn33-ddd-context-mapping
- Skillstore revision: r2
- Version status: missing
- Tree hash: 5e1725ca09ac72fef76d0e21121def8fe401fc458f9a47d9af1e930ce65c18b5
- Author: sickn33
- GitHub username: sickn33
- License: MIT
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/ddd-context-mapping
- Ref: f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 74
- Public page: https://skillstore.pages.dev/skills/sickn33-ddd-context-mapping
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-ddd-context-mapping/manifest

## Capabilities

- Lists bounded context pairs and identifies dependency direction.
- Selects DDD relationship patterns for each context pair.
- Defines contract ownership and translation boundaries.
- Plans anti-corruption layers that protect local domain language.
- Documents integration failures, fallback behavior, coupling risks, and versioning policies.

## Use Cases

- Design Service Integrations: Map upstream and downstream dependencies before teams define service contracts.
- Protect Domain Boundaries: Identify translation needs and anti-corruption layers around external models.
- Plan System Migration: Document temporary relationships, ownership, fallbacks, and versioning during incremental modernization.

## Prompt Templates

### Identify Context Relationships

```
List the bounded contexts in [system]. For each connected pair, identify the upstream context, downstream context, dependency, and exchanged business capability.
```

### Select Mapping Patterns

```
Map relationships among [contexts]. Choose a DDD context mapping pattern for each pair and explain ownership, coordination needs, and coupling risks.
```

### Design Translation Boundaries

```
Design an anti-corruption layer between [external context] and [local context]. Define translated concepts, boundary ownership, failure handling, and required contract tests.
```

### Create a Governed Context Map

```
Create a complete context map for [system]. Include every relationship, contract owner, translation rule, failure mode, fallback, versioning policy, and mitigation.
```

## Limitations

- Does not design detailed API schemas or message formats.
- Does not replace discussions between teams that own connected contexts.
- Does not cover internal class design within one bounded context.
- Requires revision when system dependencies or team ownership change.

## Best Practices

- Name every upstream and downstream context explicitly.
- Assign one clear owner to each integration contract.
- Review context maps after ownership, dependencies, or business language change.

## Anti Patterns

- Do not select a relationship pattern without documenting dependency direction.
- Do not share domain models across contexts only to reduce mapping work.
- Do not omit failure behavior and contract versioning from integration decisions.

## Security Audit

- Audited at: 2026-07-23T22:55:14.347\+00:00
- Summary: Both static findings are false positives caused by Markdown backticks in SKILL.md. The reviewed files contain guidance only, with no executable commands or prompt injection.

## Stats

- Views: 135
- Downloads: 10
- Favorites: 0
- Popularity score: 0