ddd-context-mapping
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
Best use case
ddd-context-mapping is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
Teams using ddd-context-mapping should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ddd-context-mapping/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ddd-context-mapping Compares
| Feature / Agent | ddd-context-mapping | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Map relationships between bounded contexts and define integration contracts using DDD context mapping patterns.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ```text 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.
Related Skills
react-context-setup
React Context Setup - Auto-activating skill for Frontend Development. Triggers on: react context setup, react context setup Part of the Frontend Development skill category.
error-mapping-helper
Error Mapping Helper - Auto-activating skill for API Integration. Triggers on: error mapping helper, error mapping helper Part of the API Integration skill category.
cursor-context-management
Optimize context window usage in Cursor with @-mentions, context pills, and conversation strategy. Triggers on "cursor context", "context window", "context limit", "cursor memory", "context management", "@-mentions", "context pills".
agent-context-loader
Execute proactive auto-loading: automatically detects and loads agents.md files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
filesystem-context
This skill should be used when the user asks to "offload context to files", "implement dynamic context discovery", "use filesystem for agent memory", "reduce context window bloat", or mentions file-based context management, tool output persistence, agent scratch pads, or just-in-time context loading.
what-context-needed
Ask Copilot what files it needs to see before answering a question
context-map
Generate a map of all files relevant to a task before making changes
go-context
Use when working with context.Context in Go — placement in signatures, propagating cancellation and deadlines, and storing values in context vs parameters. Also use when cancelling long-running operations, setting timeouts, or passing request-scoped data, even if they don't mention context.Context directly. Does not cover goroutine lifecycle or sync primitives (see go-concurrency).
../../../marketing-skill/marketing-context/SKILL.md
No description provided.
context-engine
Loads and manages company context for all C-suite advisor skills. Reads ~/.claude/company-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy/anonymization rules before external API calls.
json-to-llm-context
Turn JSON or PostgreSQL jsonb payloads into compact readable context for LLMs. Use when a user wants to compress JSON, reduce token usage, summarize API responses, or convert structured data into model-friendly text without dumping raw paths.
opencontext
Persistent memory and context management for AI agents using OpenContext. Keep context across sessions/repos/dates, store conclusions, and provide document search workflows.