When Claude ignores you

Claude Code mostly does what you ask. When it doesn't, it's almost always one of 5 problems. This lesson is the diagnostic routine.

Problem 1: CLAUDE.md is too long or contradictory

Symptom: Claude ignores specific rules you've set.

Cause: your CLAUDE.md is past ~60 lines globally or ~80 project-level. Important rules get buried.

Fix

Audit my global CLAUDE.md. Flag anything: that doesn't apply to every project, that's redundant with other rules, that contradicts another rule. Target under 25 lines.

Problem 2: Context is over 50%

Symptom: Claude repeats output, forgets earlier instructions, hallucinates details.

Fix: /wrapup + start a fresh session. Module 13 Lesson 3.

Problem 3: /startup wasn't run

Symptom: Claude doesn't know what project you're in, asks context questions you already answered last session.

Fix: run /startup. If you're already mid-session without it:

Run /startup now to load the project memory for this folder.

Problem 4: Wrong project folder

Symptom: Claude can't find files you expect. Using wrong MCPs. Referencing wrong client.

Fix: check where Claude Code is running

What folder are you running in? Show me the working directory.

If wrong folder, /wrapup, close, cd to the right folder, start again.

Problem 5: Instruction is ambiguous

Symptom: Claude does something other than what you wanted.

Fix: give more specific instructions. Instead of "make the report better", "increase the font size in section headings to 24px + add a one-line summary at the top of each section".

The diagnostic routine

When Claude isn't doing what you want, in order

1. Did you run /startup? Context-check: "show me which project memory is loaded"
2. Check context %: "how full is the context?" - if over 50%, /wrapup + restart
3. Check CLAUDE.md: "read my CLAUDE.md files and summarise the rules that apply to the current task"
4. Check your instruction: was it specific? Re-phrase more precisely
5. If still wrong: /wrapup + start a totally fresh session. Often resets weird state.

When to rebuild CLAUDE.md

If Claude repeatedly ignores a specific rule, it's usually because:

• The rule is vague ("be terse" - terse how?)
• The rule is buried in a 100-line file
• The rule contradicts another rule
• The rule is in the wrong file (project-specific rule in global, or vice versa)

Move the rule to the right file. Tighten the wording. Use CAPS for non-negotiable.

Action items

☐ Memorise the 5-step diagnostic routine

☐ When Claude's off, check CLAUDE.md + context % before blaming Claude

☐ Fresh session resets most weird state

Next lesson: When MCPs + connections fail.

Exercises

1. Review the concepts covered in this lesson: When Claude ignores you.
2. Write down your key takeaway from this lesson.
3. Practice running any commands or prompts mentioned above inside your terminal.