java-springboot

What problem does it solve? When building or reviewing the Spring Boot server layer of the SIFAP 2.0 modernization (Java 21, PostgreSQL 16), developers need consistent, idiomatic structure. This Skill provides a quick checklist of best practices so controllers, services, and repositories follow the same conventions enforced by CI. ## Core Features & Use Cases - Feature-sliced structure: Organizes code by domain (e.g., com.sifap.payment) with constructor injection and immutable private final dependencies. - Layer conventions: Enforces record DTOs with Bean Validation at controller boundaries, @Transactional only on services, and Spring Data JPA repositories with projections. - Configuration and security: Guides externalized configuration with @ConfigurationProperties, Spring profiles, and secret management via environment variables or Azure Key Vault. - Use Case: Ask the assistant to scaffold a new feature slice (controller, service, repository) for a payment module, and it produces an idiomatic /api/v1 endpoint with a record DTO, a transactional service, and a JpaRepository. ## Quick Start Ask the assistant to create the structure of a new feature slice with controller, service, and repository for your Spring Boot module following these best practices.