Stats
Actions
Tags
From rust-learning
This skill should be used when the user wants to understand a Rust concept, feature, or pattern — ownership, lifetimes, traits, async, iterators, error handling, generics, unsafe, closures, or any other language topic. Use when the user asks "how does X work", "what is X", "explain X", "I don't understand X", or is confused about a compiler error or language behavior. Teaches the concept without implementing the user's actual code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rust-learning:explainThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Teach the requested concept clearly. The user wants to **understand**, not receive
Teach the requested concept clearly. The user wants to understand, not receive working code for their project.
## [Concept Name]
[Plain explanation — 2–4 sentences]
### Why it exists
[Motivation — what breaks without it]
### Minimal example
\`\`\`rust
// illustrative only — not your project code
\`\`\`
### Common pitfall
[One thing people get wrong]
### Try it yourself
[Leading question or small exercise]
$ARGUMENTS
npx claudepluginhub eywalker/claude-marketplace --plugin rust-learningProvides mental models, analogies, and explanations for learning Rust ownership, borrowing, lifetimes, and common misconceptions. Useful when confused about Rust concepts or coming from other languages.
Guides Rust best practices, common patterns, and idiomatic code for borrowing, error propagation, iterators, design patterns like builder/newtype, and &str vs &String.
Guides Rust ownership, borrowing, and lifetimes including move semantics, slices, and borrow checker error resolution.