remember

This skill provides an explicit '/si:remember' command that saves an important fact, convention, or hard-won insight to a project-scoped auto-memory file so Claude will see it at the start of every future session. It addresses the problem of losing valuable context between sessions: rather than relying on Claude to automatically notice and retain a discovery, the user can deliberately pin it. It is meant for knowledge important enough that automatic capture is too risky to depend on.

The workflow parses the user's input into a concrete fact, optional rationale, and scope; checks the project's MEMORY.md for duplicate entries via a keyword grep and offers to update rather than duplicate; then appends a concise one-line entry. It warns when MEMORY.md approaches a 200-line budget, suggests promoting rule-like statements to CLAUDE.md via a companion '/si:promote' command, and confirms what was saved. The documentation emphasizes concise, actionable entries (concrete commands and values over vague concepts) and gives examples such as build/test commands, project conventions, tool gotchas, and architecture decisions.

It targets developers using Claude as a coding assistant across recurring sessions on a project, especially those who want a lightweight, reviewable memory layer. Notably, the skill's own guidance explicitly instructs users never to store credentials, tokens, or secrets in memory files, and to route enforced rules and cross-project knowledge to CLAUDE.md instead. Use cases include capturing debugging insights, CI requirements, and personal preferences that should persist.