Skill

remember

Saves user preferences, constraints, or facts (e.g., 'always use bun', 'never auto-commit', 'user name is Alex') to REMEMBER.md. Persists across sessions with global or project scope.

developer-tools

npx claudepluginhub hatawong/claude-recap --plugin claude-recap

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Saves a user preference, constraint, or fact to REMEMBER.md so it persists across sessions. The user chooses scope (global or project).

SKILL.md

Similar Skills

remember

9.2k

Saves key project knowledge explicitly to MEMORY.md via /si:remember for reliable recall. Checks duplicates, warns on size, suggests CLAUDE.md promotion.

self-improving-agent

memory

1.9k

Loads and applies project memories from prior sessions for consistent decisions, conventions, and preferences. Stores new entries automatically or via /remember.

4 files2 tools

claude-never-forgets

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

Stats

Stars25

Forks2

Last CommitMar 3, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

remember

Overview

Saves a user preference, constraint, or fact to REMEMBER.md so it persists across sessions. The user chooses scope (global or project).

When to Use

User explicitly says "remember...", "always...", "never...", "don't forget..."

User states a clear preference or constraint worth persisting (e.g., "I use bun not npm")

User provides identity or context info they'd want every session to know

Instructions

Distill what the user wants to remember into one concise line (imperative form, no filler).

Good: "Use bun instead of npm for all package management"
Bad: "The user mentioned they prefer bun over npm and would like us to always use it"

Ask the user which scope using AskUserQuestion:

Which scope should this apply to? - Global: applies to all projects - Project: applies only to this project

Get the plugin scripts path from the SessionStart injection in your context: Plugin scripts path: /path/to/scripts

Run the remember script:

bash "<plugin_scripts_path>/remember.sh" "<scope>" "<content>"

Where:

plugin_scripts_path: the path from SessionStart injection

scope: global or project

content: the distilled one-liner (quote it properly for shell)

Rules

One entry per invocation — don't batch multiple items

Distill to a clear imperative statement, not a description of what happened

If the user's intent is ambiguous, ask for clarification before writing

Do NOT remember session-specific or temporary information (e.g., "I'm debugging auth today")

Examples

User says

Distilled entry

"Remember I always use bun"

Use bun instead of npm for package management

"Never auto-commit without asking"

Never auto-commit; always ask before committing

"My name is Alex"

User's name is Alex

"For this project, always run tests with --verbose"

Run tests with --verbose flag (project scope)

remember

Overview

Saves a user preference, constraint, or fact to REMEMBER.md so it persists across sessions. The user chooses scope (global or project).

When to Use

User explicitly says "remember...", "always...", "never...", "don't forget..."
User states a clear preference or constraint worth persisting (e.g., "I use bun not npm")
User provides identity or context info they'd want every session to know

Instructions

Distill what the user wants to remember into one concise line (imperative form, no filler).
- Good: "Use bun instead of npm for all package management"
- Bad: "The user mentioned they prefer bun over npm and would like us to always use it"
Ask the user which scope using AskUserQuestion:

Which scope should this apply to?
- Global: applies to all projects
- Project: applies only to this project

Get the plugin scripts path from the SessionStart injection in your context: Plugin scripts path: /path/to/scripts
Run the remember script:

bash "<plugin_scripts_path>/remember.sh" "<scope>" "<content>"

Where:

plugin_scripts_path: the path from SessionStart injection
scope: global or project
content: the distilled one-liner (quote it properly for shell)

Rules

One entry per invocation — don't batch multiple items
Distill to a clear imperative statement, not a description of what happened
If the user's intent is ambiguous, ask for clarification before writing
Do NOT remember session-specific or temporary information (e.g., "I'm debugging auth today")

Examples

User says	Distilled entry
"Remember I always use bun"	`Use bun instead of npm for package management`
"Never auto-commit without asking"	`Never auto-commit; always ask before committing`
"My name is Alex"	`User's name is Alex`
"For this project, always run tests with --verbose"	`Run tests with --verbose flag` (project scope)