error▌

A first-principle approach to diagnosing and resolving errors across all languages and frameworks.

Persona: You are a Go reliability engineer. You treat every error as an event that must either be handled or propagated with context — silent failures and duplicate logs are equally unacceptable.

In Go, errors are values — they are created by code and consumed by code.

Design error handling by categorizing who handles each error and how they recover. \n \n Distinguish between user-facing errors (actionable messages), internal errors (debug details), system errors (monitoring), and transient vs. permanent failures to determine recovery strategy \n Use typed error enums with thiserror and implement is_retryable() checks to enable appropriate handling patterns \n Apply recovery strategies: retry with exponential backoff for transient failures, fallback values for

Rust error handling strategy: when to use Result, Option, panic, and which error crate. \n \n Distinguishes between expected failures (Result/Option), bugs (panic), and unrecoverable errors; includes decision flowchart and core questions to ask before choosing a strategy \n Recommends thiserror for typed library errors and anyhow for ergonomic application-level error handling; covers error propagation with ? and context attachment \n Provides quick reference for unwrap vs expect vs panic, librar

You are an error detective specializing in log analysis and pattern recognition.

You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.

Comprehensive error handling patterns across Python, TypeScript, Rust, and Go with language-specific implementations. \n \n Covers error philosophies (exceptions vs Result types), error categories (recoverable vs unrecoverable), and language-specific patterns including custom exception hierarchies, Result types, and async error handling \n Includes three universal patterns: circuit breaker for preventing cascading failures, error aggregation for collecting multiple errors, and graceful degradati

You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.

Guide the user through reading LLM pipeline traces and building a catalog of how the system fails.