agentleFS
Sign inStart free
wado-langwado-lang/wado/.claude/skills/rust/SKILL.md

rust

Skill120 starsChanged 15 days agoMITView on GitHub

Workspace-specific Rust rules that override common habits: panic instead of dummy or no-op fallbacks, never catch a panic outside tests, enums over unclear bool parameters, no wildcard match arms, dependencies managed in the workspace Cargo.toml, 2024 edition, zero warnings and clippy lints. Read before writing or editing Rust (.rs) code.

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use java, node and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • testdino-hqSkill

    java

    Google's official Java style guide. Covers 2-space indentation, 100-char line limit, naming conventions, braces, imports, Javadoc, exception handling, lambdas, and streams. Enforces @Override annotations and specific imports.

    Also in 4 projects that use this

  • mcollinaSkill

    node

    Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging, and more. Use when setting up Node.js projects with native TypeScript support, configuring type stripping (--experimental-strip-types), writing Node 22+ TypeScript without a build step, or when the user mentions 'native TypeScript in Node', 'strip types', 'Node 22 TypeScript', '.ts files without compilation', 'ts-node alternative', or needs guidance on error handling, graceful shutdown, flaky tests, profiling, or environment configuration in Node.js. Helps configure tsconfig.json for type stripping, set up package.json scripts, handle module resolution and import extensions, and apply robust patterns across the full Node.js stack.

    Also in 3 projects that use this

  • rogue-dev-studioSkill

    python

    Python 3.13 with uv package manager via mise. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `python` work when listed in TEAM.yaml or explicitly requested.

    Also in 6 projects that use this

  • rogue-dev-studioSkill

    golang

    Go development environment. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `golang` work when listed in TEAM.yaml or explicitly requested.

    Also in 3 projects that use this

  • trotsky1997Skill

    ast-grep

    Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.

    Also in 3 projects that use this

  • OpenAISkill

    nextjs

    Next.js App Router expert guidance. Use when building, debugging, or architecting Next.js applications — routing, Server Components, Server Actions, Cache Components, layouts, middleware/proxy, data fetching, rendering strategies, and deployment on Vercel.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Use the panic! macro instead of falling back to meaningless dummy values or no-op implementations.

    line 7
  2. Very specific:

    Use the 2024 edition.

    line 10
  3. Very specific:

    Keep the code free of compiler warnings and Clippy lints.

    line 11
  4. Very specific:

    Avoid wildcard match arms (_ => ...) unless absolutely necessary.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “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
  • Manage dependencies in the workspace Cargo.toml.
  • Use the panic! macro instead of falling back to meaningless dummy values or no-op implementations.
  • Never catch a panic in production code. A panic is a bug, and it ends the run. So there is no catch_unwind, a task is joined through wado_host::sync::joined rather than its JoinError turned into an error value, and a thread's panic is resumed where it is joined. Tests may catch one.
  • Take an enum rather than a bool where the call site would not say what the flag means. f(x, true) makes the reader open f, and f(x, Mode::Strict) does not.
  • Use the 2024 edition.
  • Keep the code free of compiler warnings and Clippy lints. mise run clippy runs -D warnings, so any warning or lint fails it.
  • Import every item you name. A crate:: or super:: path goes in a use item at the top of the module; where the item is read, write its name. use crate::elaborator::sem::Ty; then Ty, never crate::elaborator::sem::Ty inline. Alias a collision (use crate::ast::Ty as AstTy;) rather than spelling the path out. A use inside a function body counts as inline. A pub(in …) is exempt: it names a scope rather than reading an item, and Rust admits no import there. mise run check-rust-paths gates this against the empty baseline scripts/rust-inline-paths.json. Its detector (package-gale/tools/rust_inline_paths.wado) parses with the Gale Rust grammar, so the grammar decides what counts as a path. mise run list-rust-paths <file.rs>… lists what a file carries.
  • Avoid wildcard match arms (_ => ...) unless absolutely necessary.

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