sanurb/context-map
context-map/SKILL.md
Produce a DDD Context Map showing relationships between Bounded Contexts from existing UBIQUITOUS_LANGUAGE.md glossaries or conversation context. Saves to CONTEXT_MAP.md. Triggers on "context map", "context mapping", "bounded context relationships", "how do these contexts relate", "upstream downstream".
tools
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add sanurb/skills context-mapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 4:48 PM9.0s1 file scanned
SKILL.md
- name:
- context-map
- description:
- Produce a DDD Context Map showing relationships between Bounded Contexts from existing UBIQUITOUS_LANGUAGE.md glossaries or conversation context. Saves to CONTEXT_MAP.md. Triggers on "context map", "context mapping", "bounded context relationships", "how do these contexts relate", "upstream downstream".
Context Map
Identify all Bounded Contexts in scope and classify the relationship between each pair using Evans/Vernon's canonical patterns. One map per system. Every relationship typed, every direction explicit.
Instructions
-
Discover contexts. Scan the working directory for
UBIQUITOUS_LANGUAGE.mdfiles — each one names a Bounded Context in its header. If none exist, extract context boundaries from the current conversation. Ask the user if the boundary between two contexts is unclear. Minimum 2 contexts required — a map of one context is meaningless; tell the user to runubiquitous-languagefirst. -
Classify relationships. For every pair of contexts that communicate, assign exactly one relationship pattern from relationship-patterns.md. Determine direction: which is upstream (supplier) and which is downstream (consumer). If a pair has no communication, omit it — do not invent relationships. Use
🔀 CROSS-CONTEXTflags from glossaries as evidence when available. -
Write. Produce
CONTEXT_MAP.mdin the working directory following the exact structure in output-format.md. Then print an inline summary:N contexts | M relationships | K unresolved.
Non-Negotiable Acceptance Criteria
- Output file matches output-format.md exactly. No sections added, removed, or renamed.
- Every relationship uses one pattern from relationship-patterns.md. No invented patterns.
- Every relationship states upstream/downstream direction. Symmetric patterns (Shared Kernel, Partnership) mark both sides explicitly.
- No relationship between contexts that don't actually communicate. Omission is correct; fabrication is not.
- Shared terms that mean different things across contexts appear in the Translation Table with both definitions.
- Minimum 2 contexts, minimum 1 relationship. If the conversation doesn't support this, tell the user — do not fabricate.
- Inline summary is the last thing printed. Format:
N contexts | M relationships | K unresolved.
Output
File: CONTEXT_MAP.md in the current working directory.
Format: output-format.md.
Inline: summary line after file is written.
Related Skills
sanurb/setup-sanurb-skills
development
VerifiedTrustedCommunity
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub, GitLab, fp, or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `fp-plan`, `fp-implement`, `fp-review`, `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
SKILL.mdUpdated Jun 4, 2026
sanurb/prototype
development
VerifiedTrustedCommunity
Build a throwaway prototype to flush out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".
SKILL.mdUpdated Jun 4, 2026
sanurb/herdr
tools
VerifiedTrustedCommunity
Control herdr (a terminal-native agent multiplexer) from inside it. Manage workspaces and tabs, split panes, spawn sibling agents, read pane output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1). Do not use outside herdr.
SKILL.mdUpdated Jun 4, 2026
sanurb/handoff
documentation
VerifiedTrustedCommunity
Compact the current conversation into a handoff document for another agent to pick up.
SKILL.mdUpdated Jun 4, 2026