What problem does it solve? TypeScript monorepos often leak implementation details through deep imports, making packages tightly coupled and refactors risky. This Skill wires dependency-cruiser into a repo so each package exposes only its root entry-point files while everything in subfolders stays private, and it proves the rules actually fail on violations. ## Core Features & Use Cases - Entry-point boundary enforcement: Installs four dependency-cruiser rules (entry-point boundary, intra-package freedom, tests-through-entrypoints, no cycles) that block imports into package subfolders from outside code. - Scaffolded example package: Creates a copy-me template package with a root index.ts entry point, hidden lib/ implementation, and tests that import only through the entry point. - Verification loop: Runs the boundary lint to confirm it passes on clean code, fails on an injected deep import, then passes again after revert. - Use Case: A team adopting a src/packages/<name>/ layout wants CI to reject any import that bypasses a package's public entry points, without maintaining per-package rules or barrel files. ## Quick Start Ask the agent to set up deep-module boundaries with dependency-cruiser in this TypeScript repo and verify the rules fail on a deep import.
