# Antonygiomarxdev Maverick Rust Clean Code > Rust — clean code - Skill: `tomevault-io/antonygiomarxdev-maverick-rust-clean-code` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/antonygiomarxdev-maverick-rust-clean-code` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/antonygiomarxdev-maverick-rust-clean-code/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/antonygiomarxdev-maverick-rust-clean-code --- # 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. --- > Source: [antonygiomarxdev/maverick](https://github.com/antonygiomarxdev/maverick) — distributed by [TomeVault](https://tomevault.io).