rust-best-practices
Skill4 starsChanged 27 days agoNo licenceView on GitHub
Write idiomatic, robust, maintainable Rust. Use this skill whenever you write, review, refactor, debug, or explain Rust code: new crates, modules, functions, structs, traits, error types, async code, unsafe or FFI code, Cargo.toml, tests, or rustdoc. Trigger on any mention of Rust, cargo, crates, .rs files, the borrow checker, lifetimes, traits, clippy, or rustfmt, even when the user does not ask for "best practices" or "idiomatic" code. Synthesized from the Google Rust Style Guide, the Rust API Guidelines, Effective Rust, Rust Design Patterns, and Microsoft's Pragmatic Rust Guidelines.
46 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- linx-systems/clamuitheir own version, first seen Nov 9, 2026
- Cosmian/kmsedited, first seen Nov 9, 2026
- dirien/yet-another-agent-harnesstheir own version, first seen Nov 8, 2026
- crbnos/carbontheir own version, first seen Nov 7, 2026
- iyazerski/dev-flows-pluginedited, first seen Nov 1, 2026
- MaraniMatias/Mustertheir own version, first seen Nov 1, 2026
Used with
Projects with it also use rust-async-patterns, inngest and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
klauswgSkillrust-async-patterns
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
Also in 9 projects that use this
xfstudioSkillinngest
Inngest expert for serverless-first background jobs, event-driven workflows, and durable execution without managing queues or workers. Use when: inngest, serverless background job, event-driven workflow, step function, durable execution.
Also in 3 projects that use this
huialiSkillrust-testing
Also in 7 projects that use this
gihwan-devSkilltauri-v2
Tauri v2 cross-platform app development with Rust backend. Use when configuring tauri.conf.json, implementing Rust commands (#[tauri::command]), setting up IPC patterns (invoke, emit, channels), configuring permissions/capabilities, troubleshooting build issues, or deploying desktop/mobile apps. Triggers on Tauri, src-tauri, invoke, emit, capabilities.json.
Also in 6 projects that use this
mduongvandinhSkillgo-best-practices
Also in 3 projects that use this
junimnjwSkillrust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
Also in 3 projects that use this
Other versions46 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- morganlinton/BeautifulRust★ 1.8k100% same
- Cosmian/kms★ 37225% same
- tuan3w/herdr-mobile★ 2998% same
- iyazerski/dev-flows-plugin★ 0100% same
Wrote their own version · 42
- farm-fe/farm★ 5.6ksame name
- crbnos/carbon★ 2.8ksame name
- pedronauck/skills★ 649same name
- linx-systems/clamui★ 372same name
- openbezal/rhema★ 354same name
- apollographql/apollo-mcp-server★ 318same name
- apollographql/skills★ 123same name
- Blushyes/reef★ 84same name
- microsoft/scope★ 78same name
- baekenough/oh-my-customcode★ 42same name
32 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- address-reviewSkill
- comment-hygieneSkill
- commitSkill
- discussion-auditSkill
- environmentSkill
- fact-check-my-reviewSkill
- landSkill
- local-reviewSkill
- open-prSkill
- plain-englishSkill
- pr-descriptionSkill
- pr-from-reviewSkill
- pr-targetSkill
- review-queueSkill
- review-roundsSkill
- rust-portSkill
- rust-reviewSkill
- saySkill
- side-sessionSkill
- todoSkill
- wire-upSkill
- work-summarySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
35 rules. 0 are common, 9 are distinctive, and 26 are very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
26
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

