Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

rust-best-practices

Estrelas9

Forks0

Atualizado10 de abril de 2026 às 04:13

Idiomatic Rust and engineering hygiene: Clippy, Option/Result patterns, ownership in APIs, iterators, unsafe discipline, async Send boundaries, and public API docs. Use when writing or reviewing Rust, onboarding idioms, or when the user asks for Rust best practices, idioms, or lint hygiene.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

antonygiomarxdev

antonygiomarxdev/maverick

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	rust-best-practices
description	Idiomatic Rust and engineering hygiene: Clippy, Option/Result patterns, ownership in APIs, iterators, unsafe discipline, async Send boundaries, and public API docs. Use when writing or reviewing Rust, onboarding idioms, or when the user asks for Rust best practices, idioms, or lint hygiene.

Rust — best practices

Idioms and tooling

Treat compiler + Clippy as part of the review: new warnings or denies should be resolved, not accumulated.
For where format and lint flags live (CI, aliases, allow policy), see rust-linter-configuration/SKILL.md.
Use type-driven design: let the type system encode states (e.g. builder, sealed traits, newtypes) instead of runtime checks alone.
Prefer explicit error types at boundaries; map to domain errors inside the core rather than leaking io::Error everywhere.

Checklist

API takes the weakest ownership (&, &mut, AsRef) that still works?
No unwrap/expect on paths that can fail in production?
Every unsafe block has a // SAFETY: note and minimal scope?
Async code does not hold MutexGuard or other non-Send state across .await?
New pub items have a one-line doc when behavior is not obvious from the name?

Async and concurrency

Document or bound spawn sites with the same care as public functions (Send, 'static where required).
Prefer structured concurrency (scoped tasks, clear shutdown) over fire-and-forget where lifecycle matters.

When in doubt

Prefer code that a mid-level Rust reader understands without reading three layers of macros.

Mais deste repositório

mesmo repositório

rust-clean-code

antonygiomarxdev/maverick

Clean-code guidance for Rust: function size, modules, error handling, naming, and tests. Use during refactors, readability reviews, or when the user asks for cleaner or more maintainable code without a specific architecture topic.

2026-04-109

rust-linter-configuration

antonygiomarxdev/maverick

Documents Maverick Rust lint and format setup: rustfmt.toml, Clippy flags in CI, cargo aliases, and policy for allow/expect attributes. Use when configuring editors, fixing CI lint failures, adding clippy.toml or rustfmt options, or when the user mentions linters, rustfmt, Clippy, or -D warnings.

2026-04-109

rust-no-magic-values

antonygiomarxdev/maverick

Applies common production Rust practices to remove magic literals: named consts, enums, newtypes, and centralized schema strings. Use when writing or reviewing Rust, when the user mentions magic strings/numbers, duplicated literals, or when designing core versus adapter layers.

2026-04-109

rust-solid-hexagonal

antonygiomarxdev/maverick

Applies SOLID and hexagonal architecture in Rust: traits as ports, implementations in adapters, dependency inversion. Use when designing maverick-core/domain versus adapters, adding persistence or transport, or when the user mentions SOLID, ports, adapters, or coupling.

2026-04-109

name	rust-best-practices
description	Idiomatic Rust and engineering hygiene: Clippy, Option/Result patterns, ownership in APIs, iterators, unsafe discipline, async Send boundaries, and public API docs. Use when writing or reviewing Rust, onboarding idioms, or when the user asks for Rust best practices, idioms, or lint hygiene.

Rust — best practices

Idioms and tooling

Treat compiler + Clippy as part of the review: new warnings or denies should be resolved, not accumulated.
For where format and lint flags live (CI, aliases, allow policy), see rust-linter-configuration/SKILL.md.
Use type-driven design: let the type system encode states (e.g. builder, sealed traits, newtypes) instead of runtime checks alone.
Prefer explicit error types at boundaries; map to domain errors inside the core rather than leaking io::Error everywhere.

Checklist

API takes the weakest ownership (&, &mut, AsRef) that still works?
No unwrap/expect on paths that can fail in production?
Every unsafe block has a // SAFETY: note and minimal scope?
Async code does not hold MutexGuard or other non-Send state across .await?
New pub items have a one-line doc when behavior is not obvious from the name?

Async and concurrency

Document or bound spawn sites with the same care as public functions (Send, 'static where required).
Prefer structured concurrency (scoped tasks, clear shutdown) over fire-and-forget where lifecycle matters.

When in doubt

Prefer code that a mid-level Rust reader understands without reading three layers of macros.