update-memory-bank

To persist session knowledge, document decisions, patterns, progress, learnings, and next steps into persistent memory-bank files like activeContext.md and progress.md. This ensures critical context survives resets.

The best way to document development patterns is recording concrete examples drawn directly from the session into systemPatterns.md, which guides future work by preserving the exact implementation details.

Track project progress by logging completed tasks with dates, locations, validation, and blockers into progress.md, showing momentum and status across development sprints.

Yes, you can capture decisions with rationale, alternatives considered, and trade-offs into projectbrief.md and productContext.md, preserving the reasoning behind choices to survive context resets.

No dependencies are required to maintain a memory-bank. You only need to update standard markdown files like techContext.md and activeContext.md with actionable takeaways and explicit next steps.

Session context disappears due to context resets, but you can structure ephemeral knowledge into persistent documentation by updating activeContext.md, progress.md, systemPatterns.md, techContext.md, productContext.md, and projectbrief.md.