init-rust
Skill2 starsChanged 6 months agoNo licenceView on GitHub
Use when initializing Rust best-practices rules in a project, the user invokes `/init-rust`, or a new Rust workspace needs convention rules wired up for an agent. Inputs - target project root, an existing or creatable `.claude/rules/` directory, and confirmation the project targets Rust edition 2024 (rules assume 2024 + MSRV 1.85). Do not use when the user wants language-agnostic project init, framework-specific scaffolding (axum, tauri, leptos, etc.), or actual code generation; use those skills or write code directly. Produces `.claude/rules/rust.md` with `paths: "**/*.rs"` frontmatter covering workspace layout, error handling, async/Tokio, CLI (clap), serde, tracing, type system, process supervision, security, testing, naming, tooling, and Edition 2024 changes. Escalate if `.claude/rules/rust.md` already exists with manual edits, the project is not a Rust workspace, or the user targets an edition older than 2024.
In this repository17 other files it gives its agents.
- apple-calendarSkill
- changelog-prSkill
- cleanupSkill
- code-review-artifactsSkill
- dev-browserSkill
- evaluate-daySkill
- meetingSkill
- north-starSkill
- orchestrator-handoffSkill
- orchestrator-modeSkill
- plan-my-daySkill
- recordSkill
- research-modeSkill
- session-planSkill
- skill-creatorSkill
- solo-handoffSkill
- visual-reviewSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
33 rules. About 0 are common, 1 is distinctive, and 32 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.
32
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.