spring-boot-engineer

name	spring-boot-engineer
description	Use when someone needs to build or extend a Java backend using the Spring ecosystem — wiring up a new REST API, configuring security and authentication, connecting to a database via JPA, or setting up reactive endpoints with Spring Boot 3.x.
scenarios	["Build a REST API with Spring Boot including security, JPA, and error handling","Help me configure Spring Security for JWT-based authentication","Add caching, transaction management, and validation to our Spring Boot service","Spring Boot로 REST API를 만들어줘 — 시큐리티와 JPA 포함","JWT 인증을 위한 Spring Security 설정을 도와줘"]
compatibility	{"recommended":[],"optional":["think-tool"],"remote_mcp_note":"think-tool이 있으면 트랜잭션 경계 설계와 보안 설정 검토를 더 체계적으로 수행합니다. Claude 설정 → MCP Servers에서 remote SSE 엔드포인트를 추가하세요."}
license	MIT
metadata	{"author":"https://github.com/Jeffallan","version":"1.1.0","domain":"backend","triggers":"Spring Boot, Spring Framework, Spring Cloud, Spring Security, Spring Data JPA, Spring WebFlux, Microservices Java, Java REST API, Reactive Java","role":"specialist","scope":"implementation","output-format":"code","related-skills":"java-architect, database-optimizer, microservices-architect, devops-engineer"}

Spring Boot Engineer

When to Use / When Not to Use

Use when:

• Building REST controllers, JPA repositories, or service layers in Spring Boot 3.x
• Configuring Spring Security 6, OAuth2, or JWT authentication
• Setting up Actuator, health probes, or Spring Cloud components

Do not use when:

• Architecture-level service decomposition decisions (use microservices-architect)
• Kotlin-idiomatic concerns (pair with kotlin-specialist)

Process

1. Analyze requirements — Identify service boundaries, APIs, data models, security needs
2. Design architecture — Plan data access, cloud integration, security; confirm before coding
3. Implement — Create services with constructor injection and layered architecture
4. Secure — Add Spring Security, OAuth2, method security, CORS; verify security rules compile and tests pass
5. Test — Write unit, integration, and slice tests; run ./mvnw test and confirm all pass
6. Deploy — Configure Actuator health checks; validate /actuator/health returns UP

Output Template

For each Spring Boot feature, provide:

1. Entity with validation annotations
2. Repository interface extending JpaRepository
3. Service with constructor injection and @Transactional
4. REST controller with @Valid input and @RestControllerAdvice
5. Test slice (@WebMvcTest or @DataJpaTest)

What Claude Does / What You Do

Claude	You
Generates layered architecture scaffolding	Provide domain requirements and data model
Configures Spring Security rules and JWT setup	Verify auth behavior in your environment
Writes @Transactional boundaries and JPA queries	Run tests and confirm correct data behavior
Sets up Actuator endpoints and health indicators	Connect to your monitoring stack