# Domain Boundary And Language Integrity Evaluator

> Enforce DDD bounded contexts, ubiquitous language, anti-corruption layers, and shared-kernel safety. Use when reviewing cross-domain communication, shared libraries, DTO mappings, or domain model leakage.

- Skill: `anyulled/domain-boundary-and-language-integrity-evaluator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add anyulled/domain-boundary-and-language-integrity-evaluator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/anyulled/domain-boundary-and-language-integrity-evaluator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: anyulled (https://skillmd.com/u/anyulled)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/anyulled/domain-boundary-and-language-integrity-evaluator

---


# Domain Boundary and Language Integrity Evaluator

Enforce DDD boundaries and prevent domain model leakage across contexts.

## When to Use

- PRs that change cross-domain communication
- New shared libraries or shared domain models
- Data structures passed between bounded contexts
- DDD boundary or context-map audits

## Scope

- Scans: core domain entities, DTOs, mappers, translators, and cross-domain service clients that may leak bounded-context concepts.
- Exclusions: technical utilities, stable shared contracts, and explicit infrastructure adapters that do not encode domain concepts.
- Fallback: if a boundary or glossary is unclear, apply the shared conventions heuristic order and downgrade to warning with low confidence.
- Routing: defer shared-table and ORM leakage to Data and Database Coupling Evaluator and shared-kernel extraction concerns to Component Extraction and Tactical Forking Analyzer.

## Workflow

1. Detect domain entity leakage.
   - Map bounded contexts from namespaces, directories, or modules.
   - Flag entities passed, returned, or instantiated across contexts without translation.
2. Verify anti-corruption layers.
   - Check that cross-context integrations pass through mappers or ACLs.
   - Flag direct ingestion of upstream contracts by downstream domains.
3. Evaluate shared kernels.
   - Distinguish technical utilities from shared domain concepts.
   - Flag malignant shared domain models that reduce team autonomy.
   - Allow intentional shared-contract modules to pass when they are explicit integration DTOs and not domain behavior.
   - Downgrade shared kernel findings when the shared types are pipeline envelopes or transport contracts rather than business entities.
4. Report findings.
   - Include file paths and line numbers for leakage.
   - Summarize missing ACLs and shared-kernel violations.

## Rules

- Use static analysis and module boundary configuration only.
- Keep the analysis deterministic and language-agnostic.
- Treat shared domain models as boundary violations unless explicitly justified.
- Distinguish explicit shared contracts from leaking domain models.
- If naming drift exists but translation is present, prefer warning over fail.

## Shared Conventions

- Follow the repository-wide conventions in [shared-skill-conventions](../../references/shared-skill-conventions.md).
- Use the canonical output contract, severity levels, confidence rubric, routing rules, and false-positive downgrades defined there.
- If this skill is not the closest match, defer to the routing guidance in the shared conventions file.

## Output

Return:

- Domain entity leakage findings
- Missing anti-corruption layers
- Malignant shared kernel classes
- CI-ready pass or fail output