Convert .NET failures and exceptions into RFC 9457 ProblemDetails responses.
npx skills add https://github.com/shahdanish/vibepos --skill error-handling-shahdanish
Please help me install this Agent Skill. Skill: error-handling Source: https://github.com/shahdanish/vibepos/tree/main/skills/error-handling Command: npx skills add https://github.com/shahdanish/vibepos --skill error-handling-shahdanish
It prevents inconsistent, hard-to-debug error responses in .NET applications by standardizing how expected failures and unexpected exceptions are transformed into RFC 9457 ProblemDetails.
Result/Result<T> to represent business-rule outcomes like “not found” or “validation failed” without throwing exceptions.ProblemDetails responses that include type, title, status, detail, and optional errors.ValidationProblem details via endpoint filters.Load this skill when implementing error handling, validation, or API error contracts in your .NET 10 endpoints so your failures consistently return RFC 9457 ProblemDetails.
High-intent search queries and answers about installing and using this skill.
Standardize .NET API error responses by converting expected failures and unexpected exceptions into consistent RFC 9457 ProblemDetails payloads. This approach replaces inconsistent error formats with structured responses containing type, title, status, and detail fields.
The Result pattern represents business-rule outcomes like validation failures using Result or Result<T> objects instead of throwing exceptions. This allows typed mapping to structured ProblemDetails responses for predictable error handling.
Configure FluentValidation at the API boundary using endpoint filters to intercept invalid requests and return structured ValidationProblem details. This ensures validation failures consistently map to RFC 9457 ProblemDetails responses.
A global exception handler catches unexpected exceptions once, logs the details, and returns a safe 500 response. It provides optional development-only detail to prevent sensitive error detail leakage in production environments.
Yes, this RFC 9457 ProblemDetails error handling approach applies directly to .NET 10 endpoints. It integrates boundary validation, Result pattern mapping, and global exception handling to return consistent API error contracts.
Mapping Result patterns to typed ProblemDetails prevents inconsistent, hard-to-debug error responses. It standardizes API error contracts by transforming expected failures and unexpected exceptions into structured RFC 9457 payloads.
thapaliyabikendraImplement advanced C# patterns and .NET 10 performance optimizations.
cbbkrd-techConfigure global exception handling middleware for ASP.NET Core and FastAPI.
sayedihashimiDesign ASP.NET Core Minimal APIs with route groups, endpoint filters, and TypedResults.
Maj3D10Convert .NET 10 API failures into RFC 9457 ProblemDetails responses.