Rust Patterns
Idiomatic Rust patterns: ownership and borrowing, Result/? error handling, traits, enums that make illegal states unrepresentable, and safe concurrency.
- What
- Idiomatic Rust patterns: ownership and borrowing, Result/? error handling, traits, enums that make illegal states unrepresentable, and safe concurrency.
- Cost
- Free
- Needs
- Use "Rust Patterns" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a patterns skill for writing and reviewing Rust the way experienced Rustaceans do. It enforces idiomatic conventions across six areas: ownership and borrowing so the compiler prevents data races (pass references, take ownership only to store or consume, reach for Cow when ownership is conditional), Result and the ? operator for error propagation with thiserror in libraries and anyhow in applications, enums plus exhaustive pattern matching to make illegal states unrepresentable, traits and generics for zero-cost abstraction, safe concurrency through Arc<Mutex<T>>, channels, and async/await, and small, domain-organized pub surfaces. Every rule ships with good/bad code pairs, so you see the borrow checker friendly version next to the wasteful clone. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; assumes you already know Rust basics, it will not teach the language from zero; examples target modern Rust, very old codebases may diverge. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Rust Patterns" with your Muse. Prerequisites: a Rust codebase to write or review. Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/rust-patterns/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review this Rust module against these patterns: ownership, error handling, and concurrency." 3. For new code, ask: "Write this in idiomatic Rust following these patterns, with thiserror for the library parts." Tip: paste one module at a time; whole-crate reviews come back shallow. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets into a chat, and review anything Muse proposes before it changes your code.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.