What problem does it solve? TypeScript monorepos often leak implementation details through deep imports, making packages tightly coupled and hard to refactor. This Skill wires dependency-cruiser into a repo so each package exposes only its root entry-point files while everything in subfolders stays private. ## Core Features & Use Cases - 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. - Environment Detection: Detects the package manager (pnpm, yarn, bun, npm), the packages root (src/packages or packages), and merges rules into any existing dependency-cruiser config without overwriting it. - Verified Setup: Scaffolds an example package with a hidden lib/ implementation 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/ layout wants to stop other packages from importing internal files like packages/billing/lib/stripe.ts directly; this Skill sets up the lint:boundaries check, folds it into the existing typecheck command, and documents the convention in CLAUDE.md or AGENTS.md. ## Quick Start Ask the AI to set up deep-module boundary enforcement with dependency-cruiser for the packages in this TypeScript repository.
