Java Rules

java-spring-lombok

Follow these rules when generating or modifying code:

- Implement a function, class, or endpoint with a single, explicit responsibility.
- Use Spring Boot best practices and Clean Code principles.
- Use Lombok by default to remove boilerplate (e.g. @RequiredArgsConstructor, @Getter, @Value, @Builder, @Slf4j).
- Use constructor-based dependency injection and keep dependencies immutable (final fields).
- Keep controllers thin: HTTP orchestration only, no business logic.
- Organize code by feature/bounded context, not by technical layers.
- Modify only the explicitly specified files or paths.
- Do NOT add code comments. Express intent through clear naming, small methods, and explicit types.
- Respect existing project conventions, architecture, and tests.
- Add unit or integration tests when behavior changes.
- Provide documentation or migration notes outside the code when APIs, configs, or contracts change.
- If assumptions are required due to missing context or tooling, list them first before implementing.