Rust Implement

A structured workflow for writing Rust that treats code quality as a multi-pass discipline rather than getting it perfect on the first try. You design types and signatures first, implement with strict error handling rules (every `?` gets context, no wildcards in match arms), then actively simplify by removing unnecessary abstractions. The fourth pass runs automated lints plus a manual checklist. What makes this useful is the specificity: it includes nine concrete transformations like replacing boolean parameters with enums and using BTreeMap for anything serialized. The thread-through plumbing section and ownership decision tree are legitimately helpful references when you're knee-deep in borrow checker fights. It's opinionated about anyhow versus thiserror and when to Box::pin futures, which saves you from relitigating those decisions every time.

skills.sh installs: 246
GitHub stars: 222
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pproenca/dot-skills --skill rust-implement --agent claude-code

Installs into .claude/skills of the current project.

Files

Rust Implementation Discipline

Write code in passes. Experts don't produce perfect code in one shot -- they design, implement, review, and simplify. Follow this process for every module you write.

Pass 1: Design Types and Signatures

Before writing any implementation, write ONLY the type definitions and function signatures. No bodies. No logic.

Ask yourself these questions before moving on:

Can any enum state represent an invalid combination? If yes, restructure so invalid states are unrepresentable.
Are all parameters self-documenting? Replace bool params with enums (Transformation 2).
Does every struct that will be serialized or compared use BTreeMap, not HashMap (Transformation 3)?
Do config structs derive Default (Transformation 6)?
Would a caller confuse the order of String parameters? Use newtypes.
Does any struct have 2+ Option<T> fields where only one combination is valid at a time? Convert to an enum (Transformation 8).
Does any function take 4+ parameters? Replace with an args struct (Transformation 9).