mcpField
R
rust-async-patterns

rust-async-patterns

github.com/sickn33Development49.2k224 installsUpdated 1d ago
Repository

About rust-async-patterns

A skill for async Rust development with the Tokio runtime, covering tasks, channels, streams, and error handling. It is intended for developers building concurrent services or debugging and tuning async applications.

Key features

  1. 01Tokio async runtime practices
  2. 02Patterns for tasks, channels, and streams
  3. 03Guidance on async error handling
  4. 04Async debugging and performance tuning

Use cases

  1. 01Build async Rust applications
  2. 02Implement concurrent network services
  3. 03Debug Tokio async I/O issues
  4. 04Improve async error handling and performance

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill rust-async-patterns

After installing, type/rust-async-patternsin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

Rust Async Patterns

Production patterns for async Rust programming with Tokio runtime, including tasks, channels, streams, and error handling.

Use this skill when

  • Building async Rust applications
  • Implementing concurrent network services
  • Using Tokio for async I/O
  • Handling async errors properly
  • Debugging async code issues
  • Optimizing async performance

Do not use this skill when

  • The task is unrelated to rust async patterns
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported