context-maplisted

Maintains a strategic DDD Context Map (`docs/context-map.md` with Mermaid diagram) showing relationships between bounded contexts (Customer/Supplier, Anti-Corruption Layer, Open Host Service, Shared Kernel, Published Language, Conformist, Separate Ways, Partnership) and each context's subdomain type (Core/Supporting/Generic — drives pattern choice and rule-set strictness). Use when introducing a new context, changing cross-context communication, classifying subdomains, or onboarding to understand the system.
domain-centric-development/dca-marketplace · ★ 0 · Web & Frontend · score 75

Install: claude install-skill domain-centric-development/dca-marketplace

# /context-map — Strategic DDD context map The context map is DDD's strategic-design centerpiece: which bounded contexts exist, how they relate, who's upstream/downstream, and *what pattern* governs each relationship. This skill keeps the map in sync with the code — in one of two modes: - **Declared mode** (projects on the DCA packages): the relationships are *declared in code* on the context root — `@Upstream`, `@ExternalUpstream`, `@Partnership` on `package-info.java` (Java) or `[Upstream]`, `[ExternalUpstream]`, `[Partnership]` on the `XContext` marker class (C#). The `contextmap` rule set (`DCA-MAP-*`) fails the build when a declaration and the real dependencies disagree, and `ContextMapRenderer` renders `docs/architecture/context-map.md` from an opt-in test. The skill **edits the declarations and runs that test**; it never hand-edits the rendered file. What the declarations cannot carry — the pattern name a relationship goes by and the subdomain type of each context — belongs in the hand-maintained map at `docs/context-map.md`, which the skill does own. - **Manual mode** (no packages): the skill maintains `docs/context-map.md` itself from the heuristics below. Detect the mode first: `grep -rln "@Upstream\|\[Upstream\|@BoundedContext\|\[BoundedContext" --include=*.java --include=*.cs`. Declarations found → declared mode. Otherwise Modulith `@ApplicationModule` metadata, then the event/ACL heuristics. ## Map location Two files, two owners — never