What problem does it solve?
It prevents inconsistent and ad-hoc error responses by providing a clear strategy for handling validation failures, expected business outcomes, and unexpected exceptions in .NET 10 APIs.
Core Features & Use Cases
- Use the Result pattern for expected failures to represent business-rule outcomes like “order not found” or “validation failed” without throwing exceptions.
- Return RFC 9457 ProblemDetails for every API error so clients receive consistent
type, title, status, detail, and optional errors.
- Validate at the boundary using FluentValidation and endpoint filters to catch invalid requests early and map validation failures to standard error responses.
- Centralize unexpected exceptions with a global exception handler that logs and converts crashes into safe ProblemDetails responses (including development-friendly detail).
Quick Start
Load the error-handling skill and implement your API endpoints so expected failures use Result-to-ProblemDetails mappings while unexpected exceptions are caught globally and returned as ProblemDetails.