remember

Persist user learnings and preferences across sessions in local memory files.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/stratus/my-claude --skill remember-stratus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/stratus/my-claude/tree/main/skills/remember
Command: npx skills add https://github.com/stratus/my-claude --skill remember-stratus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persisting user learnings and preferences across sessions to maintain context and accelerate workflows.

Core Features & Use Cases

  • Save and organize memory entries in MEMORY.md or topic files under a local auto memory path
  • Keep sensitive data out of git by storing memory locally at ~/.claude/projects/<project-slug>/memory
  • Use cases include capturing user preferences (e.g., editors, tool choices), patterns from debugging, and environment quirks to reuse later

Quick Start

Remember that I prefer tabs in my editor and always use pnpm for project commands.

Frequently Asked Questions about remember

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist user preferences and context across sessions?

To persist user preferences and context across sessions, this skill writes notes to a local memory path using MEMORY.md or topic files, capturing environment quirks, tool choices, and decision patterns for ongoing projects.

Can I save debugging notes and patterns locally without exposing secrets to git?

Yes, you can save debugging notes locally without exposing secrets to git. Memory is stored under ~/.claude/projects/<project-slug>/memory, keeping sensitive data out of version control while preserving context for future sessions.

What's the best way to remember project setup quirks and editor preferences?

The best way to remember project setup quirks and editor preferences is to store them as memory entries in topic files or MEMORY.md, organizing notes by preferences, environment quirks, and debugging patterns for later reuse.

Does this memory persistence approach work for ongoing projects with changing decision patterns?

This memory persistence approach works well for ongoing projects with changing decision patterns. It captures user strategies and environment quirks during debugging and setup tasks, writing to auto memory paths to maintain context as projects evolve.

How does organizing notes in MEMORY.md or topic files help preserve context?

Organizing notes in MEMORY.md or topic files helps preserve context by structuring captured learnings into readable formats under a local memory path. This allows future sessions to retrieve user preferences, debugging patterns, and environment details efficiently.

When do I need a memory persistence skill for my workflow automation?

You need a memory persistence skill for workflow automation when you repeatedly lose context between sessions, forcing you to re-explain preferences, tool choices, and environment quirks. It accelerates workflows by storing these details locally for automatic reuse.