Generate production-ready Rust Cursor rules for Project Rules (.mdc), AGENTS.md, or legacy .cursorrules. This template encodes stack-specific conventions for projects using Rust. Systems language with ownership, zero-cost abstractions, and fearless concurrency.
The template focuses Cursor AI on concrete Rust practices instead of generic coding advice. Required sections are always included; optional sections can be enabled when they match your project.
The generator turns these sections into Project Rules with frontmatter, AGENTS.md, or a single .cursorrules file depending on the output format you choose.
- Prefer borrowing (&T, &mut T) over taking ownership when possible.
- Use snake_case for variables, functions, and methods.
- Use PascalCase for types, traits, and enums.
- Use SCREAMING_SNAKE_CASE for constants and statics.
- Clone only when ownership transfer is unavoidable.
- Use references with explicit lifetimes only when the compiler requires them.- Use Result<T, E> for fallible operations — no exceptions.
- Use the ? operator for error propagation.
- Use thiserror for custom error types with derive macros.
- Use anyhow for application-level error handling.
- Use Option<T> instead of null — never use unwrap() in production code.
- Use expect() with descriptive messages during development only.- Use mod declarations to organize code into modules.
- Use pub to control visibility — keep internals private by default.
- Use use statements for imports at the top of each file.
- Use pub(crate) for internal visibility within the crate.
- Use workspace for multi-crate projects.
- Keep module files focused: one primary concern per module.