Cf Remember

Extract project knowledge from conversation to docs/memory — for AI recall in future sessions. Use when the user wants to save project context, capture decisions, document conventions, or preserve knowledge from the current session — e.g. "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "save for later", "don't forget", "note this", "record this convention", "preserve this knowledge". Auto-invoke when ANY of these signals appear: (1) A bug fix (via cf-fix or cf-sys-debug) involved a non-obvious root cause, a workaround, or required multiple failed attempts before resolving — save to bugs/ so future sessions avoid the same trap. (2) An explicit architecture or approach decision was made in conversation — e.g. "we chose X over Y because...", "we decided to use X instead of Y", "the reason we're doing X is..." — save to decisions/. (3) A new project-wide convention or pattern was established during implementation — e.g. a naming rule, an API design pattern, a structural constraint — save to conventions/. (4) A substantial session ends with newly documented feature flows, non-obvious API behavior, or gotchas that would save significant time in a future session — save to features/. Do NOT auto-invoke for: trivial one-line fixes, simple config changes, purely educational exchanges (use /cf-learn for those), or knowledge already obvious from reading the code. Unlike /cf-learn (educational notes for humans), this saves project context for AI recall.

mkdir -p ~/.claude/skills/cf-remember
curl -L https://claudskills.com/skills/cf-remember/SKILL.md \
  -o ~/.claude/skills/cf-remember/SKILL.md

@misc{cf-remember-2026,
  author    = {ClaudSkills},
  title     = {Cf Remember [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/cf-remember/}
}