agentleFS
junhjangjunhjang/claude-harness/.claude/skills/rust-failure-modes/SKILL.md

rust-failure-modes

Skill0 starsChanged 6 months agoMITView on GitHub

Rules for writing or editing Rust code. Forbids #[allow(clippy::*)] without justification, .clone() to escape the borrow checker, .unwrap()/.expect() outside test code. Auto-loads on .rs file edits.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If tempted to break any rule, stop and ask the user.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Apply these rules when touching .rs files. Full rationale: .claude/rules/rust-llm-failures.md.

  1. No #[allow(clippy::*)] without // reason: .... Fix the lint first; suppress only with documented justification next to the attribute.
  2. No .clone() to escape the borrow checker. Try &T, lifetime restructuring, ownership change, Cow<T>, or Arc<T> first. "Compiler complained" is not a reason.
  3. No .unwrap() / .expect() outside #[cfg(test)] or tests/. Use ? and Result<T, E>. Exceptions: provably impossible invariant with // reason: comment, or initialization-time unrecoverable failure (intentional panic). Performance-critical and safety-critical code: zero tolerance.

If tempted to break any rule, stop and ask the user. Do not silently bypass with a suppression.

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.