Standardizes Rust backend development using Axum and Tokio with strict guidelines for error handling, async safety, and project…
When to activate: Rust CLI tools, clap, command-line arguments, subcommands, config files, environment variables, terminal output
Navigate Rust code using LSP. Triggers on: /navigate, go to definition, find references, where is defined, 跳转定义, 查找引用, 定义在哪, 谁用了这个
Architects high-performance Rust core libraries designed for seamless cross-language integration and efficient document processing.
When to activate: Rust database, sqlx, diesel, PostgreSQL, SQLite, MySQL, migrations, queries, connection pools, transactions
Visualize Rust project dependencies as ASCII art.
Standardizes Rust backend development using Axum and Tokio with best practices for error handling, async safety, and performance.
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
Use when Rust error handling with Result, Option, custom errors, thiserror, and anyhow.
When to activate: Rust generics, trait bounds, associated types, GATs, where clauses, PhantomData, higher-ranked trait bounds, type system
Guides learners from beginner to competent in Rust through stateful, adaptive curriculum management and spaced repetition.
//! use htmltomarkdown::HtmlConverter; //! let converter = HtmlConverter::new(); //! let markdown = converter.convert(" Hello ")?; //!
When to activate: Rust modules, Cargo.toml, workspaces, crate organization, pub visibility, use declarations, features, dependencies
When to activate: Rust tracing, logging, metrics, spans, instruments, OpenTelemetry, tracing-subscriber, prometheus, structured logging
Use when Rust's ownership system including ownership rules, borrowing, lifetimes, and memory safety.
When to activate: general Rust code, ownership, borrowing, lifetimes, enums, pattern matching, traits, structs, idiomatic Rust
Guide for writing Rust code covering ownership, borrowing, lifetimes, error handling, async programming, and Rust best practices
Guidance for scaffolding new Rust projects.
CRITICAL: Use for ALL Rust questions including errors, design, and coding.
When to activate: Rust security, unsafe code, input validation, secret handling, cryptography, supply chain, audit, injection prevention
When to activate: Rust serde, JSON, serialization, deserialization, custom serialize, rename, flatten, skip, default, serde_json, toml…