rootnode-anti-pattern-detectionlisted

# Anti-Pattern Detection for Claude Projects > **Calibration:** Tier 2 (Sonnet-graceful) — designed and tested against Opus 5 + Sonnet 5 dual-primary. Runs correctly on Sonnet 4.6 (legacy-graceful) with slightly less depth on multi-dimensional analysis; on Haiku 4.5 with extended thinking; fallback-graceful on Opus 4.8. Effort default is `high` on Opus 5 and Sonnet 5; step down to `medium` for cost-sensitive runs where evals show quality holds. See repository README for model compatibility. Detect and fix the seven structural mistakes that cause Claude Projects to underperform. Each pattern has specific detection criteria and symptoms — diagnose by evidence, not intuition. ## Critical: Evidence-First Diagnosis Never assert a pattern without citing the specific component that exhibits it. For every pattern you detect, quote the exact text from the user's Custom Instructions or knowledge files that demonstrates the problem. If you cannot point to concrete evidence, the pattern is not confirmed. ## Reasoning discipline A defensible diagnosis shows its evidence. Observe the specific file contents, structural features, duplication instances, and layer assignments; name the anti-pattern they match against the detection criteria; then explain the severity and impact. A summary diagnosis without the observation-pattern-impact chain is harder to act on and harder to dispute — the hard rule (evidence-first, above) keeps the assertion valid; the walk-through keeps it actionable.