cross-context

Design Anti-Corruption Layer and Context Mapping patterns for bounded contexts.

2|Updated Dec 24, 2025

Search Tags:#architecture #integration #cross-context #bounded-context #ACL #context-mapping

Ready to run

npx skills add https://github.com/knowlet/skills --skill cross-context

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cross-context
Source: https://github.com/knowlet/skills/tree/main/skills/cross-context
Command: npx skills add https://github.com/knowlet/skills --skill cross-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams manage dependencies across bounded contexts by designing Anti-Corruption Layers and Context Mapping to prevent model pollution and ensure clean integration.

Core Features & Use Cases

Identify cross-context dependencies: Detect when multiple BCs must collaborate.
Design integration patterns: ACL, Open Host Service, Shared Kernel, etc.
Define cross-context contracts: Establish robust, versioned interfaces between BCs.
Ensure isolation: Prevent leakage of external models into the current BC.

Quick Start

When the analysis framework detects cross_context_dependencies, run this Skill to generate ACL and Context Mapping guidelines for the involved BCs.

Frequently Asked Questions about cross-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent model contamination when integrating multiple bounded contexts?▼

Design an Anti-Corruption Layer to translate between bounded contexts and block external models from leaking into your context. ACL acts as a boundary that detects dependencies, maps contracts, and isolates concerns across integration points.

What integration patterns should I use for cross-context dependencies in payments or notifications?▼

Select from Anti-Corruption Layer, Open Host Service, or Shared Kernel based on your dependency direction and isolation needs. Each pattern defines how contexts expose contracts and handle translation between different domain models.

How do I identify when bounded contexts need to communicate?▼

Detect cross-context dependencies by analyzing where authorization, payments, or notifications span multiple contexts. Map dependency types and directions to determine which integration pattern and contract structure fits each interaction.

What should a cross-context contract include?▼

Define versioned interfaces that specify functional and technical requirements: data formats, error handling, timeouts, and retries. Contracts establish clear boundaries and enable safe translation between context models without coupling implementation details.

How do I ensure fault tolerance across bounded contexts?▼

Configure timeouts, retries, and observability within your integration layer to handle failures gracefully. Monitor cross-context communication to detect cascading failures and maintain isolation when one context becomes unavailable.