expert-arch-enforcer

Architecture boundary enforcement monitors predefined invariants to prevent dependency violations. It checks module dependencies, data validation, naming conventions, and file size constraints to stop architecture drift across multi-layer codebases.

The six-layer dependency model structures code into Types, Config, Repo, Service, Runtime, and UI layers. It enforces forward-only dependencies between these layers to maintain strict architectural integrity and prevent circular references.

You can check module boundaries by triggering architecture or dependency checks. The system validates entry parameters, enforces module boundary communication, and detects naming convention or file size violations automatically.

Yes, architecture checks support PR integration for remediation. When dependency direction violations or boundary breaches are detected, the system outputs repair suggestions directly within your pull request workflow.

Yes, the architecture enforcement tool supports Chinese triggers for static analysis. You can initiate module boundary checks and dependency checks using Chinese commands to fit localized development workflows.

Configurable thresholds for code quality enforcement require predefined invariants to be established before checking. Without explicit boundary rules and size constraints configured, the static analysis cannot detect architecture drift or generate remediation reports.