Rust coding guidelines: 50 core rules for idiomatic Rust
50 Rust-specific style rules — naming, formatting, clippy, error handling, memory, concurrency, async, macros, and a deprecated→better migration table
- What
- 50 Rust-specific style rules — naming, formatting, clippy, error handling, memory, concurrency, async, macros, and a deprecated→better migration table
- Cost
- Free
- Needs
- a Rust project the agent can read and refactor — the skill is a style methodology, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @actionbook's 50-rule Rust style guide, built from the community rust-coding-guidelines document — Rust-specific naming rules (no `get_` prefix, `as_`/`to_`/`into_` conversion conventions, `iter()`/`iter_mut()`/`into_iter()`), error-handling discipline (propagate with `?`, prefer `expect()` over `unwrap()`), memory and lifetime habits, concurrency rules (atomics for primitives, explicit lock ordering), async guidance (async is for I/O, never hold locks across await), macro discipline, and a deprecated→better table (`lazy_static!` → `OnceLock`, `try!` → `?`, `failure` → `thiserror`/`anyhow`). Honest caveats: methodology only, no tooling — the agent needs a Rust project to apply it to; license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Rust coding guidelines: 50 core rules for idiomatic Rust is a free Muse skill that teaches 50 Rust-specific style rules for idiomatic Rust, covering naming, formatting, clippy, error handling, memory, concurrency, async, macros, and a deprecated-to-better migration table. It includes conversion conventions, lifetime habits, async guidance, macro discipline, and replacements like lazy_static to OnceLock and try to question mark.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 5c40d3aStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a Rust project the agent can read and refactor — the skill is a style methodology, not software Install "Rust coding guidelines: 50 core rules for idiomatic Rust" for me. It gives my agent @actionbook's 50-rule Rust style playbook: Rust-specific naming (no get_ prefix, as_/to_/into_ conversions, iter conventions), error-handling discipline (? propagation, expect() over unwrap()), memory/lifetime habits, concurrency and async rules (atomics for primitives, never hold locks across await), macro discipline, a quick reference (rustfmt, clippy::all, doc comments), and a deprecated→better migration table. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://raw.githubusercontent.com/actionbook/rust-skills/5c40d3ad785193231b7d0dbfb8e1eb447e5edd94/skills/coding-guidelines/SKILL.md Pinned version: install the code at commit 5c40d3ad785193231b7d0dbfb8e1eb447e5edd94 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "coding-guidelines". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my Rust project or file to review; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 5c40d3a · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.