While building the software, we all agree, as a team, to follow a set of guidelines which are typically considered as best practices.
But during the development, developers might violate those guidelines unknowingly or ignorance.
Typically, we rely upon code reviews or code quality checking tools like SonarQube, PMD, etc. to check for such violations.
But some of the guidelines could be opinionated decisions which might not be able to automate using SonarQube, PMD etc.

Test

ArchUnit is a Java testing library that lets you enforce architectural rules as JUnit tests. Five practical examples are shown: preventing service/repository layers from depending on the web layer, enforcing layered architecture access rules, banning Spring field injection in favor of constructor injection, enforcing class naming conventions, and restricting usage to JUnit 5 only. The DSL reads like plain English, making the rules easy to understand and maintain alongside the codebase.

Imposing Code Structure Guidelines using ArchUnit

Rule 1: Services and Repositories should not talk to Web layer

Rule 2: Should follow Layered Architecture

Rule 3: Spring’s @Autowired should NOT be used with Field based injection