菜单
Rust development guidance for creating, modifying, reviewing, testing, packaging, and debugging Rust crates, CLIs, services, and libraries. Use when tasks involve .rs files, Cargo.toml, Cargo.lock, workspaces, ownership, lifetimes, traits, async Rust, tokio, serde, cargo fmt, cargo test, cargo clippy, or Rust dependency management.
Elixir development guidance for creating, modifying, reviewing, testing, and debugging Elixir and Phoenix applications. Use when tasks involve .ex or .exs files, mix.exs, Phoenix, LiveView, Ecto, OTP supervision trees, GenServer, ExUnit, mix format, mix test, migrations, schemas, contexts, or Elixir dependency management.
Go development guidance for creating, modifying, reviewing, testing, and debugging Go services, libraries, CLIs, and tooling. Use when tasks involve .go files, go.mod, go.work, goroutines, channels, contexts, HTTP handlers, database code, table tests, gofmt, go test, or Go module management.
Node.js and JavaScript/TypeScript development guidance for creating, modifying, reviewing, testing, packaging, and debugging backend, CLI, tooling, and full-stack code. Use when tasks involve package.json, npm, pnpm, yarn, bun, .js, .mjs, .cjs, .ts, tsconfig, Express, NestJS, Next.js API routes, Vitest, Jest, ESLint, or Node dependency management.
Python development guidance for creating, modifying, reviewing, testing, packaging, and debugging Python code. Use when tasks involve .py files, pyproject.toml, requirements files, pytest, ruff, mypy, FastAPI, Django, Flask, CLIs, scripts, type hints, virtual environments, or Python dependency management.
Analyze a codebase before changing it, infer local patterns, and choose focused implementation and verification steps.
Planning discipline for long-running Deep Agent tasks with delegation, task tracking, validation, and concise delivery.
| name | rust-programming |
| description | Rust development guidance for creating, modifying, reviewing, testing, packaging, and debugging Rust crates, CLIs, services, and libraries. Use when tasks involve .rs files, Cargo.toml, Cargo.lock, workspaces, ownership, lifetimes, traits, async Rust, tokio, serde, cargo fmt, cargo test, cargo clippy, or Rust dependency management. |
Make Rust changes that are explicit about ownership, error paths, feature flags, and public API compatibility.
Cargo.toml, Cargo.lock, workspace config, feature flags, examples,
benches, and CI before editing.Result and the crate's existing error approach (thiserror, anyhow,
custom enums, or plain errors).unsafe out of changes unless the project already requires it and the
invariants are documented.no_std, platform-specific code, and workspace member
boundaries.cargo fmt on changed Rust code.cargo test -p <crate> or cargo test <test-name> first, then
broader workspace tests when shared code changed.cargo check for fast validation and cargo clippy when configured or
useful for the change.