Refactor Rust code to idiomatic patterns with anyhow and thiserror.
npx skills add https://github.com/RambleRainbow/jd --skill rust-patterns-ramblerainbow
Please help me install this Agent Skill. Skill: rust-patterns Source: https://github.com/RambleRainbow/jd/tree/main/.claude/skills/rust-patterns Command: npx skills add https://github.com/RambleRainbow/jd --skill rust-patterns-ramblerainbow
This Skill solves the common pain points of writing non-idiomatic Rust code that triggers avoidable borrow checker errors, runtime panics from improper error handling, and unmaintainable module structures, enabling developers to fully leverage Rust's compile-time safety and performance guarantees without steep trial and error.
Use the rust-patterns skill to refactor your existing Rust application's error handling to replace all unwrap() calls with proper Result propagation using anyhow, and restructure your src directory to organize modules by business domain instead of file type.
High-intent search queries and answers about installing and using this skill.
Fix borrow checker errors by applying idiomatic Rust ownership and borrowing rules to restructure data access. This eliminates non-idiomatic patterns, ensuring compile-time safety guarantees without unnecessary clones.
The best way to handle errors is replacing unwrap() calls with structured Result propagation using anyhow and thiserror. This eliminates runtime panics by enforcing safe error handling patterns.
Refactor legacy Rust code by restructuring the src directory to organize modules by business domain instead of file type. This eliminates unmaintainable module structures and standardizes domain organization.
You need safe concurrency primitives when implementing parallel execution to prevent data races. Utilizing vetted community-aligned templates ensures safe concurrent operations without triggering runtime panics.
Yes, exhaustive enum pattern matching is fully supported for robust state modeling. It enforces compile-time checks to handle all possible enum variants, preventing unhandled state bugs.
Using unsafe code bypasses compile-time safety guarantees, so it requires strict usage rules to prevent security vulnerabilities. Explicit anti-pattern guidance and tooling like cargo clippy must be applied.
laurigatesAssist with modern Rust development using cargo, rustc, clippy, and rustfmt.
r3bl-orgRun clippy, cargo fmt, and module checks on Rust workspaces.
sehoon787Enforce ownership, error handling, and concurrency patterns in Rust code.
iammarkpsAnalyze Rust source files for safety, correctness, and idiomatic patterns.
