Remember

What Is Remember?

The "Remember" skill for Claude Code is a specialized command-line utility designed to explicitly save critical knowledge to Claude’s auto-memory system. Unlike passive or automatic memory capture, this skill empowers developers to proactively record discoveries, insights, or conventions that are considered too important to risk being missed by automated processes. Each memory entry is timestamped and contextualized, ensuring that vital project-specific or global knowledge is always readily accessible for future reference.

The tool is particularly valuable in complex development environments where critical information—such as debugging breakthroughs, architectural decisions, and unique project conventions—must be retained with high fidelity. The command is invoked using /si:remember, followed by a descriptive string detailing the information to be preserved.

Why Use Remember?

In fast-paced engineering teams, information can be ephemeral—shared in passing, buried in chat logs, or lost in the churn of daily development. Relying solely on automated capture mechanisms risks omitting key context or subtle but important insights. The "Remember" skill addresses this challenge by providing a deliberate mechanism to record and preserve knowledge that might otherwise be overlooked.

Typical scenarios benefiting from explicit memory capture include:

• Debugging insights that resolved elusive issues after hours of investigation.
• Unwritten project conventions not documented elsewhere.
• Tool-specific workarounds or gotchas.
• Architectural or technology decisions that shape future work.
• Personal or team preferences that influence code style or review processes.

By making the act of remembering explicit, teams ensure that important lessons, conventions, and decisions remain accessible—ultimately improving onboarding, context transfer, and operational continuity.

How to Get Started

To use the "Remember" skill, ensure it is installed and accessible in your Claude Code environment. The typical workflow involves invoking the command with a concise, descriptive message about what should be remembered.

Basic Usage

/si:remember <what to remember>

Example 1:

Capturing a Tool-Specific Insight

/si:remember "Jest needs --forceExit flag or it hangs on DB tests"

Example 2:

Documenting a Project Convention

/si:remember "We use barrel exports in src/components/"

Example 3:

Recording a Debugging Breakthrough

/si:remember "CORS errors on /api/upload are caused by the CDN, not the backend"

Each entry is timestamped and saved within a project-specific or global memory directory, providing a durable, contextual history of important knowledge.

Key Features

• Explicit Knowledge Capture: Empowers users to proactively preserve critical insights rather than relying on automatic memory.
• Timestamped Entries: Each entry is automatically timestamped, creating an auditable record of when knowledge was acquired or decisions were made.
• Contextual Storage: Memory entries are stored with context, distinguishing between project-specific and global knowledge, ensuring relevance and retrievability.
• Duplicate Checking: The workflow includes logic to prevent redundant entries by checking for duplicates in the project’s memory directory.
• Simple Syntax: The /si:remember command is easy to use and integrates seamlessly into daily development workflows.

Best Practices

• Be Descriptive but Concise: When recording a memory, balance detail with brevity. Include enough context to make the entry meaningful to future readers, but avoid unnecessary verbosity.
• Specify Scope: Indicate whether the information is project-specific or applicable globally. This helps with organization and retrieval.
• Capture Why It Matters: When possible, include the rationale or context behind the fact. For example, instead of just stating a convention, briefly mention why it was adopted.
• Avoid Sensitive Data: Do not store secrets, credentials, or personally identifiable information using the "Remember" skill.
• Integrate Into Workflows: Make it a habit to invoke /si:remember immediately after uncovering important knowledge, especially when it does not belong in permanent documentation like README.md.

Example:

Including Context and Rationale

/si:remember "The /api/auth endpoint uses a custom JWT library, not passport, because passport did not support our multi-tenant requirements."

Important Notes

• Not a Replacement for Documentation: While "Remember" is useful for capturing ephemeral or situational knowledge, it is not a substitute for comprehensive documentation. Use it to complement, not replace, formal project docs.
• Memory Location: Entries are stored in $HOME/.claude/projects/<project-path>/me, ensuring project-level isolation and easy retrieval.
• Review Regularly: Periodically review and prune memory entries to maintain relevance and accuracy, especially as projects evolve.
• Command Syntax: The command expects a single string argument. For multi-line or highly detailed entries, consider linking to external documentation.
• Collaboration: Encourage team-wide usage to build a collective knowledge base that benefits all contributors.

The "Remember" skill is a powerful addition to any engineering team’s toolkit, enabling deliberate, reliable knowledge capture that transcends individual memory and fosters a culture of shared learning.