Tight coupling between modules
Direct import cycles between modules increase coupling and make change boundaries harder to maintain.
#Metadata
#Why it matters
Cyclic dependencies complicate initialization order, testing, and architecture boundaries.
#Remediation
Extract shared types or helpers into a third module, or invert the dependency so the cycle disappears.
#Repository path
The generated metadata points to critiq-rules/libs/rules/catalog/rules/typescript/ts.quality.tight-module-coupling.rule.yaml.