CCA-F: Claude Certified Architect — Foundations

Question

You have documented API error-handling conventions in a CLAUDE.md file at your project root, specifying that endpoint handlers should use a custom ApiError class. After several sessions, you notice that Claude Code sometimes follows these conventions and sometimes instead uses generic try/catch blocks with string messages. This inconsistency appears random across different coding sessions.

What is the most efficient first diagnostic step to take?

Explanation

The /memory command is the built-in Claude Code tool for inspecting exactly which CLAUDE.md, CLAUDE.local.md, and rules files are currently loaded in a session, along with their load order. Since Claude Code memory loading depends on factors like the current working directory, recursive traversal up the directory tree, and on-demand loading of subdirectory files, inconsistent behavior across sessions is most efficiently diagnosed by first confirming whether the project CLAUDE.md is actually being loaded every time, rather than speculating about conflicting rule files, insufficient detail, or needing new path-scoped rules files.

Learn more

CCA-F: Claude Certified Architect — Foundations

AstroTutor

Notes

Readiness

QuestionQ62

Community Discussion