Skill

Memory Storage

Store important information in persistent memory. Fires when the user shares decisions, preferences, project updates, or says "remember this."

From engram

Install

Run in your terminal

npx claudepluginhub anthropics/claude-plugins-community --plugin engram

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.7k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad-pro-skills

43.8k

Stats

Stars0

Forks0

Last CommitMar 13, 2026

Actions

View Source View Plugin View on GitHub View README

When to Remember

User makes an important decision ("let's go with PostgreSQL for the database")

User states a preference ("I prefer tabs over spaces" / "no em-dashes in copy")

Project milestones or status changes ("v2.0 shipped today")

Key people, roles, or relationships ("Sarah is the new engineering lead")

Lessons learned ("the deploy failed because we forgot to run migrations")

User explicitly asks you to remember something

Architecture decisions, technical choices, or design rationale

Best Practices

Be specific and include context: WHO decided WHAT and WHY

Include dates when relevant: "As of March 2026, the API uses v2 endpoints"

Do not store sensitive information (passwords, API keys, personal secrets)

Store the decision AND the reasoning, not just the outcome

Do not over-store -- not every message needs to be remembered. Focus on information that would be valuable in a future session.

Let the user know when you have stored something important: "Got it, I'll remember that."

Memory Storage

You can store important information in persistent memory using the engram_remember tool. This lets you remember things across sessions.

When to Remember

User makes an important decision ("let's go with PostgreSQL for the database")
User states a preference ("I prefer tabs over spaces" / "no em-dashes in copy")
Project milestones or status changes ("v2.0 shipped today")
Key people, roles, or relationships ("Sarah is the new engineering lead")
Lessons learned ("the deploy failed because we forgot to run migrations")
User explicitly asks you to remember something
Architecture decisions, technical choices, or design rationale

How to Remember

engram_remember({ text: "Thomas decided to use PostgreSQL instead of MySQL for the new project. Reason: better JSON support and the team has more experience with it." })

Best Practices

Be specific and include context: WHO decided WHAT and WHY
Include dates when relevant: "As of March 2026, the API uses v2 endpoints"
Do not store sensitive information (passwords, API keys, personal secrets)
Store the decision AND the reasoning, not just the outcome
Do not over-store -- not every message needs to be remembered. Focus on information that would be valuable in a future session.
Let the user know when you have stored something important: "Got it, I'll remember that."