beautiful-rust plugin
Skills that teach Claude to write, review, and port idiomatic Rust, distilled from five authoritative guides, plus a drop-in clippy config.
How to install the beautiful-rust plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add morganlinton/BeautifulRust
/plugin install beautiful-rust@beautiful-rustWhat's inside beautiful-rust
3 parts read from the plugin's own files.
Skills 3
Claude loads it when the task matches- rust-best-practices
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.
- rust-port
Port code from C, C++, Python, Go, JavaScript, or TypeScript into idiomatic Rust that keeps the original behavior: ownership instead of manual memory, Result instead of error codes and exceptions, enums instead of flag ints and magic strings, and tests that prove the port matches. Use this whenever the user asks to port, translate, convert, migrate, or rewrite code in Rust ("rewrite this in Rust", "what would this look like in Rust", "move this module to Rust"), even if they don't say "port". Pairs with the rust-best-practices skill, which covers the target code's style.
- rust-review
Review existing Rust code for idiom, API design, error handling, safety, and maintainability, and produce a prioritized report where every finding cites the rule it breaks and gives a concrete fix. Use this whenever the user asks to review, audit, critique, grade, or "check" Rust code, a crate, a module, a .rs file, a diff, or a pull request, or asks what is wrong with their Rust or how to make it more idiomatic, even if they don't say "review". Pairs with the rust-best-practices skill, which covers writing new code.
Using beautiful-rust in Claude Code
Skills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update beautiful-rust@beautiful-rust
- Refresh the marketplace
- /plugin marketplace update beautiful-rust
- Turn it off for now
- /plugin disable beautiful-rust@beautiful-rust
- Remove it
- /plugin uninstall beautiful-rust@beautiful-rust
Skills in beautiful-rust
- rust-best-practicesmorganlinton/BeautifulRust
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.
61 files1.8Kstars - rust-portmorganlinton/BeautifulRust
Port code from C, C++, Python, Go, JavaScript, or TypeScript into idiomatic Rust that keeps the original behavior: ownership instead of manual memory, Result instead of error codes and exceptions, enums instead of flag ints and magic strings, and tests that prove the port matches. Use this whenever the user asks to port, translate, convert, migrate, or rewrite code in Rust ("rewrite this in Rust", "what would this look like in Rust", "move this module to Rust"), even if they don't say "port". Pairs with the rust-best-practices skill, which covers the target code's style.
34 files1.8Kstars - rust-reviewmorganlinton/BeautifulRust
Review existing Rust code for idiom, API design, error handling, safety, and maintainability, and produce a prioritized report where every finding cites the rule it breaks and gives a concrete fix. Use this whenever the user asks to review, audit, critique, grade, or "check" Rust code, a crate, a module, a .rs file, a diff, or a pull request, or asks what is wrong with their Rust or how to make it more idiomatic, even if they don't say "review". Pairs with the rust-best-practices skill, which covers writing new code.
34 files1.8Kstars
beautiful-rust plugin questions
How do I install the beautiful-rust plugin?
In Claude Code run /plugin marketplace add morganlinton/BeautifulRust, then /plugin install beautiful-rust@beautiful-rust.
What does the beautiful-rust plugin include?
beautiful-rust bundles 3 skills.
How do I update or remove the beautiful-rust plugin?
Update it with claude plugin update beautiful-rust@beautiful-rust in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall beautiful-rust@beautiful-rust.
What license is the beautiful-rust plugin under?
MIT, as stated in the plugin's manifest.