Menu
[Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Idiomatic patterns for writing code with formality-core (a-mir-formality). Use when writing or reviewing judgment functions, type definitions, or parser-related code in projects built on formality-core.
Guidance for using the Toasty async ORM crate — schema definition, CRUD, relations, queries, and transactions
Always use this skill before writing any test code in the Toasty repository
| name | rust-best-practice |
| description | [Critical] Best practice for Rust coding. Always activate this skill before authoring Rust code or answering questions about Rust. |
cargo add to add new dependencies or features rather than editing Cargo.toml directlycargo fmt after modifying Rust source files to ensure consistent formattingcargo clippy --all --workspace and fix any warningscargo test --all --workspace, though some projects may have other commands)