What problem does it solve? Modular codebases drift over time: import cycles appear, domain modules start importing entrypoints, and generic folders like utils or shared quietly absorb real responsibilities. This Skill audits and enforces a Domain DAG architecture so every durable module has clear ownership, explicit exclusions, and a one-directional dependency graph. ## Core Features & Use Cases - Import Graph Validation: Detects cycles, reverse entrypoint imports, forbidden edges, and layer-direction violations across TypeScript, JavaScript, and Svelte sources, including configured path aliases. - Ownership & Boundary Guidance: Provides axioms, placement heuristics, extraction protocols, and stop rules for deciding where code belongs and when to stop decomposing. - Configurable Severity Ladder: Distinguishes hard failures (cycles, forbidden edges) from heuristic warnings (shared buckets, missing headers, wide interface surfaces) via a project-local domain-dag.json. - Use Case: Before merging a refactor of a monorepo, run the bundled validator from the project root to confirm the local import graph is acyclic and no domain module reaches into the application composition root. ## Quick Start Ask the agent to run the domain-dag validator against the current project root and report any import cycles or boundary violations.
