agentleFS
Sign inStart free
GiammeGiamme/linear-spanks/skills/extras/tech-rust/SKILL.md

tech-rust

Skill1 starsChanged 28 days agoMITView on GitHub

Technology skill loaded when writing systems or backend code in Rust.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When writing Rust, prioritize memory safety, zero-cost abstractions, and idiomatic error handling:

    line 11
  2. Very specific:

    Error Handling: Never use unwrap() or expect() in production code.

    line 14
  3. Very specific:

    Pattern Matching: Use exhaustive match statements instead of long if/else chains, especially when dealing with Option and Result types.

    line 15
  4. Very specific:

    Iterators: Prefer iterator methods (.map(), .filter(), .fold()) over manual for loops where possible for conciseness and optimization.

    line 16
  5. Very specific:

    Clippy: Ensure code passes cargo clippy without warnings.

    line 17

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Rust Best Practices

Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.

When writing Rust, prioritize memory safety, zero-cost abstractions, and idiomatic error handling:

  1. Ownership & Borrowing: Minimize cloning (.clone()). Prefer passing references (&T or &mut T) and structure your data to satisfy the borrow checker naturally.
  2. Error Handling: Never use unwrap() or expect() in production code. Propagate errors using the ? operator and return Result<T, E>.
  3. Pattern Matching: Use exhaustive match statements instead of long if/else chains, especially when dealing with Option and Result types.
  4. Iterators: Prefer iterator methods (.map(), .filter(), .fold()) over manual for loops where possible for conciseness and optimization.
  5. Clippy: Ensure code passes cargo clippy without warnings. Adhere strictly to the linter's idiomatic suggestions.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free