M15 Anti Pattern

The m15-anti-pattern skill helps developers identify and refactor common code anti-patterns during code reviews, focusing on Rust-specific issues like excessive cloning, unwrap calls in production, and fighting the borrow checker. It's designed for Rust developers and code reviewers who need to distinguish between solving symptoms versus root causes, and who want guidance on more idiomatic approaches. The skill maps anti-patterns to their underlying design problems and traces them to related skills for deeper understanding of ownership, error handling, and domain design.

skills.sh installs: 5.6K
GitHub stars: 1.3K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add zhanghandong/rust-skills --skill m15-anti-pattern --agent claude-code

Installs into .claude/skills of the current project.

Files

Anti-Patterns

Layer 2: Design Choices

Core Question

Is this pattern hiding a design problem?

When reviewing code:

Is this solving the symptom or the cause?
Is there a more idiomatic approach?
Does this fight or flow with Rust?

Anti-Pattern → Better Pattern

Anti-Pattern	Why Bad	Better
`.clone()` everywhere	Hides ownership issues	Proper references or ownership
`.unwrap()` in production	Runtime panics	`?`, `expect`, or handling
`Rc` when single owner	Unnecessary overhead	Simple ownership
`unsafe` for convenience	UB risk	Find safe pattern
OOP via `Deref`	Misleading API	Composition, traits
Giant match arms	Unmaintainable	Extract to methods
`String` everywhere	Allocation waste	`&str`, `Cow<str>`
Ignoring `#[must_use]`	Lost errors	Handle or `let _ =`