linguistic-boundary-verifier

What problem does it solve?

This Skill solves the problem of ubiquitous language leaking across bounded context boundaries in modular software systems, which creates hidden coupling between modules that should be independent. Standard architectural dependency tools miss these leaks because they often take the form of string literals, event language, or misdirected API calls that do not show up in import graphs.

Core Features & Use Cases

• Boundary Violation Detection: Analyzes language.md files to map module relationships and vocabulary, then scans code for foreign terms, reversed event flow, and wrong-direction API calls.
• Type-Specific Fix Proposals: Suggests targeted fixes for each violation type: behavior generalization for string leaks, ACL translation for event leaks, and dependency inversion for misdirected API calls.
• Visual Reporting: Generates clear before/after ASCII diagrams for each violation to make problems and fixes immediately understandable, plus a full boundary report artifact.
• Use Cases: Use for architectural reviews of multi-module changes, single-module PR checks for new concept consistency, quarterly architecture health checks, and post-refactoring boundary validation.

Quick Start

Invoke the linguistic-boundary-verifier skill with your module names to scan for language leakage across bounded context boundaries and receive a report with proposed fixes and visual diagrams.