Enforce domain constraints for Rust REST APIs with Axum or Actix.
npx skills add https://github.com/AlexKVal/rust-skills-for-cursor --skill domain-web-alexkval
Please help me install this Agent Skill. Skill: domain-web Source: https://github.com/AlexKVal/rust-skills-for-cursor/tree/main/skills/domain-web Command: npx skills add https://github.com/AlexKVal/rust-skills-for-cursor --skill domain-web-alexkval
Domain constraints for Rust web services are often under-communicated: developers struggle to enforce non-blocking I/O, thread-safe shared state, and clear ownership patterns across frameworks like Axum and Actix. This skill provides a structured set of rules and patterns to guide design decisions and prevent common pitfalls.
Start by wiring a basic Axum handler that stores shared state in Arc and exposes a non-blocking endpoint.
High-intent search queries and answers about installing and using this skill.
Manage shared state in Rust web services by wrapping it in Arc and enforcing Send + Sync bounds, which ensures thread-safe access across non-blocking handlers and multiple worker threads without data races.
Enforce non-blocking handlers in a Rust REST API by adopting async I/O patterns and avoiding blocking operations inside request handlers, ensuring the thread pool remains free to process concurrent requests efficiently.
Rust web servers panic when sharing state across threads if the state lacks Send + Sync guarantees or uses Rc, which is not thread-safe; switching to Arc-based state management enforces the required ownership and concurrency constraints.
Yes, you must avoid Rc when building scalable Rust microservices because it is single-threaded; use Arc-based sharing instead to satisfy Send + Sync state requirements for safe, high-concurrency web app architectures.
Structure explicit error handling in Rust async web frameworks by returning structured error types from non-blocking handlers instead of unwinding, ensuring predictable API responses and stable worker thread execution under concurrent load.
Yes, you can build framework-agnostic Rust web services by applying domain constraints like Arc-based state sharing and explicit error handling through structured patterns, allowing the same design to map cleanly onto both Axum and Actix implementations.
0xharryriddleDesign Rust web services with async I/O, shared state, and middleware.
tdcareConfigure a Salvo reverse proxy for routing and balancing Rust microservice requests.
imehrImplement Rust database access patterns with SQLx and Diesel.
lywa1998Build safe, scalable Rust web services with async handlers and shared state.
