error-handling

Name: error-handling
Availability: InStock
Author: jorgeochipinti97

Standardize error handling with typed error hierarchies and RFC 7807 payloads.

Updated Jan 22, 2026

Search Tags:#frontend #logging #backend #error-handling #typing #problem-details #RFC7807

Ready to run

npx skills add https://github.com/jorgeochipinti97/dublin-skills --skill error-handling-jorgeochipinti97

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: error-handling
Source: https://github.com/jorgeochipinti97/dublin-skills/tree/main/skills/implementation/error-handling
Command: npx skills add https://github.com/jorgeochipinti97/dublin-skills --skill error-handling-jorgeochipinti97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Errors are features. They inform the user, guide recovery, and let operators fix what's broken. Bad error handling hides bugs and degrades UX — treat it with the same rigor as the happy path.

Core Features & Use Cases

Typed error hierarchy (ValidationError, NotFoundError, etc.) to distinguish user vs. system failures.
Global error handling and UI fallbacks with RFC 7807-style Problem Details and structured logging for observability.
React error boundaries and backend error mapping to surface actionable messages without leaking internal details.

Quick Start

Deploy a typed error hierarchy, a global error handler, and React/NestJS error boundaries to standardize error responses and user notifications.

Frequently Asked Questions about error-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize error handling across frontend and backend applications?▼

Standardize error handling by deploying a typed error hierarchy, a global error handler, and UI error boundaries to map backend failures to consistent user notifications without leaking internal details.

What is the best way to implement RFC 7807 Problem Details for API errors?▼

Implement RFC 7807 Problem Details by mapping typed errors to standardized response payloads, ensuring your global error handler outputs structured problem details for consistent frontend parsing.

How do I create a typed error taxonomy to distinguish user vs system failures?▼

Create a typed error taxonomy by defining specific error classes like ValidationError and NotFoundError, allowing your application to distinguish between user input failures and internal system issues.

How does structured logging with correlation IDs improve error observability?▼

Structured logging with correlation IDs improves error observability by tracking requests across frontend boundaries and backend services, allowing operators to trace exact failure points during incidents.

Can I use React error boundaries to surface actionable error messages?▼

Yes, you can use React error boundaries to catch UI failures and surface actionable user-facing messages, preventing application crashes while safely hiding sensitive internal stack traces.

Why should I avoid leaking internal details in user-facing error messages?▼

Avoid leaking internal details in error messages to prevent security vulnerabilities, ensuring your global error handler maps backend failures to safe, user-friendly messages that guide recovery.