What problem does it solve? TypeScript monorepos often leak implementation details across packages, letting any file import any other file and eroding module boundaries. This Skill wires dependency-cruiser into a repo so each package becomes a deep module: implementation hidden in subfolders, reachable only through its root entry-point files. ## 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 fail the build on deep imports. - Multiple entry points per package: Supports several small root entry files (index.ts, client.ts, server.ts) instead of one giant barrel index. - Verified setup: Scaffolds an example package and proves the rules bite by observing a pass, a forced failure on a deep import, then a pass again. - Use Case: A team adopting a packages/ monorepo layout wants CI to reject imports like packages/billing/lib/stripe from other packages, forcing all access through public entry points. ## Quick Start Ask the agent to set up deep-module boundaries with dependency-cruiser for this TypeScript repo and verify the rules fail on a deep import.
