problem-details-rfc9457
FeaturedUse when implementing error handling, exception mappers, or error response formatting. Enforces RFC 9457 (Problem Details for HTTP APIs) using Spring's built-in ProblemDetail.
Install
Quality Score: 88/100
Skill Content
Details
- Author
- rrezartprebreza
- Repository
- rrezartprebreza/spring-boot-skills
- Created
- 5 months ago
- Last Updated
- 5 days ago
- Language
- Java
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
problem-details-error-design
Playbook for designing a consistent RFC 9457 Problem Details error model — type URIs, extension members, status code mapping, and a catalog template. Prevents per-endpoint bespoke error shapes.
error-envelope
This skill should be used when the user mentions "error handling", "problem details", "rfc 9457", "rfc 7807", "request validation", "api errors", "zod", "pydantic", "class-validator", "error response format", "problem+json", "validation error", or making an API return consistent, machine-readable errors. It provides the RFC 9457 Problem Details envelope and idiomatic per-stack request-validation patterns.
controller-advice-style
The house style for error responses of a Spring MVC REST application - `@RestControllerAdvice`, `@ExceptionHandler`, `ProblemDetail` (RFC 9457), `ResponseEntityExceptionHandler`, `AuthenticationEntryPoint`, `AccessDeniedHandler`. Load it before writing or changing any of them, when a new exception has to reach the client, when shaping validation `errors`, and when an endpoint returns 403 where 401 was expected, a `@PreAuthorize` denial comes back as 500, a status is lost to a catch-all handler, one module's exception is answered by another module's advice, or an error body has its fields nested under `properties`. Not for the controllers themselves (the separate `controller-style` skill) and not for documenting errors in Swagger (the separate `swagger-style` skill).