architecture-guardian

To enforce clean architecture boundaries in a TypeScript project, validate layer dependencies to ensure Domain does not import Application or Infrastructure. This skill detects import violations, flags offending files and symbols, and proposes guided refactoring fixes.

Improper imports in your domain layer occur when architectural boundaries are breached by importing Application or Infrastructure. Layer validation detects these cross-layer coupling violations, reports the offending files with rationale, and suggests refactor fixes to restore separation.

The best way to detect dependency management violations in layered architecture is to run validation that checks whether repositories depend on Domain and implementations on Infrastructure, flagging tests and DTOs that breach boundaries with file and symbol context.

Yes, architecture validation works with TypeScript and Node.js projects using domain-driven design. It validates layer boundaries between Domain, Application, and Infrastructure, ensuring DTOs stay constrained to application interfaces and detecting boundary breaches.

To fix code quality issues from cross-layer coupling in TypeScript, use guided fixes that propose refactor suggestions and optional automated patches for import violations. Results are stored under a reusable architecture namespace for ongoing dependency management.

Automated architecture boundary checks are limited to validating import dependencies between Domain, Application, and Infrastructure layers in TypeScript projects. They detect and report violations with file and symbol context but require manual review of proposed refactor fixes before applying patches.