error-patterns

name	error-patterns
description	Provides error classification, recovery, and graceful-degradation patterns. Use when implementing error handling or debugging resilience failures in any skill.
alwaysApply	false
category	infrastructure
tags	["errors","error-handling","recovery","resilience","debugging"]
dependencies	["usage-logging"]
provides	{"infrastructure":["error-handling","error-classification","recovery"],"patterns":["graceful-degradation","error-logging","debugging"]}
usage_patterns	["error-handling","resilience-patterns","debugging-workflows"]
complexity	beginner
model_hint	fast
estimated_tokens	450
progressive_loading	true
modules	["modules/classification.md","modules/recovery-strategies.md","modules/agent-damage-control.md"]

Table of Contents

• Overview
• When to Use
• Error Classification
• By Severity
• By Recoverability
• Quick Start
• Standard Error Handler
• Error Result
• Common Patterns
• Authentication Errors (401/403)
• Rate Limit Errors (429)
• Timeout Errors
• Context Too Large (400)
• Integration Pattern
• Detailed Resources
• Exit Criteria

Error Patterns

Overview

Standardized error handling patterns for consistent, production-grade behavior across plugins. Provides error classification, recovery strategies, and debugging workflows.

When To Use

• Building resilient integrations
• Need consistent error handling
• Want graceful degradation
• Debugging production issues

When NOT To Use

• Project doesn't use the leyline infrastructure patterns
• Simple scripts without service architecture needs

Error Classification

By Severity

Level	Action	Example
Critical	Halt, alert	Auth failure, service down
Error	Retry or secondary strategy	Rate limit, timeout
Warning	Log, continue	Partial results, deprecation
Info	Log only	Non-blocking issues

By Recoverability

class ErrorCategory(Enum):
    TRANSIENT = "transient"      
    PERMANENT =        
    CONFIGURATION =       
    RESOURCE =