菜单
Route Rust work to the smallest useful skill. Use for Rust coding, design, compile errors, API questions, crate layout, async, performance, unsafe, or domain-specific Rust work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Migrate a Rust codebase to the Polonius borrow checker (location-sensitive analysis, nightly flag -Zpolonius=next) and evolve owned-value internal APIs into the reference-returning, borrow-centric designs that NLL discouraged. Use this skill whenever the user mentions Polonius, NLL limitations, borrow-checker workarounds, defensive clones, double map lookups, get-or-insert helpers, lending iterators, reducing clone counts, or asks to audit, simplify, de-clone, or redesign Rust APIs around borrowing. Also use it when reviewing Rust code containing clone-to-appease-borrowck patterns, entry() calls with cloned keys, id/index indirection standing in for references, or clone-modify-writeback sequences — even if the user does not name Polonius. Provides two modes (workaround retirement; ownership-model evolution), a pattern catalogue with lifetime-versus-aliasing discriminators, an API evolution playbook, worked examples, and a documentation strategy.
Design and maintain Rust unit tests with clear helper boundaries, rstest fixtures and parameterization, serial_test isolation, fallible setup, and rich assertions with googletest, pretty_assertions, and insta. Use when refactoring assertion helpers, replacing brittle boolean assertions, shaping table tests, or deciding between equality, matcher, and snapshot assertions.
Use for Rust crate boundaries, workspace structure, feature flags, public versus internal APIs, layering, and testable module design.
Capture architectural decisions in Rust projects using the Y-Statement format. Use when a choice is hard to reverse, when the rationale will outlive its author, or when reviewers keep asking "why did we pick this?". Especially relevant for typestate, trait bounds, public API shape, `unsafe` invariants, runtime selection, and verification tooling.
Audit and curate a Rust project's dependency graph. Use for `cargo-vet`, `cargo-audit`, `cargo-deny`, lockfile hygiene, version pinning, and the policy of who is trusted to ship what. Also for SemVer guardrails (`cargo-semver-checks`, `cargo-public-api`) at the publishing boundary.
Write and maintain Kani bounded model checking harnesses for Rust. Use when verifying structural invariants, unsafe code, bounded state machines, or dispatch logic via exhaustive symbolic execution.
| name | rust-router |
| description | Route Rust work to the smallest useful skill. Use for Rust coding, design, compile errors, API questions, crate layout, async, performance, unsafe, or domain-specific Rust work. |
| globs | ["**/Cargo.toml","**/*.rs"] |
Load this first for non-trivial Rust work, then load only the smallest useful follow-on skill.
leta skill for code navigation, references,
implementations, and refactors.nll-to-poloniusrust-memory-and-staterust-types-and-apisrust-errorsrust-unit-testingSend/Sync, blocking, channels, or cancellation:
rust-async-and-concurrencyrust-performance-and-layoutunsafe, foreign function interface (FFI), layout guarantees, or soundness:
rust-unsafe-and-ffiarch-crate-designcargo-vet, cargo-deny, SemVer guardrails:
arch-supply-chainarch-decision-recordscargo-mutants, loom,
shuttle, turmoil, Kani, Verus): rust-verification; deep dives
in proptest, kani, and verusdomain-web-servicesdomain-cli-and-daemonsno_std, firmware, devices, or edge nodes: domain-embedded-and-iotnll-to-polonius with
rust-types-and-apis only when public API compatibility constrains the
migration.domain-web-services with
rust-async-and-concurrency or rust-errors.domain-cli-and-daemons with rust-errors.domain-embedded-and-iot with
rust-memory-and-state or rust-unsafe-and-ffi.Arc<Mutex<_>> without clarity,dyn Any, erased errors, or unstable generic sprawl,Read routing-matrix.md only when the route is still unclear.