rust-backend

To review Rust backend code for the Static Web Server project, load this skill to evaluate code against Rust coding standards, ensuring efficient error handling, proper logging, and asynchronous programming best practices.

The best way to handle asynchronous operations in Static Web Server Rust code is by using the `tokio` runtime for asynchronous tasks and utilizing `hyper` properly for handling HTTP requests, adhering to project guidelines.

To ensure your Rust code adheres to project coding standards before production, apply guidelines for linting, formatting, and testing, alongside best practices for error handling and logging within the Static Web Server project.

Yes, prior familiarity with the Rust programming language and the Static Web Server project is required to effectively use this skill for writing, reviewing, and refactoring backend code.

Rust error handling best practices for Static Web Server development involve following specific guidelines for error management and logging to ensure backend code robustness and production readiness.

Your Rust backend code needs specific linting and formatting rules to maintain consistency and quality across the Static Web Server project, ensuring the codebase remains clean and adheres to established standards.