remember

Store user-defined learnings and decisions in PostgreSQL with BGE embeddings.

3.9k|296|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill remember-parcadei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/remember
Command: npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill remember-parcadei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of losing valuable insights, solutions, and decisions made during a session by providing a persistent memory system.

Core Features & Use Cases

  • Persistent Storage: Saves learnings, patterns, and decisions in a PostgreSQL database.
  • Type Classification: Automatically detects or allows manual specification of learning types (e.g., WORKING_SOLUTION, ARCHITECTURAL_DECISION, FAILED_APPROACH).
  • Tagging: Extracts relevant tags from the content for easier retrieval.
  • Use Case: After solving a complex bug, you can use /remember to store the fix, ensuring that knowledge isn't lost and can be easily recalled if the same issue arises again.

Quick Start

Use the remember skill to store the following learning: TypeScript hooks require npm install before they work.

Frequently Asked Questions about remember

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

FAQPage Schema
How do I store learnings and codebase patterns for future recall?

You can store learnings for future recall by saving user-defined solutions and decisions into a persistent memory system using PostgreSQL and BGE embeddings, which automatically extracts tags for easier retrieval.

What types of knowledge can I persist in a memory system?

Specific learning types you can persist include WORKING_SOLUTION, ARCHITECTURAL_DECISION, CODEBASE_PATTERN, FAILED_APPROACH, and ERROR_FIX, managed via auto-detection or manual assignment.

How do I save an error fix so the same issue doesn't happen again?

Save an error fix by classifying it as an ERROR_FIX learning type and storing it in the PostgreSQL database, where automatic tag extraction ensures the knowledge is easily retrieved if the issue arises again.

Does storing knowledge patterns require manual tagging?

Storing knowledge patterns does not require manual tagging because the system automatically extracts relevant tags from the content directly to enhance future recall alongside type classification.

Do I need PostgreSQL to persist architectural decisions and working solutions?

You need PostgreSQL to persist architectural decisions and working solutions, as the memory system relies on it alongside BGE embeddings to store and manage your classified learnings.

When should I save a failed approach to a persistent memory database?

Save a failed approach to a persistent memory database immediately after identifying it does not work, categorizing it as a FAILED_APPROACH to prevent repeating the same debugging efforts later.