Rust Cursor Rules
Cursor rules for Rust: ownership patterns, error handling with Result, idiomatic Rust, and performance-aware coding conventions.
- Use Result<T, E> for all fallible operations; propagate with the ? operator - Prefer returning errors over panicking; reserve panic! for truly unrecoverable states - Use thiserror for library errors and anyhow for application errors - Leverage the type system to make invalid states unrepresentable - Prefer iterators and combinators over imperative loops - Use clippy and rustfmt in CI; treat clippy warnings as errors - Document all public items with doc comments including examples - Use #[derive] for common traits (Debug, Clone, PartialEq, serde)
How to use with Cursor
Create a `.cursorrules` file in your project root and paste these rules. Cursor reads this automatically on every AI interaction.
Related Rules
Python Cursor Rules
Best Cursor AI coding rules for Python development. Enforce type hints, PEP 8, Pythonic patterns, and modern Python best practices in your .cursorrules file.
TypeScript Cursor Rules
Cursor rules for TypeScript: enforce strict mode, eliminate any types, and write type-safe code with these .cursorrules configurations.
React Cursor Rules
Cursor rules for React: component patterns, hooks best practices, performance optimization, and clean state management conventions.
Next.js Cursor Rules
Cursor rules for Next.js App Router: server components, data fetching, routing, and deployment best practices.