memory

Maintain tasks/memory.md as a living, durable "what matters" record for the project. Write it for someone taking over the project (or a future session resuming later). Explain where things are, what was decided, and what to watch before proceeding. Treat this as shared behaviour embedded in other skills, not a mandatory standalone step in normal workflows.

Guardrails

• Do not store secrets (API keys, tokens, credentials).
• Keep entries short and durable; avoid duplicating long PRDs or code.
• Update tasks/memory.md in place; do not rewrite the whole file.
• Write in plain language so a junior dev (or another AI) can take over without extra context.
• Prefer inline updates during active skills (prd, design, implement, review, commit).
• Update when worthwhile information emerges.