enforcement

You can enforce architectural integrity during PR reviews by validating the 4-layer module structure (domain, infrastructure, application, ui) and checking dependency rules. This Skill applies provider-agnostic factory patterns and mandates T | Error returns to prevent structural drift.

The best way to standardize error handling patterns across feature modules is to enforce T | Error return types and apply centralized guardrails. This Skill ensures all feature modules adopt consistent error handling conventions and standardized naming during module creation and audits.

The provider-agnostic factory pattern works by using CONFIG.SERVICE_PROVIDER to inject dependencies without coupling to specific implementations. This Skill validates the factory pattern during architectural audits to ensure dependency rules and clean architecture boundaries are maintained across modules.

Yes, you can use architectural enforcement for module creation, PR reviews, and code quality audits. This Skill provides centralized guardrails that validate the 4-layer structure, enforce naming conventions, and check cross-cutting enforcement rules to ensure adherence to best practices.

Your module structure fails architectural integrity checks when it violates the mandated 4-layer layout (domain, infrastructure, application, ui) or breaks dependency rules. This Skill identifies non-compliant cross-cutting patterns, missing provider factory implementations, and incorrect T | Error return types.