Automated summary
This skill maps relationships between bounded contexts and defines integration contracts using DDD context mapping patterns.
Strengths
- Walks through four concrete steps: context pairs, pattern selection, translation rules, and failure/versioning policy.
- Delivers a contract ownership matrix that makes upstream/downstream responsibility explicit.
- Explicitly captures anti-corruption decisions and a coupling-risk mitigation plan.
- Ships a dedicated reference file for deeper context map patterns.
Limitations
- Does not substitute for API-level schema design.
- Does not by itself guarantee organizational alignment across teams.
- Must be revisited whenever team ownership changes.
Use it when several bounded contexts must integrate and you need to settle contract ownership and prevent domain leakage across boundaries.
Avoid it for a single-context system with no integrations, or when you only need internal class design.
Security analysis
SafeThe skill is purely instructional documentation for DDD context mapping. It declares no tools, executes no commands, accesses no network or secrets, and contains no destructive or exfiltrating behavior.
No concerns found
How this analysis is madeExamples
Use @ddd-context-mapping to define how Checkout integrates with Billing, Inventory, and Fraud contexts, including ACL and contract ownership.We are migrating a legacy monolith to services. Map each context pair, pick relationship patterns, and specify the anti-corruption layer translation rules and versioning policy.Produce a contract ownership matrix for our Order, Payment, and Notification contexts, listing upstream/downstream direction, failure modes, and fallback behavior.name: ddd-context-mapping description: Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns. risk: safe source: self tags: "[ddd, context-map, anti-corruption-layer, integration]" date_added: "2026-02-27" domain: "Backend & APIs" size_class: s summary: Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns. detail_sections:
- Use this skill when
- Do not use this skill when
- Instructions
- Output requirements
- Examples
- Limitations
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.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ddd-context-mapping-mrzxuqqj' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ddd-context-mapping-mrzxuqqj/download' --output '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md.part' && mv '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md.part' '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md' && test -s '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ddd-context-mapping' && cp -R '.skill-downloads/ddd-context-mapping-mrzxuqqj' '.claude/skills/ddd-context-mapping'Cursor
test -f '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md' && test -s '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/ddd-context-mapping' && cp -R '.skill-downloads/ddd-context-mapping-mrzxuqqj' '.cursor/skills/ddd-context-mapping'Codex
test -f '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md' && test -s '.skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/ddd-context-mapping' && cp -R '.skill-downloads/ddd-context-mapping-mrzxuqqj' '.agents/skills/ddd-context-mapping'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ddd-context-mapping-mrzxuqqj'openskills read 'ddd-context-mapping-mrzxuqqj'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ddd-context-mapping-mrzxuqqj/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.