Skills ddd-context-mapping

📦

ddd-context-mapping

Name: ddd-context-mapping
Author: sickn33

Content revision r2 Safe ⚙️ External commands

Map Bounded Context Relationships

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

Supports: Claude Codex Code(CC)

📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "ddd-context-mapping" from https://skillstore.io/skills/sickn33-ddd-context-mapping.md and its manifest at https://skillstore.io/api/skills/sickn33-ddd-context-mapping/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-ddd-context-mapping.md Signed manifest GET /api/skills/sickn33-ddd-context-mapping/manifest Signed lockfile GET /api/skills/sickn33-ddd-context-mapping/lockfile

Test it

Using "ddd-context-mapping". Map how Checkout depends on Billing and Inventory.

Expected outcome:

Billing is upstream of Checkout through a customer-supplier relationship. Billing owns the payment contract.
Inventory is upstream of Checkout through a conformist relationship. Checkout accepts the published availability model.
Checkout translates billing failures into local order states and uses a reservation timeout for inventory failures.

Using "ddd-context-mapping". Protect the Claims context from a legacy Policy system.

Expected outcome:

Place an anti-corruption layer at the Claims boundary. Translate legacy policy terms into Claims language, isolate failures, and verify mappings with contract tests.

Using "ddd-context-mapping". Define governance for Catalog events consumed by Search.

Expected outcome:

Catalog owns the published event language. Search owns its local projection, supports two event versions, and alerts on rejected or delayed events.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

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.

Files scanned

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (2)

SKILL.md:32 SKILL.md:43-46

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-ddd-context-mapping/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-ddd-context-mapping/security.svg)](https://skillstore.io/skills/sickn33-ddd-context-mapping?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-ddd-context-mapping?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-ddd-context-mapping/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-ddd-context-mapping.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). ddd-context-mapping security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-ddd-context-mapping/audits/5

BibTeX citation

@techreport{sickn33-sickn33-ddd-context-mapping-2026,
  author = {sickn33},
  title = {ddd-context-mapping security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/sickn33-ddd-context-mapping/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ddd-context-mapping security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-ddd-context-mapping/audits/5"
identifiers:
  - type: other
    value: "skillstore:sickn33-ddd-context-mapping:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.

Avoid

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.

Frequently Asked Questions

What information should I provide?

Provide context names, responsibilities, dependency directions, exchanged concepts, contract owners, and known integration constraints.

Does this skill create API schemas?

No. It defines context relationships and ownership decisions before detailed API or event schema design.

Which DDD patterns can it recommend?

It covers partnership, shared kernel, customer-supplier, conformist, anti-corruption layer, open host service, and published language.

Can it help with legacy migrations?

Yes. It can define anti-corruption layers, translation ownership, temporary dependencies, fallback behavior, and migration risks.

How often should a context map be reviewed?

Review it whenever team ownership, business language, integration contracts, or dependency directions change.

Can it resolve organizational disagreements?

No. It documents decisions and tradeoffs, but responsible teams must agree on ownership and coordination.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/ddd-context-mapping

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

8 downloads · 135 views

File structure

📁 references/

📄 context-map-patterns.md

📄 SKILL.md