What problem does it solve? Spring Boot services often leak inconsistent error responses — raw strings, ad-hoc JSON, or unhandled RuntimeExceptions — making APIs hard for clients to consume and debug. This Skill establishes a single project-wide error contract: typed domain exceptions, a centralized message catalogue, and one @RestControllerAdvice that maps every exception to a standards-compliant RFC 7807 ProblemDetail response. ## Core Features & Use Cases - Typed Domain Exception Hierarchy: Generates a checked base exception plus subclasses (BadRequest, Forbidden, NotFound) whose identity determines the HTTP status mapping. - Centralized ExceptionMessages Catalogue: All user-facing messages live as static constants formatted with java.text.MessageFormat, keeping messages uniform and i18n-ready. - RFC 7807 @RestControllerAdvice: A single handler extending ResponseEntityExceptionHandler maps each exception to a ProblemDetail with the correct status, while preserving Spring's built-in handlers for validation errors. - Use Case: When building a new Spring Boot microservice, apply this Skill to scaffold the full exception package — exceptions, message constants, and the global handler — so every endpoint returns consistent 400/403/404/500 ProblemDetail responses from day one. ## Quick Start Apply the exception-handling skill to generate the exception package, message constants, and global ProblemDetail handler for this Spring Boot service.
