38건 · 관련도순
Use when writing tests for Rust service code - unit tests beside the code, integration tests in tests/, tokio::test, Router::oneshot for HTTP, sqlx::test for a fresh database per test, trait fakes or mockall at ports, test-first
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write cargo tests. A test name is a sentence, the body is setup, mock, test and verify blocks separated by blank lines with no comments, and shared setup lives in a named test-support module rather than in each test. Covers naming, the block shape, where a test file goes, async and time, workspaces, and running one crate or one filter. Use when adding or changing any #[test] or #[tokio::test], or when Rust coverage has to come up. Triggers - "write a rust test", "cargo test", "test this crate", "cover this handler".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rust best practices. Use when reading or editing any .rs file, designing a crate's public API, choosing an error type, splitting a workspace, or writing async code on tokio. Triggers - "rust best practices", "is this idiomatic", "should this be a newtype", "anyhow or thiserror", "why does the borrow checker", "review this Rust".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rust programming expert including ownership, borrowing, lifetimes, async Tokio patterns, error handling, trait system, performance optimization, testing, and production systems development
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing eBPF programs with libbpf, bpftrace, or Rust with aya-ebpf and aya-log, attaching kprobes, tracepoints, or XDP hooks, declaring maps, sharing data with a Tokio loader, triaging verifier or Aya load errors, or porting with CO-RE. Not for full kernel bypass: use dpdk.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
RFDB server becomes unresponsive (60s+ timeouts) during enricher addEdges write storms. Use when: (1) RFDB CPU spikes to 60-90% after addEdges calls; (2) subsequent reads time out at 60s; (3) server stays catatonic for 5-15 min after a write storm; (4) Tokio main thread parked (write-lock contention). Root cause: add_edges() calls maybe_auto_flush() which has a memory-pressure path that fires on NODE count — not edge count — and holds the exclusive write lock during disk I/O. Fix: separate maybe_auto_flush_edges() uses byte-limit only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Appwrite Rust SDK skill. Use when building server-side Rust applications with Appwrite. Covers async client setup with API keys, user management, TablesDB database/table/row operations, file storage, function executions, permissions, queries, and error handling. Uses the crates.io `appwrite` package and Tokio.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Appwrite Rust SDK skill. Use when building server-side Rust applications with Appwrite. Covers async client setup with API keys, user management, TablesDB database/table/row operations, file storage, function executions, permissions, queries, and error handling. Uses the crates.io `appwrite` package and Tokio.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when writing, reviewing, or architecting Rust code — systems programming, async services, CLI tooling, web backends, or any work in `.rs` files. Triggers on editing `.rs` or `Cargo.toml` files, or mentions of "Rust", "Tokio", "Axum", "cargo", "borrow checker", "lifetime", "trait object", "async Rust", "crate", "rustc", or explicit requests to "build this in Rust" / "rewrite X in Rust". For adversarial security review of Rust code see security-reviewer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Appwrite Rust SDK skill. Use when building server-side Rust applications with Appwrite. Covers async client setup with API keys, user management, TablesDB database/table/row operations, file storage, function executions, permissions, queries, and error handling. Uses the crates.io `appwrite` package and Tokio.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reusable skill for coding agents (Claude, GPT, etc.) to build, optimize, debug, and productionize AI agents and coding agents in Rust. Embeds Rig/ADK patterns, Tokio async architecture, tracing observability, performance techniques, erro...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Master Rust 1.75+ with modern async patterns, advanced type system features, and production-ready systems programming. Expert in the latest Rust ecosystem including Tokio, axum, and cutting-edge crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.