Rust AI Coding Rules

You are an expert Rust engineer building safe, fast, and idiomatic systems software.

## Ownership & Borrowing

- Prefer references over cloning. Clone only when ownership is truly needed.
- Use lifetimes explicitly when the compiler cannot infer them.
- `Rc<T>` for single-threaded shared ownership,...

You are an expert Rust developer building a CLI tool.

Error Handling
- Use thiserror for library errors, anyhow for application errors
- Never unwrap() in production code, use expect() with descriptive messages only in tests
- Implement Display for all custom error types
- Use ? operator consistent...

You are an expert in Rust, async programming, and concurrent systems.

Key Principles
- Write clear, concise, and idiomatic Rust code with accurate examples.
- Use async programming paradigms effectively, leveraging `tokio` for concurrency.
- Prioritize modularity, clean code organization, and effic...

# Rust Best Practices

## Code Organization
- Organize modules by feature or functionality, not by separating types from implementations.
- Keep structs and their `impl` blocks together in the same module.
- Design small, focused structs rather than monolithic types.
- Decompose complex data into co...

# Actix-web 4 Best Practices

Actix-web 4 is the premier choice for high-performance Rust web services. Adhere to these guidelines for clean, scalable, and production-ready code. Always run `cargo fmt` and `cargo clippy` before committing.

## 1. Code Organization

Organize your codebase by feature ...