rust-style-guide
Apply this Rust style guide when writing, reviewing, refactoring, or configuring Rust code for this project. Covers Rust 2024/MSRV, library vs application conventions, public API design, errors, panics, ownership and cloning, async/Tokio/concurrency, tracing, rustfmt/Clippy, testing with nextest, and unsafe/macro policy. Also use when setting up new Rust projects, investigating Rust performance, verifying library releases, or reviewing Rust code changes.
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Rust Style Guide
Use this skill to apply the project's Rust style conventions while writing, reviewing, refactoring, or configuring Rust code.
Location: This skill's supporting files live in
.fabro/skills/rust-style-guide/at the repository root. Every linked path below (guidelines.md,guidelines/*.md,workflows/*.md) is relative to that directory. Read them with that prefix — e.g..fabro/skills/rust-style-guide/guidelines.md.
Supporting Files
- guidelines.md - index of Rust style policy pages. Load this for ordinary Rust work, then load only the guideline pages relevant to the task.
- workflows/new-rust-project.md - workflow for creating or configuring a new Rust crate, workspace, CLI, library, service, or application.
- workflows/reusable-library-release.md - workflow for verifying reusable library releases, feature combinations, dependency checks, and out-of-box builds.
- workflows/performance-investigation.md - workflow for measuring, profiling, and changing performance-sensitive Rust code.
- workflows/code-review-refactor.md - workflow for reviewing, refactoring, or changing existing Rust code.
Routing Examples
| Task | Load |
|---|---|
| Create a new Rust project | workflows/new-rust-project.md, guidelines.md |
| Verify a reusable library release | workflows/reusable-library-release.md, guidelines.md |
| Investigate performance | workflows/performance-investigation.md, guidelines.md |
| Review or refactor code | workflows/code-review-refactor.md, guidelines.md |
| Define a public library error type | guidelines.md, library/application errors, error propagation, public API evolution |
| Handle top-level CLI/application errors | guidelines.md, library/application errors, error propagation, panics |
| Choose enum vs trait vs trait object | guidelines.md, enums vs traits, trait design, public API evolution |
| Add a domain ID or validated value | guidelines.md, newtypes, constructors, validation |
| Write async service code | guidelines.md, async runtime, task lifecycle, shutdown, logging |
| Add instrumentation | guidelines.md, logging and observability, error messages |
| Configure formatting, lints, or tests | guidelines.md, rustfmt, Clippy, Cargo, CI |
| Review unsafe code or macros | guidelines.md, unsafe and macros, public API evolution |
Core Behavior
- Load only the pages the task needs; guideline pages are the policy, workflow pages are the procedures.
- Prefer concrete Rust guidance over language tutorials.
- Keep library/application differences explicit.
- Use the project's OO-leaning Rust default without forcing inheritance-shaped designs.
- Prefer strong, compiler-backed types over primitive-heavy APIs.
- Apply the loaded rules directly. Ask one focused question only when required project context is missing.
- Repository
fkukuck/fabro
- Revision
ac667f5
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.