This is a comprehensive guide to writing production-ready Rust code with strong opinions on the right way to do things. It covers ownership patterns to avoid unnecessary cloning, error handling with Result and the ? operator (using thiserror for libraries and anyhow for applications), modeling states as enums to make invalid states unrepresentable, and safe concurrency primitives. The examples are concrete and show both good and bad patterns side by side. Use this when you want to write idiomatic Rust that leverages the type system for safety rather than fighting the borrow checker, or when reviewing code to catch common antipatterns like unwrap in production or overly defensive cloning.
npx -y skills add affaan-m/everything-claude-code --skill rust-patterns --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
wshobson/agents