How does this skill help with Rust error handling?

It provides a systematic framework for categorizing errors and choosing recovery strategies, moving beyond simple syntax to architectural design.

Does it support common Rust error crates?

Yes, it provides specific implementation guidance for thiserror, anyhow, tokio-retry, and failsafe-rs.

Can I use this for designing public APIs?

Absolutely. It focuses on distinguishing between user-facing errors (actionable) and internal system errors (logged) to improve API usability and security.

What recovery patterns are included?

The skill covers retries with backoff, fallbacks for degraded modes, circuit breakers to prevent cascading failures, and timeouts.

Domain Error Strategy for Rust

Name: Domain Error Strategy for Rust
Author: lywa1998

bylywa1998

API 개발

Guides the design and implementation of robust error handling architectures and recovery strategies in Rust applications.

소개

This skill provides a comprehensive framework for categorizing and managing errors in Rust projects, moving beyond simple error types to strategic decision-making. It helps developers determine the appropriate audience for errors—distinguishing between user-facing, internal, and system-level failures—while providing implementation patterns for recovery strategies like exponential backoff, circuit breakers, and fallbacks. By utilizing industry-standard crates like thiserror and anyhow, it ensures that your domain logic remains resilient, debuggable, and user-friendly.

주요 기능

Implementation patterns for retries with exponential backoff and jitter
0 GitHub stars
Audience-based error categorization for users, developers, and operators
Resilience strategies including circuit breakers, timeouts, and bulkheads
Structured error hierarchy design using thiserror and anyhow
Best practices for avoiding anti-patterns like string errors and unhandled panics

사용 사례

Implementing transient failure recovery for external microservices
Creating clear, actionable error payloads for frontend consumption
Designing production-grade error handling for distributed web APIs

소개

주요 기능

Implementation patterns for retries with exponential backoff and jitter
0 GitHub stars
Audience-based error categorization for users, developers, and operators
Resilience strategies including circuit breakers, timeouts, and bulkheads
Structured error hierarchy design using thiserror and anyhow
Best practices for avoiding anti-patterns like string errors and unhandled panics

사용 사례

Implementing transient failure recovery for external microservices
Creating clear, actionable error payloads for frontend consumption
Designing production-grade error handling for distributed web APIs