Skip to content
Skills Library
Programming · Building & coding

ds-rust

/ds-rust

Use when changing Rust crate behavior, Cargo features, async lifecycles, or native dependency boundaries in an existing project.

Repository
dsstack ↗
Licence
MIT
Last repository change
08.11.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when changing Rust crate behavior, Cargo features, async lifecycles, or native dependency boundaries in an existing project.

Original author description

Use when changing Rust crate behavior, Cargo features, async lifecycles, or native dependency boundaries in an existing project.

How it works

SKILL.md has no level-two headings · 14 lines, 350 words

SKILL.md preview
---
name: "ds-rust"
description: "Use when changing Rust crate behavior, Cargo features, async lifecycles, or native dependency boundaries in an existing project."
---

# Rust changes

- Reuse the toolchain pin, lockfile, wrappers, runtime, and shared crate utilities. Consolidate duplication the change touches; leave intentionally different behavior and unrelated code alone. Find the owning crate and smallest existing test target before building.
- Run that target through the wrapper, for example `cargo nextest run -p <crate> <filter>` when installed; `cargo check` neither runs tests nor links everything. Add cases to existing modules: each new `tests/*.rs` file creates another binary to compile and link.
- Before changing build setup, run `command -v cargo-steward`. When present, it is Cargo's rustc wrapper with sccache behind it and may route each worktree's target and `TMPDIR`; follow the installed `cargo-steward` skill. Don't set your own `RUSTC_WRAPPER` (even empty); pick its inner wrapper with `CARGO_STEWARD_INNER`. When `cargo steward shim explain --json` shows `target_dir.routed`, don't set `CARGO_TARGET_DIR` or `--target-dir` either; otherwise follow the project's target-dir policy.
- Without cargo-steward, use available sccache through the project wrapper or `RUSTC_WRAPPER=sccache`, preserving existing wrapper chains, and give concurrent builds separate targets.
- Set `CARGO_INCREMENTAL=0` for cacheable builds; incremental rustc output is not cacheable. Preserve an explicitly required incremental workflow. When enabling or diagnosing caching, compare `sccache --show-stats` before and after a real build.
- Keep the target directory, profile, features, target triple, and `RUSTFLAGS` stable. Don't clean warm output just to demonstrate cache hits.
- Use all available logical CPU cores. If config or wrappers lower Cargo jobs or test threads through `CARGO_BUILD_JOBS`, `RUST_TEST_THREADS`, or nextest's `--test-threads`, set them to the detected count. Keep tests serial only where the project requires isolation.
- Use integration tests for process, database, FFI, cancellation, or resource-lifetime boundaries. Include affected dependents or feature combinations when changes cross crate or feature boundaries.

When a task/worktree is complete or superseded, remove its unused targets and temporary output. With cargo-steward, run `cargo steward remove --worktree <dir>` to preview, then again with `--apply`, before deleting the worktree (`remove --orphaned` covers worktrees already deleted); free space with `cargo steward gc` rather than `cargo clean` or deleting build files. Without it, check active processes first. Preserve shared caches, required artifacts, and unmerged work.
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named ds-rust.

Database snapshot: 13.11.2026 · package version 10fa59152624 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90cc-rust-project-standard
    Use when Rust crate or workspace structure, module boundaries, ownership-facing APIs, Result conventions, Cargo dependencies or engineering checks need design or review.
  • 100rust-learner
    Learn Rust language features and crate updates. Use when user asks about Rust version changelog, what's new in Rust, crate updates, Cargo.toml dependencies, tokio/serde/axum features, or any Rust ecosystem questions.
  • 90rust
    This skill should be used when writing or reviewing Rust code, or when the project uses "Rust", "Cargo", "cargo clippy", "crate", or Rust module patterns. Provides Rust coding conventions, patterns, and best practices. Project-specific conventions always take priority.
  • 90rust-architecture
    Use this skill when structuring Rust backend applications — workspace layout, crate organization, feature-based modules, error handling architecture, async runtime selection, and type-driven design. This skill enforces: Cargo workspace for multi-crate projects, Result/Option for…
  • 100rs-learner
    Use when asking about Rust versions or crate info. Keywords: latest version, what's new, changelog, Rust 1.x, Rust release, stable, nightly, crate info, crates.io, lib.rs, docs.rs, API documentation, crate features, dependencies, which crate, what version, Rust edition, edition…
  • 86rust-review
    Use when reviewing Rust code, a Rust diff or a crate before it lands, or when asked whether Rust code is sound or idiomatic.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.