compound-learnings

To save architectural decisions and gotchas for future Claude sessions, trigger the ship phase to capture durable learnings, which writes recorded conventions and file paths directly to CLAUDE.md and auto-memory.

The best way to update documentation when API or architecture changes is to use a knowledge-capture workflow that automatically refreshes docs and records decisions during the ship phase of engineering projects.

Auto-memory records project conventions and knowledge by capturing durable learnings from completed work, storing important decisions and gotchas to accelerate future sessions and reduce repeat work.

Yes, you should wait until the ship phase to capture knowledge for CLAUDE.md, as this is when the workflow records decisions, gotchas, and conventions after completing a significant work session.

You can preserve file paths and engineering decisions across sessions by writing durable knowledge to CLAUDE.md and updating auto-memory, ensuring future sessions reuse captured conventions.

Your Claude session repeats work because it lacks durable knowledge capture; recording decisions and gotchas to CLAUDE.md during the ship phase empowers future sessions with prior architectural context.