How does this skill handle unwrap() calls?

The skill provides a 'Trace Down' approach to replace dangerous unwraps with the '?' operator, match blocks, or descriptive .expect() calls that document why a failure is considered an invariant violation.

When should I use anyhow versus thiserror?

Use 'thiserror' when building libraries where callers need to match on specific error types. Use 'anyhow' for application code where you want easy error propagation and the ability to add context without defining custom structs for every error.

Can this skill help with custom error types?

Yes, it includes patterns for designing domain-specific error variants and mapping lower-level errors (like io::Error) into high-level business logic errors.

Does it provide guidance on when to panic?

Absolutely. It follows a strict logic: use Result for expected failures (like a missing file) and panic! only for unrecoverable bugs or broken internal invariants.

Rust Error Handling Expert

Name: Rust Error Handling Expert
Author: lywa1998

bylywa1998

開発者ツール

Implements idiomatic Rust error handling strategies using Result, Option, and industry-standard crates like anyhow and thiserror.

概要

This skill equips Claude with a comprehensive framework for navigating Rust's sophisticated error handling ecosystem. It provides structured guidance on choosing between recoverable and unrecoverable errors, implementing custom error types for libraries using thiserror, and managing application-level failures with anyhow. By applying these patterns, developers can ensure their code is robust, maintainable, and provides clear context for troubleshooting, moving beyond simple unwraps to professional-grade error propagation and domain-specific error design.

主な機能

0 GitHub stars
Decision framework for choosing between Result, Option, and panic!
Guidelines for when to use unwrap() versus expect() with invariants
Standardized patterns for adding diagnostic info to error call chains
Best practices for the '?' operator and error propagation with context
Implementation patterns for 'anyhow' in applications and 'thiserror' in libraries

ユースケース

Designing public-facing library APIs with type-safe error variants
Adding meaningful context to application failures for better observability
Refactoring unsafe unwraps into robust error propagation patterns

概要

主な機能

0 GitHub stars
Decision framework for choosing between Result, Option, and panic!
Guidelines for when to use unwrap() versus expect() with invariants
Standardized patterns for adding diagnostic info to error call chains
Best practices for the '?' operator and error propagation with context
Implementation patterns for 'anyhow' in applications and 'thiserror' in libraries

ユースケース

Designing public-facing library APIs with type-safe error variants
Adding meaningful context to application failures for better observability
Refactoring unsafe unwraps into robust error propagation patterns