What problem does it solve? TypeScript monorepos often leak implementation details because any file can import any other file, making packages shallow and tightly coupled. This Skill wires dependency-cruiser into a repo so each package becomes a deep module: implementation hidden in subfolders and reachable only through its root entry-point files. ## Core Features & Use Cases - Boundary rule installation: Installs dependency-cruiser and writes a .dependency-cruiser.cjs config with four error-level rules covering entry-point boundaries, intra-package freedom, tests-through-entrypoints, and cycle detection. - Verification loop: Scaffolds an example package, then proves the rules bite by observing a pass, a deliberate failure on a deep import, and a pass again. - Documentation and discoverability: Writes a README in the packages folder discouraging barrel files and adds a pointer from CLAUDE.md or AGENTS.md so agents discover the convention. - Use Case: A team adopting package-based architecture in a pnpm monorepo runs this Skill to enforce that src/packages/billing is only ever imported through its root files, never its lib/ internals. ## Quick Start Ask the agent to set up deep-module boundaries with dependency-cruiser for the packages in this TypeScript repo.
