Rules for writing and reviewing idiomatic, production-quality Rust (error handling, ownership/borrowing, API and type design, modules, testing, clippy/fmt, unsafe). Use whenever writing, refactoring, or reviewing Rust code, or when the user runs /rust-best-practices or asks "is this idiomatic Rust?".
Skills
npx skilld add shauntheking/rust-best-practices --allshauntheking/tech-note
Claude Code skill: one-page academic-style technical notes (HTML + PDF)
1 skill
npx skilld add shauntheking/tech-note --allBuild a one-page "technical note" in an academic-paper style — small-caps running head, big serif title with one highlighted phrase, abstract, a hero flow diagram on a lavender panel, numbered two-column sections, a booktabs table, and captioned figures — as a self-contained HTML file plus PDF. Use when the user asks for a technical note, a paper-style one-pager, "notes like this", or a visual explainer of a system, workflow, paper, tool, or concept.
Curated skills from @shauntheking. Checked GitHub just now