clean-architecture-guardian

Clean architecture layer separation enforces unidirectional dependency rules between code layers. This Skill automatically validates that dependencies flow correctly—C# to F# is allowed from UI/Application layers to Domain, while F# to C# cross-layer calls are blocked—preventing architectural decay and circular references across your codebase.

Yes. Namespace hierarchy validation ensures your code adheres to bounded-context-specific and layered structures, improving organization. This Skill checks namespace conformance during new implementations and refactoring, catching violations before code review and maintaining clean separation of concerns without manual inspection.

F# compilation order errors occur when files reference code not yet compiled due to forward references. This Skill verifies correct F# file ordering automatically, detecting compilation order violations before they cause build failures and ensuring your mixed-language project compiles without warnings.

Architectural compliance scoring depends on layer separation, dependency direction rules, namespace hierarchy, and build cleanliness. This Skill automates conformance checks against Phase B1 standards, detecting violations during feature completion and issue remediation to reach and maintain 97+ quality scores without manual review.

Yes. Circular dependency detection identifies bidirectional or multi-hop dependency cycles that violate clean architecture. This Skill scans your F# and C# codebase for forbidden circular references across layers and namespaces, flagging violations to break cycles before they compromise system design.