◇ Could this help me?
Yes. Keeping CLAUDE.md focused on durable identity and rules while offloading volatile detail into scoped files is a sound, safe practice: it keeps the always-loaded context small and reduces the chance of stale instructions being read every run. One caveat to apply while adopting: files under .claude/ are not auto-loaded, so anything Claude must always know still belongs in CLAUDE.md or must be explicitly referenced from it. This is a general Claude Code workflow update, not project-specific.
Audit CLAUDE.md and propose a slimmer version that keeps only durable identity and permanent rules (who I am, what I build, how I think, operating principles). Then propose moving the rest into a structured .claude/ folder: session-log.md, project-state.md, tools.md, context.md, and prompts/, scripts/, reference/ subfolders. Show me the proposed split and the trimmed CLAUDE.md before changing any files, and flag anything that must stay in CLAUDE.md because it needs to be loaded every run. Do not delete or overwrite existing files until I approve the plan.