error-handling

Standardize typed error hierarchies and retry patterns across TypeScript, Python, and Go.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill error-handling-zescode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-handling
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/error-handling
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill error-handling-zescode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the lack of consistency in error management, preventing silent failures, unhandled exceptions, and poor user feedback in multi-language codebases.

Core Features & Use Cases

  • Typed Error Hierarchies: Provides patterns for creating structured, domain-specific error classes in TypeScript, Python, and Go.
  • Resilience Patterns: Implements retry logic with exponential backoff and circuit breakers to handle unreliable external dependencies.
  • Use Case: Use this to standardize how your API handles database connection timeouts, validation failures, and unexpected runtime crashes across different microservices.

Quick Start

Apply the error handling patterns to the current module by defining a base AppError class and implementing a consistent catch-and-log strategy for all external service calls.

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 patterns across TypeScript, Python, and Go?

To standardize error handling across TypeScript, Python, and Go, implement typed error hierarchies and consistent catch-and-log strategies. This ensures uniform API error contracts and safe exception propagation across different microservices in multi-language codebases.

What is the best way to handle API database connection timeouts and validation failures?

The best way to handle API database connection timeouts and validation failures is by defining a base domain-specific error class. This standardizes user-facing feedback loops and comprehensive server-side logging for unexpected runtime crashes.

How do you implement retry logic with exponential backoff for external dependencies?

Implement retry logic with exponential backoff by applying resilience patterns to external service calls. This mechanism prevents silent failures from unreliable dependencies by safely propagating exceptions and maintaining application stability.

Can I use these error handling patterns to create structured error classes in production environments?

Yes, you can use these patterns to create structured, domain-specific error classes in production environments. They facilitate robust application stability by enforcing consistent API error contracts and comprehensive server-side logging.

Why do my microservices experience silent failures and unhandled exceptions?

Microservices experience silent failures and unhandled exceptions due to a lack of consistency in error management. Standardizing typed error hierarchies and user-facing feedback loops prevents these issues and ensures robust application stability.