Software Anti-Patterns Catalog

Overview

Anti-patterns are recurring solutions that seem reasonable but cause more harm than good. Unlike code smells (surface indicators -- see detect-code-smells), anti-patterns describe complete failed solutions at class, module, or system scope. Each entry includes root cause, symptoms, and remediation with cross-references to fix skills.

When to Use

• Architecture review reveals no clear ownership of responsibilities
• A codebase is routinely described as "nobody dares touch that"
• A single change requires coordinating edits across many files/teams
• Bug fixes in one area consistently break unrelated areas

Quick Reference