rust-io
Skill0 starsChanged 2 months agoMITView on GitHub
Use for Rust CLI data-flow changes involving bounded buffering, record parsing, byte fidelity, or read/write completion.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- rust-buildSkill
- rust-cli-interfaceSkill
- rust-cli-testingSkill
- rust-concurrencySkill
- rust-debuggingSkill
- rust-designSkill
- rust-distributionSkill
- rust-errorsSkill
- rust-filesystemSkill
- rust-idiomaticSkill
- rust-implementSkill
- rust-memorySkill
- rust-performanceSkill
- rust-processesSkill
- rust-testingSkill
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
- Distinctive: line 10
Use Read, BufRead, Write, and existing parsers before building an I/O abstraction.
≈ “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 I/O
Streaming. Trace bytes from their source to their consumer, including what must remain buffered between steps. Honor supplied requirements and preserve settled choices outside the requested change; resolve only what the task leaves open.
Use Read, BufRead, Write, and existing parsers before building an I/O abstraction. Stream growing input when the operation permits it; whole-input reads can be appropriate for demonstrably bounded data. Identify when sorting, aggregation, or lookahead genuinely requires retention and bound or externalize that state.
Choose bytes or UTF-8 text from the actual contract. Preserve delimiters, final unterminated records, and invalid-byte behavior where meaningful. A read may return fewer bytes than requested. A short read is not EOF, and a buffer boundary is not a record boundary.
Reuse buffers where repeated allocation matters. Reading by lines still permits one unbounded line; enforce required record limits while reading, before allocating the complete record. Bound decompressed data and pending output as well as source bytes. Treat a configured limit as an explicit error rather than silent truncation.
Lock standard streams for sustained access and buffer repeated small writes when useful. Use complete-write operations where required and observe the final flush result; BufWriter drop can hide errors. Balance batching with interactive latency and let slow consumers constrain production.
Handle Interrupted and BrokenPipe at the correct boundary using the command's policy. Propagate other failures without converting them to clean EOF or success.
Check the changed I/O property with controlled readers or writers: relevant chunk splits, record limits, short writes, or late failures, not all of them for every change. Use real pipes when backpressure or downstream closure is the claim. For review, explain the risk without editing; for implementation, report observed byte/error behavior and any untested OS boundary. Do not add throughput benchmarks unless throughput is part of the claim.
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.

