Skip to main content
prompt GP ChatGPT

Tokio Async Rust taste — ChatGPT prompt: what it does, how to install

The Tokio Async Rust taste prompt for ChatGPT sets engineering conventions for asynchronous Rust services built with Tokio. It applies while writing or reviewing code that handles task cancellation, network timeouts, and shutdown.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Tokio Async Rust taste does

The prompt guides Tokio-based Rust service code. It keeps #[tokio::main] in binary crates, steers CPU-heavy work away from the async runtime, and calls for bounded concurrency with a Semaphore or buffer_unordered(n). Libraries should stay runtime-independent where that fits the design.

It covers channels, errors, and observability too. Network calls should have timeouts; spawned tasks should be tracked with JoinSet or TaskTracker; long-running work should receive a CancellationToken and a drain deadline. For HTTP services, the prompt names axum and tower middleware. Tests use #[tokio::test] with start_paused = true to control time.

For short critical sections, it favors std::sync::Mutex or parking_lot; tokio::sync::Mutex is reserved for locks held across .await. In Claude Code, the file goes at .claude/commands/prompts.csv.md.

What it helps with

  • separate Tokio runtime setup from reusable library code
  • handle cancellation and timeouts in async tasks
  • cap concurrency during fan-out work
  • test async code without real-time sleeps

Example prompts for the agent

  • Review this service for blocking work and unbounded channels.
  • Design graceful shutdown for these long-running tasks with CancellationToken.
  • Write a Tokio test for this handler that controls time.

How to install Tokio Async Rust taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Tokio Async Rust taste

How do I install Tokio Async Rust taste in Claude Code?

Place the file at .claude/commands/prompts.csv.md.

What does Tokio Async Rust taste do?

It sets coding conventions for Tokio services, covering task ownership, network timeouts, tracing, concurrency limits, and tests.

How does the prompt recommend testing async code?

Use #[tokio::test] and set start_paused = true to control time instead of relying on real sleeps.

Source text

prompts.csv · CC0-1.0
# Tokio Async Rust taste of a production service engineer
- Use `#[tokio::main]` only in the binary and keep library crates runtime-agnostic where practical, taking futures and handles as inputs. Confidence: 0.80
- Never block the async runtime; move CPU-heavy or blocking I/O work to `spawn_blocking` or a dedicated thread pool. Confidence: 0.95
- Use `tokio::sync::Mutex` only when a lock must be held across an `.await`; otherwise use `std::sync::Mutex` or `parking_lot` for short critical sections. Confidence: 0.90
- Prefer message passing with bounded `mpsc` channels over shared mutable state, and size every channel deliberately for backpressure. Confidence: 0.85
- Never use unbounded channels in request paths, because a slow consumer turns into unbounded memory growth. Confidence: 0.85
- Put a timeout on every network call with `tokio::time::timeout` or a client-level setting; no await on the network should be able to hang forever. Confidence: 0.95
- Use `JoinSet` or `TaskTracker` to own spawned tasks so they are awaited, cancelled and their errors are observed. Confidence: 0.85
- Treat every `.await` as a possible cancellation point and keep state consistent if the future is dropped there. Confidence: 0.85
- Use `select!` carefully and only with cancel-safe branches; document why each branch is safe to drop. Confidence: 0.80
- Implement graceful shutdown with a `CancellationToken` passed to every long-running task, plus a drain deadline. Confidence: 0.90
- Use `thiserror` for library error enums and `anyhow` (or `eyre`) with context in binaries. Confidence: 0.85
- Instrument with `tracing`, using `#[instrument(skip_all, fields(...))]` on handlers and structured fields instead of formatted strings. Confidence: 0.90
- Build HTTP services on `axum` with `tower` middleware for timeouts, concurrency limits, tracing and request IDs. Confidence: 0.80
- Share application state through an `Arc<AppState>` holding pools and clients, not through global statics. Confidence: 0.85
- Reuse one `reqwest::Client` and one database pool per process instead of creating them per request. Confidence: 0.95
- Bound concurrency for fan-out work with a `Semaphore` or `buffer_unordered(n)` rather than spawning a task per item. Confidence: 0.85
- Avoid holding guards or non-`Send` values across `.await`; let the compiler's `Send` errors guide the code toward a cleaner structure. Confidence: 0.75
- Test async code with `#[tokio::test]` and control time with `start_paused = true` instead of real sleeps. Confidence: 0.80
- Use `tokio-console` or runtime metrics when debugging stalls, before guessing at the cause. Confidence: 0.65
- Keep tokio feature flags minimal in libraries and enable `full` only in binaries or tests. Confidence: 0.70

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Programming languages →

From the same set218

The whole set →
Internationalization taste The Internationalization taste ChatGPT prompt sets out product internationalization practices. It covers localized UI text, data formats, and public pages. GP ChatGPT ★ 178,201repo stars API Rate Limiting taste API Rate Limiting taste — a prompt for ChatGPT that defines rate limiting rules for API endpoints. Helps design backend protection against abuse and traffic spikes. GP ChatGPT ★ 178,201repo stars Python Type Hints taste The Python Type Hints taste ChatGPT prompt sets conventions for typing Python code. It covers annotations, type choices, and static checking. GP ChatGPT ★ 178,201repo stars Secrets Management taste Secrets Management taste — a prompt for ChatGPT that defines security standards and best practices for secrets management. GP ChatGPT ★ 178,201repo stars Tailwind CSS taste Tailwind CSS taste is a prompt for ChatGPT, Claude.ai, and Claude Code that sets utility-first styling rules, design tokens, and bans arbitrary pixel sizes in Tailwind CSS code. GP ChatGPT ★ 178,201repo stars Vite Frontend Tooling taste The Vite Frontend Tooling taste ChatGPT prompt sets preferences for building frontend projects with Vite. It covers app setup, type checks, tests, and release builds. GP ChatGPT ★ 178,201repo stars Linux Server Hardening taste Linux Server Hardening taste — a prompt for ChatGPT provides an operations engineering ruleset for hardening Linux servers. It guides base image setup, SSH access policies, and automated configuration via Ansible or cloud-init. GP ChatGPT ★ 178,201repo stars Database Schema Design taste The Database Schema Design taste ChatGPT prompt sets rules for designing relational database schemas. It covers keys, constraints, indexes, and data storage. GP ChatGPT ★ 178,201repo stars

Project sponsors

Companies that keep this analytics open