Senior Java Development Architect

What It Solves

In Spring Boot backend projects, much of the day-to-day work is not simply writing one feature, but repeatedly setting up pom.xml, filling in application.yml, generating Entity/Mapper/Service/Controller/DTO/VO classes, adding Redis, RabbitMQ, or Spring Security, and then completing tests and API docs. Without shared conventions, teams easily end up with Controllers calling Mappers directly, scattered exception handling, missing DTO/VO separation, or amount fields typed as double. This skill consolidates Spring Boot scaffolding, code generation, integration guidance, and review checklists into one workflow, aiming for clearer structure, better testability, and maintainability.

How It Works

After a trigger, the skill classifies the task: create a project, generate a CRUD module, integrate middleware, write tests, generate docs, refactor, or review code. If a project already exists, it first reads pom.xml / build.gradle, package layout, and existing modules before selecting the relevant path. Core steps include:

• Spring Boot scaffolding: defaults to Maven, Spring Boot 3.2.x, and Java 17; generates pom.xml, application.yml, the main class, README.md, and shared Result / GlobalExceptionHandler templates.
• CRUD generation: creates entity, mapper, service, controller, dto, vo, and test stubs from module fields and persistence choices; defaults to MyBatis-Plus, with MyBatis or JPA as alternatives.
• Middleware integration: supports Redis, RabbitMQ, Kafka, and Spring Security, generating version-aware configuration, producers/consumers, and JWT flows when requested.
• Testing and docs: Controller tests can use @WebMvcTest + MockMvc, Service tests can use Mockito, and persistence tests can use @DataJpaTest; API docs can be emitted as Markdown from Controllers, or enhanced with springdoc-openapi.
• Code review: checks layered architecture, exception handling, validation, logging, security, and naming conventions, then provides before/after snippets.

Boundaries

It is best suited for Spring Boot backend initialization, module generation, and normalization of maintenance work, especially around MyBatis/MyBatis-Plus/JPA, Redis, messaging, and security integration. It does not replace business modeling, architecture decisions, or production deployment judgment. For complex domain models, multi-tenancy, distributed transactions, or custom middleware policies, review output against the existing system. Keep compile and unit-test validation enabled, and expect its defaults to differ from team-specific standards.