rust-programmer
Skill0 starsChanged 3 months agoMITView on GitHub
Write, refactor, and debug Rust (.rs) code and Cargo projects using idiomatic patterns, safe error handling, ownership/lifetimes guidance, async/concurrency best practices, and a standard verification routine (fmt/clippy/test). Use when tasks involve Rust source files, Cargo.toml workspaces, Rust API design, or Rust performance/safety reviews.
In this repository66 other files it gives its agents.
- adb-android-app-opsSkill
- agents-sdkSkill
- api-documentationSkill
- atlasSkill
- backend-api-auth-guardrailsSkill
- browser-useSkill
- bundleSkill
- changelogSkill
- chatgpt-appsSkill
- chrome-devtools-testSkill
- chronicleSkill
- cloudflare-deploySkill
- cloudflare-email-serviceSkill
- cloudflare-one-migrationsSkill
- cloudflare-oneSkill
- cloudflareSkill
- computer-useSkill
- create-planSkill
- database-analysisSkill
- database-data-guardrailsSkill
- debug-memory-leakSkill
- deep-initSkill
- deploySkill
- develop-web-gameSkill
- dev-workflowSkill
- docSkill
- durable-objectsSkill
- explainSkill
- figmaSkill
- firmware-feature-writerSkill
- fix-bugSkill
- fix-lintSkill
- frontend-mobile-uiux-designerSkill
- frontend-ui-guardrailsSkill
- gemini-cliSkill
- grok-x-searchSkill
- hermes-chromeSkill
- image-file-readerSkill
- imagegenSkill
- infra-ops-mobile-guardrailsSkill
- layout-reviewSkill
- localizeSkill
- multimodal-lookerSkill
- openai-docsSkill
- optimizeSkill
- parallel-devSkill
- plan-modeSkill
- playwrightSkill
- project-planningSkill
- qa-testerSkill
- refactorSkill
- review-changesSkill
- review-fix-shipSkill
- sandbox-sdkSkill
- screenshotSkill
- security-auditSkill
- security-scanSkill
- security-threat-modelSkill
- source-command-collab-startSkill
- turnstile-spinSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Read Cargo.toml (features, workspace members, lints, edition).
- Distinctive: line 21
Follow the current patterns (error types, logging/tracing, async runtime).
- Distinctive: line 25
Use strongly typed data; avoid “stringly typed” APIs.
- Distinctive: line 26
Prefer ownership at boundaries and borrowing internally.
- Very specific: line 30
If async: avoid blocking calls in async contexts.
- Distinctive: line 33
Add deterministic unit tests for pure logic.
- Distinctive: line 34
Add integration tests for public API and IO boundaries.
- Distinctive: line 35
Avoid timing-dependent tests unless required.
- Distinctive: line 38
Prefer iterators, pattern matching, and small focused functions.
- Very specific: line 39
Avoid unwrap/expect outside tests unless the invariant is proven and documented.
- Very specific: line 40
Avoid unsafe unless necessary.
- Distinctive: line 43
Run the standard checks (fast → slow):
- Very specific: line 48
If useful, run the bundled script: scripts/cargo_verify.sh.
- Distinctive: line 54
Call out compatibility risk if public APIs or features change.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Rust Programmer
Goal: produce idiomatic, safe, and testable Rust with a repeatable verification loop.
Workflow
1) Clarify requirements
- Confirm crate type: library vs binary.
- Confirm runtime: sync vs async (Tokio or not).
- Confirm MSRV/toolchain constraints and target platforms.
- Confirm error strategy (public error type vs opaque errors).
- Identify public API surface and backwards-compat expectations.
2) Inspect the existing crate/workspace
- Read
Cargo.toml(features, workspace members, lints, edition). - Follow the current patterns (error types, logging/tracing, async runtime).
- Locate critical paths via
rgand call sites (avoid introducing a new style).
3) Design before coding
- Use strongly typed data; avoid “stringly typed” APIs.
- Prefer ownership at boundaries and borrowing internally.
- Pick an error model:
- Library:
thiserror+ a stable error enum. - Binary/CLI:
anyhow+Contextat boundaries.
- Library:
- If async: avoid blocking calls in async contexts; use
spawn_blockingfor CPU/IO-bound sync work.
4) TDD (required for behavior changes)
- Add deterministic unit tests for pure logic.
- Add integration tests for public API and IO boundaries.
- Avoid timing-dependent tests unless required; keep retries bounded and explicit.
5) Implement (idiomatic + minimal diff)
- Prefer iterators, pattern matching, and small focused functions.
- Avoid
unwrap/expectoutside tests unless the invariant is proven and documented. - Avoid
unsafeunless necessary; document invariants and add coverage.
6) Verify
Run the standard checks (fast → slow):
cargo fmt --all -- --checkcargo clippy --all-targets --all-features -- -D warnings(or match repo policy)cargo test --all --all-features
If useful, run the bundled script: scripts/cargo_verify.sh.
Output expectations
- State assumptions (toolchain, crate type, runtime).
- Summarize what changed and why.
- List verification (commands, tests).
- Call out compatibility risk if public APIs or features change.
Resources
scripts/cargo_verify.sh: standard local verification runner.references/rust-playbook.md: deeper patterns and decision notes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

