rust-learning

This skill should be used when the user explicitly wants mechanical, repetitive Rust boilerplate written for them — things like impl Display, impl From, thiserror error enums, clap structs, serde annotations, Cargo.toml dependency blocks, or impl Default. Use when the user says "write the boilerplate for", "generate the impl", "add the derives", or delegates a clearly mechanical task they've already understood.

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.

This skill should be used when the user explicitly wants a specific todo!() stub implemented for them. Use when the user says "fill in this todo", "implement this one for me", "you can write this part", "I'm delegating this stub", or points at a specific unimplemented function they want completed. Implements only the targeted stub — nothing else.

This skill should be used when the user is stuck on a Rust problem and wants a nudge in the right direction without being given the answer. Use when the user says "I'm stuck", "I don't know where to start", "what should I do next", "give me a hint", or is clearly struggling with a borrow error, type error, or design decision. Gives the minimum useful guidance to unblock — not the solution.

This skill should be used when the user wants feedback on Rust code they have written. Use when the user asks to "review", "check", "look at", "critique", or "give feedback on" their code, or after they finish implementing something and want to know if it's idiomatic, correct, or could be improved. This is a teaching review — not a rewrite.