What problem does it solve? Spring Boot applications without centralized exception handling return inconsistent error responses, leak stack traces, and force developers to duplicate try-catch logic across controllers. This Skill provides a complete pattern for custom domain exceptions mapped to standardized HTTP error responses. ## Core Features & Use Cases - Base Exception Hierarchy: Create a BaseException with ExceptionType (CLIENT_EXCEPTION / SERVER_EXCEPTION) plus eight business exceptions covering HTTP 400, 401, 403, 404, 409, 429, 500, and 501. - Global REST Handler: A @RestControllerAdvice class that intercepts custom exceptions, Spring validation errors, security exceptions, and database lock exceptions, returning a consistent { "type", "message" } JSON body. - OpenAPI Integration: Add ExceptionResponse schemas to api.yml and reference standardized error responses on every endpoint. - Use Case: When building a Spring Boot REST API with JWT security and @PreAuthorize role checks, use this Skill so that AccessDeniedException automatically becomes a 403 response and NotFoundException thrown in services becomes a clean 404 JSON body. ## Quick Start Implement custom exception handling with a global REST exception handler in my Spring Boot project following the clean architecture pattern.
