- 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 throughwado_host::sync::joinedrather than itsJoinErrorturned into an error value, and a thread's panic is resumed where it is joined. Tests may catch one. - Take an
enumrather than aboolwhere the call site would not say what the flag means.f(x, true)makes the reader openf, andf(x, Mode::Strict)does not. - Use the
2024edition. - Keep the code free of compiler warnings and Clippy lints.
mise run clippyruns-D warnings, so any warning or lint fails it. - Import every item you name. A
crate::orsuper::path goes in auseitem at the top of the module; where the item is read, write its name.use crate::elaborator::sem::Ty;thenTy, nevercrate::elaborator::sem::Tyinline. Alias a collision (use crate::ast::Ty as AstTy;) rather than spelling the path out. Auseinside a function body counts as inline. Apub(in …)is exempt: it names a scope rather than reading an item, and Rust admits no import there.mise run check-rust-pathsgates this against the empty baselinescripts/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.
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.
- 1 file
- 2 KB
- Updated 3 weeks ago
- GitHub
Use this Skill: https://skilld.dev/gh/wado-lang/wado/rust Nothing lands on disk. Nothing to clean up.
Edit a local copy. It keeps the author and licence.
≈87 tokens for metadata: the name and description. ≈407 when used: this file.
Description uses 4.3% of example budget
Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.
- A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.
In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈347 characters, or 4.3%.
The 1% threshold is a size suggestion. Longer descriptions can still fit.
Your model, settings, and other Skills decide how much text your Agent can read.
Example settings and source
The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.
Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.
Source: SKILL.md on GitHub
Skill behaviors
No rule matched.
skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.
skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.
Third-party checks
Provenance
Signed by skilld at b208ba0. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.
Last checked against GitHub yesterday.