Diagnose why a Claude Project stopped following instructions
When to use: Your Project worked, you added stuff, now it ignores key rules.
Flow
-
Run the project auditUse rootnode-project-audit on my Project system prompt + instructions.✓ Copied→ Six-dimension scorecard with specific failures called out
-
Check for anti-patternsNow rootnode-anti-pattern-detection — which of the 7 patterns do I have?✓ Copied→ Named patterns (e.g. 'conflicting directives', 'buried critical instruction')
-
Rebalance memoryApply rootnode-memory-optimization — where should each rule actually live?✓ Copied→ Recommendation on what belongs in system prompt vs project docs vs user memory
Outcome: A diagnosed Project with a concrete fix list.
Pitfalls
- Audit report is long; you only fix the easy ones — Start with anti-patterns flagged — those block the rest