domain-web

Design Rust web services with async I/O, shared state, and middleware.

3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/0xharryriddle/codex-field-kit --skill domain-web-0xharryriddle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-web
Source: https://github.com/0xharryriddle/codex-field-kit/tree/main/archive/upstream/chasebuild-agent-skills/rust/skills/domain-web
Command: npx skills add https://github.com/0xharryriddle/codex-field-kit --skill domain-web-0xharryriddle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and implementing robust web services in Rust while managing async operations, state, and security pain points.

Core Features & Use Cases

  • Guidance for building stateless HTTP services and safe concurrency patterns.
  • Framework-agnostic design notes covering axum, actix-web, warp, and rocket, with practical examples.
  • Best practices for state sharing (Arc), middleware, authentication, and error handling.

Quick Start

Create a Rust web service using axum with shared Arc state and a simple authentication middleware.

Frequently Asked Questions about domain-web

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build Rust web services with async non-blocking I/O?

To build async Rust web services, use frameworks like axum or actix-web to handle concurrent requests efficiently. This Skill provides guidance on designing robust HTTP APIs, managing asynchronous operations, and implementing safe concurrency patterns for scalable web services.

What is the best way to share state across axum or actix-web handlers?

Sharing state across axum or actix-web handlers is best achieved using Arc-based shared state. This approach ensures thread-safe concurrency in async Rust applications. The Skill covers best practices for state sharing, allowing multiple request handlers to safely access and modify shared application data without blocking.

How do I implement authentication middleware in Rust web APIs?

Implementing authentication middleware in Rust web APIs requires extracting request data and validating credentials before passing requests to handlers. This Skill demonstrates how to use request extractors and middleware layers in frameworks like warp or rocket to secure endpoints and manage user authentication flows effectively.

Does this Skill cover error handling with IntoResponse for Rust APIs?

Yes, this Skill covers error handling with IntoResponse for Rust APIs. It provides framework-agnostic design notes on transforming custom application errors into proper HTTP responses. This ensures your async web services return consistent status codes and error payloads across axum, actix-web, warp, or rocket.

Can I use request extractors with warp and rocket for async HTTP services?

You can use request extractors with warp and rocket to parse and validate incoming HTTP requests for async services. This Skill offers practical examples of using extractors to manage shared state and authentication, ensuring your async Rust web services handle request data robustly and safely.

Why does async Rust require specific patterns for safe concurrency in web services?

Async Rust requires specific patterns for safe concurrency in web services because non-blocking I/O operations demand careful state management to prevent data races. This Skill explains how to use Arc-based shared state and async patterns to maintain memory safety and high performance under concurrent load.