compound

Persisting development session learnings into CLAUDE.md involves analyzing git diff and git log outputs to identify architectural decisions and gotchas, then writing durable rules into .claude/rules/ to guide future sessions.

Documenting stack-specific debugging decisions from a git diff involves extracting reusable patterns and fixed mistakes, then writing them into CLAUDE.md for broad conventions or creating topic-specific rule files under .claude/rules/ for framework quirks.

Updating CLAUDE.md without duplicating existing rules requires analyzing the current session's git changes and checking existing instructions to ensure only new, broadly applicable conventions and anti-patterns are appended to the file.

Yes, you can extract reusable rules from refactoring sessions for frameworks like TanStack and Drizzle by identifying stack-specific quirks and conventions from the git log, then persisting them as topic-specific rule files under .claude/rules/.

You should avoid writing session learnings into project rules when the insights are one-off fixes, speculative conclusions, or non-reusable implementation details that do not represent durable architectural conventions or recurring stack-specific gotchas.