원클릭으로 Manus에서 모든 스킬 실행

rust-clean-code

스타9

포크0

업데이트2026년 4월 10일 04:13

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

antonygiomarxdev

antonygiomarxdev/maverick

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Rust — clean code

Practical principles (community-aligned)

Readability over micro-optimization unless a path is measured as hot.
Explicit over implicit: clear return types; visible conversions (.into(), TryFrom).
Errors as values: propagate Result; prefer ? over nested if let Err.
Less shared mutable state; when it exists, keep boundaries clear (Arc, channels, or single-owner design).

Review checklist

Does the function fit one screen and does its name describe the observable effect?
Is every pub justified, or can visibility shrink?
Any unwrap/expect outside tests or documented invariants?
Do tests assert observable behavior, not brittle implementation details?

Warning signs

Many parameters of the same primitive type → context struct or builder.
Heavy clone to appease the borrow checker without revisiting API boundaries → redesign ownership at the boundary.

이 저장소의 다른 Skills

같은 저장소

rust-best-practices

antonygiomarxdev/maverick

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.

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-clean-code
description	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.

Rust — clean code

Practical principles (community-aligned)

Readability over micro-optimization unless a path is measured as hot.
Explicit over implicit: clear return types; visible conversions (.into(), TryFrom).
Errors as values: propagate Result; prefer ? over nested if let Err.
Less shared mutable state; when it exists, keep boundaries clear (Arc, channels, or single-owner design).

Review checklist

Does the function fit one screen and does its name describe the observable effect?
Is every pub justified, or can visibility shrink?
Any unwrap/expect outside tests or documented invariants?
Do tests assert observable behavior, not brittle implementation details?

Warning signs

Many parameters of the same primitive type → context struct or builder.
Heavy clone to appease the borrow checker without revisiting API boundaries → redesign ownership at the boundary.