Name: Error Handling
Author: lgili

Error Handling

Error-first patterns specialist for writing robust, predictable code that fails loudly with actionable messages and recovers gracefully where appropriate. Use when writing functions that call external APIs, parse user input, access the filesystem, perform database operations, or any logic where failure is possible. Trigger for asks like "add error handling", "handle failures", "what if this fails", "make this more robust", "add validation", "improve error messages", or when reviewing code that uses bare try/catch, ignores error returns, or has deeply nested conditionals.

lgili0 스타2026. 4. 8.

직업
카테고리: 프레임워크 내부 구조

Overview

Use this skill to write code that fails loudly, recovers predictably, and produces error messages that tell users and operators exactly what went wrong and what to do.

Core Workflow

Enumerate all failure modes.
- List every way the function or operation can fail.
- Classify: expected (invalid input, not found, timeout) vs unexpected (bug, infra failure).
- Decide which failures are recoverable (retry, fallback, user correction) vs fatal (abort).
Apply guard clauses at function entry.
- Validate inputs at the top of the function before any logic runs.
- Return or throw immediately on invalid input — don't let bad data propagate deep.
- Keep the happy path at the lowest nesting level (flipped conditionals pattern).
Design typed error classes.
- Use named error classes for each expected failure domain.
- Include structured context in the error: field name, received value, expected format.

Overview

Use this skill to write code that fails loudly, recovers predictably, and produces error messages that tell users and operators exactly what went wrong and what to do.

Core Workflow

Enumerate all failure modes.
- List every way the function or operation can fail.
- Classify: expected (invalid input, not found, timeout) vs unexpected (bug, infra failure).
- Decide which failures are recoverable (retry, fallback, user correction) vs fatal (abort).
Apply guard clauses at function entry.
- Validate inputs at the top of the function before any logic runs.
- Return or throw immediately on invalid input — don't let bad data propagate deep.
- Keep the happy path at the lowest nesting level (flipped conditionals pattern).
Design typed error classes.
- Use named error classes for each expected failure domain.
- Include structured context in the error: field name, received value, expected format.

Topic	Reference	Load when
Error patterns	`references/error-patterns.md`	Guard clauses, early returns, result types, error classification
Error messages	`references/error-messages.md`	Writing clear, actionable, non-leaking error messages
Language-specific	`references/error-by-language.md`	TypeScript, Python, Go, Rust — idiomatic error handling per language

Error Handling

Overview

Core Workflow

Error Handling

Overview

Core Workflow

Reference Guide

Constraints

MUST DO

MUST NOT DO

Output Template

References

Pytorch Patterns

Regex Vs Llm Structured Text

Effect

Flags

WPF to WinUI 3 Migration Skill

At Dispatch V2