error-handling

Implement try/catch patterns, toast notifications, HTTP error categorization, and logging.

Updated Nov 18, 2025
One-click install
npx skills add https://github.com/twhitehead-blackdog/People --skill error-handling-twhitehead-blackdog
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: error-handling
Source: https://github.com/twhitehead-blackdog/People/tree/main/.agent/skills/error-handling
Command: npx skills add https://github.com/twhitehead-blackdog/People --skill error-handling-twhitehead-blackdog

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides standardized patterns and tools to effectively manage, display, and log errors within an application, ensuring a smoother user experience and easier debugging.

Core Features & Use Cases

  • Centralized Error Handling: Implement try/catch blocks with dedicated error handling functions.
  • User Feedback: Utilize a MessageService for displaying toast notifications (success, error, warning) to the user.
  • HTTP Error Categorization: Differentiate and present user-friendly messages for common HTTP status codes (400, 401, 403, 404, 500).
  • Logging: Integrate a LoggerService for detailed error logging for developers.
  • Form Validation Feedback: Provide specific warnings for invalid form fields.
  • Retry Mechanisms: Implement automatic retries for transient errors.

Quick Start

Use the error-handling skill to display a success message to the user.

Frequently Asked Questions about error-handling

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

FAQPage Schema
How do I handle HTTP errors and display user-friendly toast notifications?โ–ผ

Handle HTTP errors by categorizing status codes like 400, 401, 403, 404, and 500, then displaying user-friendly toast notifications through a centralized MessageService to ensure smoother application UX.

What is the best way to implement try/catch patterns for centralized error logging?โ–ผ

Centralized error logging uses try/catch blocks integrated with a LoggerService to capture detailed developer-facing error information, ensuring robust application debugging and standardized error management.

How do I show form validation feedback for specific invalid fields?โ–ผ

Form validation feedback provides specific warnings for invalid fields by utilizing reusable code snippets that manage user-facing error information directly within the application's form inputs.

Can I implement automatic retries for transient HTTP errors?โ–ผ

Yes, you can implement automatic retry mechanisms specifically designed to recover from transient HTTP errors, facilitating robust application development without requiring manual user intervention.

Does this error handling approach work for both user-facing and developer-facing errors?โ–ผ

Yes, this error handling approach manages both user-facing toast notifications and developer-facing logging, providing comprehensive strategies to effectively display and log application errors.

When should I use centralized error handling instead of inline try/catch blocks?โ–ผ

Use centralized error handling instead of inline try/catch blocks when you need standardized patterns, reusable code snippets, and dedicated functions to manage HTTP error categorization and application-wide logging.