rust-pro
Rust Development Expert
Build high-performance, memory-safe Rust applications with expert guidance on async patterns, advanced type system features, and production-ready systems programming.
Descargar el ZIP de la skill
Subir en Claude
Ve a Configuración → Capacidades → Skills → Subir skill
Activa y empieza a usar
Pruébalo
Usando "rust-pro". Explain async/await in Rust and show how to use Tokio for a concurrent web server
Resultado esperado:
Async/await in Rust provides a way to write asynchronous code that looks synchronous. With Tokio, you can build concurrent servers efficiently. Here's a basic example of an async HTTP server...
Usando "rust-pro". Help me understand ownership model for the this code that manages a database connection pool
Resultado esperado:
For a database connection pool, you typically want multiple threads to access connections. This requires Arc<Mutex<ConnectionPool>> or a specialized pool like r2d2. Let me explain the ownership semantics...
Auditoría de seguridad
SeguroPrompt-only skill with no executable code. Static analysis scanned 0 files and detected 0 potential security issues. This is a Rust developer persona definition that provides guidance on Rust programming without any network, filesystem, or system access capabilities. Risk score: 0/100.
Puntuación de calidad
Lo que puedes crear
Building Async Web Services
Design and implement high-performance web APIs using axum, Tokio, and async patterns with proper error handling and backpressure
Performance Optimization
Analyze and optimize Rust code for memory usage, cache efficiency, and zero-cost abstractions while maintaining safety
FFI and Unsafe Code
Create safe wrappers around C libraries with proper safety invariants and documentation for unsafe code blocks
Prueba estos prompts
Explain how [Rust concept] works in Rust 1.75+ and provide a code example.
I have this Rust code that fails with a borrow checker error. Analyze the ownership model and suggest a fix: [code]
Design an async web service in Rust that handles [use case] with Tokio. Include error handling, proper shutdown, and testing approach.
Profile and optimize this Rust code for [metric]. Suggest zero-cost abstractions, memory layout improvements, or algorithm changes: [code]
Mejores prácticas
- Prefer Result types over exceptions for error handling
- Use Arc and Rc only when shared ownership is truly needed
- Document all unsafe code blocks with explicit safety invariants
Evitar
- Using unwrap() in production code without proper error handling
- Ignoring the borrow checker by using unsafe instead of finding a safe solution
- Blocking async code with synchronous I/O operations