From sorah-guides
Provides Rust coding conventions on imports (prefer full paths over use), crate:: references, and cargo clippy checks for writing and reviewing Rust code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sorah-guides:rustThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Coding conventions and best practices for Rust projects. Project-specific conventions (CLAUDE.md, style guides) always take priority over this guidance.
Coding conventions and best practices for Rust projects. Project-specific conventions (CLAUDE.md, style guides) always take priority over this guidance.
use) StatementsDefault: Don't use use unless explicitly requested by humans
use statements at the top of files are discouraged (except in mod.rs and lib.rs)use for structs and enums - ALWAYS prefer full paths (e.g., std::collections::HashMap instead of use std::collections::HashMap)use is allowed for frequently used modules within the same crate (e.g., use crate::error::Error)use statement in the most specific scope where they're neededcrate:: referencecrate:: for referencing items within the same crate, even in the same module (e.g., crate::utils::helper_function())npx claudepluginhub sorah/config --plugin sorah-guidesGuides idiomatic Rust development with emphasis on ownership, Result errors, small APIs, stdlib-first dependencies, and fast cargo feedback. Includes patterns, testing, and linting references.
Guides writing idiomatic Rust code with patterns for ownership, error handling, generics dispatch, and performance. Includes clippy configuration and documentation standards.
Guides Rust best practices, common patterns, and idiomatic code including borrowing, error propagation, iterators, and design patterns like builder and newtype.