Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsIf Claude Code seems to ignore a project rule, first check what the session actually loaded: run /context and inspect the Memory files list. Then trace applicable instruction files and imports, check whether AGENTS.md is enabled, and reconcile contradictory guidance at its source. File order does not reliably settle a conflict.
How to see which instruction files Claude Code loaded
- In the affected Claude Code session, run
/context. - Find the Memory files list and note the paths shown.
- Check that the session started from the working directory you expected. The current directory affects which instruction files apply.
If a file is absent from the list, first investigate discovery conditions and project-instruction settings rather than rewriting the file’s contents. A file Claude Code did not load cannot guide that session as project memory. Anthropic’s Claude Code Memory documentation describes the loading behavior.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
Which files to check—and when they apply
| Source | Scope or loading behavior | What to inspect |
|---|---|---|
Ancestor CLAUDE.md and CLAUDE.local.md |
Loaded at startup, from filesystem root toward the working directory. | Check each parent directory through the working directory. In the same directory, CLAUDE.local.md is appended after CLAUDE.md. |
| Nested instruction files | Loaded when Claude works in the matching subtree. | Check the directories containing the files Claude is editing and their applicable nested instructions. |
.claude/rules/ project rules |
Project-level guidance; some rules may be path-scoped. | Review relevant rule files, including any excluded by monorepo claudeMdExcludes configuration. |
~/.claude/rules/ user rules |
Personal guidance across projects; user rules load before project rules. | Look for rules that conflict with the project’s shared requirements. Earlier loading does not make them an override. |
@path imports |
Expanded with the referring CLAUDE.md at startup; imports may recurse up to four hops. |
Follow every reference. Relative paths resolve from the file containing the import; external imports may require approval. |
AGENTS.md |
Loaded under conditions described below; behavior depends on project settings and Claude Code version. | Check whether another applicable CLAUDE file or the Project instructions setting prevents it from loading. |
Record each applicable instruction’s source path, the behavior it governs, whether it is current, and any incompatible direction elsewhere. Keep team-shared requirements in project guidance and individual preferences in user rules.
Why Claude Code may ignore AGENTS.md
In the default setup, Claude Code reads AGENTS.md when there is no CLAUDE.md, .claude/CLAUDE.md, or CLAUDE.local.md in the working directory or an ancestor. If one of those CLAUDE files exists, AGENTS.md is not read by default.
#1 Best Overall
- Run
claude --version. DirectAGENTS.mdsupport requires Claude Code v2.1.277 or later; the documentation describes session cases where it may be unavailable before v2.1.281. - Open
/configand inspect the Project instructions setting. If you expect both formats, chooseclaude-md-and-agents-md, notclaude-mdormanaged-only. - Alternatively, import
AGENTS.mdfromCLAUDE.md. Anthropic recommends this route when direct loading may be unavailable in a session.
How to audit and resolve conflicting instructions
Compare the directions, not their file order
Ancestor files are ordered from filesystem root toward the working directory, and a same-directory CLAUDE.local.md follows CLAUDE.md. But order is not a dependable conflict-resolution rule. Anthropic warns that when instructions conflict, Claude may follow either arbitrarily. A later instruction is not a guaranteed override.
Follow every import
An import uses syntax such as @path/to/file. Relative paths resolve from the importing file, not simply from the shell’s working directory. Imports can recursively bring in files up to four hops; references outside the project may prompt for approval. Import parsing excludes code spans and fenced code blocks. Adding imports organizes guidance but does not reduce context use.
Reconcile the source files
- Remove guidance that is stale, obsolete, or no longer applicable.
- Combine compatible requirements and rewrite remaining rules as specific, actionable instructions.
- Separate shared project requirements from personal preferences so the change goes in the intended file.
- For guidance needed only on matching files, use path-scoped rules rather than loading it everywhere.
For controls that must be technically enforced, use managed settings; CLAUDE.md files express behavioral guidance rather than enforced policy.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use the prompt audit if your version supports it
Claude Code v2.1.283 or later documents the /doctor prompt-audit command. Run it to identify stale or contradictory material, including instructions that reference nonexistent files or commands. Its default scope includes CLAUDE.md, CLAUDE.local.md, AGENTS.md and rules, as well as skills, commands, subagents, and output styles under .claude/ and ~/.claude/. Pass a file or directory to narrow the audit.
The audit reports findings and proposes edits; it does not change files until you ask it to apply them. Review suggested changes against the actual project requirements before accepting them.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep the instruction set maintainable
- Anthropic recommends keeping each
CLAUDE.mdunder 200 lines; longer files consume more context and may reduce adherence. - Files over 4 MiB are skipped.
- Imports can split long guidance into organized files, but they do not reduce context use.
- When unexpected guidance appears, inspect monorepo exclusions, imported files, and nested rules—not just the top-level file.
These command names, settings, and version thresholds are product-documentation details that may change. Confirm current behavior in Anthropic’s Claude Code Memory documentation when troubleshooting a newer release.
Quick Recap
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
