Automated summary
Governs Rust coding by requiring `cargo add` for dependencies, `cargo fmt` after edits, and running tests before finishing a turn.
Strengths
- Short, directly actionable rules that are easy to apply on every turn
- Enforces test verification (`cargo test --all --workspace`) before wrapping up
- Prevents hand-editing `Cargo.toml` by favoring `cargo add`
Limitations
- Does not cover `clippy`, error handling, or sensitive areas like `unsafe`
- Assumes a standard Cargo project; project-specific test commands are not detailed
- Is a checklist of conventions rather than a deeper guide to Rust idioms
Activate it whenever writing, modifying, or answering questions about Rust code to keep formatting, dependencies, and tests consistent.
Not needed for general questions about the Rust ecosystem or for non-Rust code.
Security analysis
SafeThe skill contains only standard Rust development guidance: using cargo add, running cargo fmt, and running tests. It declares no tools, performs no network or filesystem actions, and includes no destructive or exfiltration instructions.
No concerns found
How this analysis is madeExamples
Add the `serde` crate with the derive feature to this Rust project and use it to make the `Config` struct serializable.Refactor the `parse_args` function in src/main.rs to return a Result, then format the code and run the workspace tests.Implement a `from_str` constructor for `UserId` in this Rust crate and make sure everything still builds and passes tests.name: rust-best-practice description: [Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust.
Important dos and don'ts for working with Rust source code
- Use
cargo addto add new dependencies or features rather than editingCargo.tomldirectly - Before finishing your turn, when editing Rust code:
- Run
cargo fmtafter modifying Rust source files to ensure consistent formatting - Run tests (most commonly
cargo test --all --workspace, though some projects may have other commands)
- Run
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/rust-best-practice-mrwakdl7/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/rust-best-practice-mrwakdl7' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/rust-best-practice-mrwakdl7/download' --output '.skill-downloads/rust-best-practice-mrwakdl7/SKILL.md.part' && mv '.skill-downloads/rust-best-practice-mrwakdl7/SKILL.md.part' '.skill-downloads/rust-best-practice-mrwakdl7/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/rust-best-practice-mrwakdl7/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.