Enforce Java DDD four-layer architecture rules across Java source files.
npx skills add https://github.com/Xunzi229/skills --skill architecture-guard-xunzi229
Please help me install this Agent Skill. Skill: architecture-guard Source: https://github.com/Xunzi229/skills/tree/main/architecture-guard Command: npx skills add https://github.com/Xunzi229/skills --skill architecture-guard-xunzi229
Prevents improper layer dependencies, naming violations, and unsafe data flow in Java DDD and Clean Architecture projects so that Controllers, Application services, Domain, and Infrastructure responsibilities remain correctly separated and auditable.
Run an architecture check on the current module to detect layer dependency violations and receive suggested fixes for Controller, Application, Domain, and Infrastructure boundaries.
High-intent search queries and answers about installing and using this skill.
To detect forbidden cross-layer dependencies in a Java DDD project, scan Java source files to analyze imports and package usage, flagging violations like Controller-to-Mapper calls or Domain dependencies on external SDKs. This keeps layer boundaries auditable.
Enforcing DDD naming conventions for Request, Command, Query, DO, Entity, DTO, and BO requires static analysis that validates naming patterns against layer responsibilities. This ensures inserts and updates go through Domain Repository abstractions.
Yes, you can check architecture rules in a SpringBoot 2.1 and MyBatis-Plus codebase. The static analysis targets Java 11 projects to catch dependency violations during feature implementation, code reviews, or Service and Controller refactoring.
To fix a Controller directly calling a Mapper or Repository, create Application-layer orchestrations to mediate the request flow. The analysis flags these forbidden imports and proposes moving SQL or SDK calls to the infrastructure layer.
Your Domain layer breaks when depending on external frameworks because DDD rules require Domain code to remain isolated. Static scanning detects these forbidden imports and suggests defining Repository interfaces in the Domain layer instead.
Yes, static analysis works for refactoring Application and Service layers by detecting unsafe data flow and suggesting remediation. It provides actionable guidance to move SQL and SDK calls to the infrastructure layer, ensuring proper separation of responsibilities.
Xunzi229Generate Spring Cloud DDD business logic code for Java 11 projects.
ic-facetImplement Hexagonal Architecture layers in Java services with strict domain, application, and infrastructure boundaries.
WarLikeLauxInspect task implementations against project constitution and architectural principles.
agnaldo4jDetect and classify circular dependencies across Kotlin class, package, and Gradle module boundaries.
