What problem does it solve? It standardizes how a full-stack ASP.NET Core and TypeScript application defines, returns, and displays errors, eliminating ad-hoc error strings, leaked stack traces, and inconsistent frontend error handling. ## Core Features & Use Cases - ErrorCode Enum + Registry: Define every error as an enum value with an [ErrorCodeInfo] attribute (HTTP status, user message, handling suggestion), cached in a singleton ErrorCodeRegistry for O(1) lookup. - RFC 7807 ProblemDetails Pipeline: ExceptionHandlerMiddleware and ControllerErrorExtensions.ProblemResult() return structured problem+json responses with traceId, never exposing SQL details or stack traces in production. - Frontend Integration: TypeScript isKnownErrorCode type guards, handleApiError with default strategies (login redirect, upgrade prompt, toast), plus preflight validator error code ranges for editor features. - Use Case: When adding a new API error, register it in ErrorCode.cs with its attribute, return it via ProblemResult in the controller, and the frontend automatically maps it to a localized user-facing toast. ## Quick Start Ask the AI to add a new error code for a failed operation and wire it through the backend ProblemResult response and frontend toast mapping following this skill's standards.