agentsclimarketplace

Ddd context mapping

Skill sinhoneyy/master-skills/plugins/master-skills-ai-agent-builder/skills/ddd-context-mapping

Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.From its SKILL.md

Install
npx -y skills add sinhoneyy/master-skills --skill ddd-context-mapping

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 250 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 1 file

673 B alongside SKILL.md

references/

Keep looking

Skills are one crate of 610,220. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.