error-handling-patterns

Design language-agnostic error handling patterns for APIs and services.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/angga30/antigravity-skill-tech-lead --skill error-handling-patterns-angga30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-handling-patterns
Source: https://github.com/angga30/antigravity-skill-tech-lead/tree/main/error-handling-patterns
Command: npx skills add https://github.com/angga30/antigravity-skill-tech-lead --skill error-handling-patterns-angga30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a unified, language-agnostic framework for designing and implementing robust error handling across programming languages, enabling consistent semantics, clear debugging, and safer APIs.

Core Features & Use Cases

  • Cross-language philosophies: exceptions vs results, error codes, options/maybes, and custom error hierarchies.
  • Language-specific patterns and reusable templates for Python, TypeScript, Rust, and Go.
  • Best practices for retries, circuit breakers, logging, tracing, and user-facing error messages.
  • Use case: standardize error handling in microservices to reduce incident response time and improve incident postmortems.

Quick Start

Define a standard error model and apply the chosen pattern to a sample API call.

Frequently Asked Questions about error-handling-patterns

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

FAQPage Schema
What is the best way to standardize error handling across microservices?

Standardizing error handling across microservices requires a unified, language-agnostic framework that enforces structured patterns like custom error hierarchies, exceptions, and result types to ensure consistent semantics and clearer debugging.

How do I implement circuit breaker and retry patterns for fault-tolerant systems?

Implementing circuit breaker and retry patterns involves applying best practices for graceful degradation and fallbacks within service integrations, ensuring systems fail safely and recover automatically during transient faults or network disruptions.

Should I use exceptions or result types for robust API design?

Choosing between exceptions and result types for API design depends on the target language, where this framework provides cross-language philosophies comparing exceptions, error codes, and options to help you build safer, more predictable APIs.

Does this error handling framework provide concrete examples for Python, TypeScript, Rust, and Go?

Yes, the framework provides language-specific patterns and reusable templates for Python, TypeScript, Rust, and Go, offering clear guidance and concrete examples to implement robust error handling tailored to each language's semantics.

When do I need custom error types and structured logging in distributed systems?

You need custom error types and structured logging in distributed systems when you want to enforce structured patterns for debugging and tracing, which significantly reduces incident response time and improves postmortems.