This teaches you to look at working Rust code and see unnecessary complexity. It's built around four diagnostic questions you run before touching anything: Is this parameter just being forwarded? Is this feature flag still needed? Is this file doing too many things? Does this struct have mutually exclusive optional fields? Then it gives you six transformation patterns with actual coordination sequences: how to remove forwarded parameters from the bottom up, how to split a 950-line file by domain instead of layer, how to migrate types incrementally with From bridges instead of big-bang rewrites. The crate extraction section includes before-and-after compile time measurements, which is rare and useful. It's opinionated about when to add abstraction versus when to delete it.
npx skills add https://github.com/pproenca/dot-skills --skill rust-refactor