stack-rust
Skill0 starsChanged 2 months agoMITView on GitHub
Apply repository-native Rust and Cargo practices with attention to ownership, concurrency, unsafe boundaries, error contracts, and feature/workspace configuration.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cmoron/claude-configtheir own version, first seen May 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- cmoron/claude-config★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- elixir-docsSkill
- feature-planSkill
- independent-reviewSkill
- multi-repo-changeSkill
- package-readinessSkill
- parallel-deliverySkill
- safe-refactorSkill
- security-reviewSkill
- stack-elixirSkill
- stack-nextjsSkill
- stack-phoenix-liveviewSkill
- stack-svelteSkill
- systematic-debuggingSkill
- technical-writingSkill
- ui-validationSkill
- unslopSkill
- worktree-integrationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 13
Avoid unnecessary allocation, cloning, locking, or async complexity, but optimize only when evidence/scope warrants it.
- Very specific: line 14
Treat unsafe, FFI, raw pointers, filesystem/process/network access, and serialization boundaries as review-sensitive.
- Distinctive: line 15
Keep error types/contracts consistent with surrounding code.
- Distinctive: line 16
Do not enable all features blindly when mutually exclusive or platform-specific features exist.
- Distinctive: line 20
Use repository-native commands.
- Very specific: line 29
Only use --all-features when the repository's feature model makes that valid.
- Distinctive: line 31
Run platform/feature combinations required by the local repository instructions and report combinations not exercised.
≈ “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
Inspect Cargo.toml, workspace membership, feature flags, toolchain files, lint configuration, and applicable AGENTS.md before editing.
Working rules
- Preserve crate/workspace boundaries unless the task requires architectural change.
- Avoid unnecessary allocation, cloning, locking, or async complexity, but optimize only when evidence/scope warrants it.
- Treat
unsafe, FFI, raw pointers, filesystem/process/network access, and serialization boundaries as review-sensitive. - Keep error types/contracts consistent with surrounding code.
- Do not enable all features blindly when mutually exclusive or platform-specific features exist.
Validation
Use repository-native commands. Where supported, typical checks include:
cargo fmt --check
cargo check
cargo test <relevant scope>
cargo clippy --all-targets -- -D warningsOnly use --all-features when the repository's feature model makes that valid.
Run platform/feature combinations required by the local repository instructions and report combinations not exercised.
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.