M15 Anti Pattern

What it does

The m15-anti-pattern skill helps identify and avoid common anti-patterns in software development, particularly within Rust projects. It analyzes code structures, design choices, and implementation strategies to flag practices that may lead to inefficiencies, bugs, or maintenance challenges.

When to use it

• During code reviews to catch problematic patterns before they are merged into the main branch.
• When refactoring legacy code to ensure adherence to best practices.
• Before deploying a new feature to verify that no harmful design choices were made.
• As part of an automated CI/CD pipeline to enforce coding standards and quality.

Key capabilities

• Detects overuse of global state or singletons in Rust applications.
• Identifies unnecessary complexity in function signatures or module structures.
• Highlights improper error handling patterns that may lead to silent failures.
• Warns against unsafe code practices that violate Rust's safety guarantees.

Example prompts

• "Analyze this Rust module for anti-patterns."
• "Check the use of unsafe blocks in this file for potential issues."
• "Review the function signature and suggest improvements."

Tips & gotchas

• This skill works best when used alongside a linter or static analysis tool for comprehensive code quality checks.
• It may not catch all anti-patterns, especially those that are context-specific or require domain knowledge to identify.