rustoria
AGENTS.md0 starsChanged 35 days agoMITView on GitHub
This repository is a Rust engineering skill system for AI coding agents.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository15 other files it gives its agents.
- rustoriaSkill
- rust-debuggingSkill
- rust-dependenciesSkill
- rust-fundamentalsSkill
- rust-axumSkill
- rust-clapSkill
- rust-dieselSkill
- rust-ratatuiSkill
- rust-rayonSkill
- rust-serdeSkill
- rust-tokioSkill
- rust-productionSkill
- rust-code-auditSkill
- rust-stdSkill
- rust-unsafe-checkerSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
Native Rust first: Prefer std over third-party crates.
- Very specific: line 40
No blocking in async: Use spawn_blocking or async-native crates.
- Distinctive: line 50
Always: analyze first, plan second, modify third, validate fourth.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
Agent Instructions
This repository is a Rust engineering skill system for AI coding agents.
Quick start
- Load the root router (
SKILL.md) for any Rust task. - Route to the appropriate skill based on the task.
- Load references when deep dives are needed.
- Consult examples for compile-tested patterns.
Skill catalog
Native core
rust-fundamentals— language basicsrust-std— standard library API discoveryrust-production— production engineeringrust-debugging— debuggingrust-unsafe-checker— unsafe Rust reviewrust-dependencies— dependency management
Security
rust-code-audit— repository security audit
Library extensions
rust-tokio— async runtimerust-axum— HTTPrust-serde— serializationrust-diesel— databasesrust-rayon— parallelismrust-clap— CLIrust-ratatui— TUI
Principles
- Native Rust first. Prefer
stdover third-party crates. - No blocking in async. Use
spawn_blockingor async-native crates. - No casual
unwrap()in production paths. - Version-sensitive advice names its version.
- Examples use edition 2021.
Agent execution safety
- Read-only actions (inspect, search, analyze, explain, review) are always safe.
- Mutating actions (create, modify, delete, install, commit, push, execute) require user awareness.
- Destructive operations require explicit user confirmation.
- Always: analyze first, plan second, modify third, validate fourth.
Validation
bash scripts/validate.sh
bash scripts/test-triggers.shDoes 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.

