Remember Skill for Claude
Store a learning, pattern, or decision in the memory system for future recall
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill rememberThe instruction itself
7 sections, as written by the authorRemember - Store Learning in Memory
Store a learning, pattern, or decision in the memory system for future recall.
Usage
/remember <what you learned>
Or with explicit type:
/remember --type WORKING_SOLUTION <what you learned>
Examples
/remember TypeScript hooks require npm install before they work
/remember --type ARCHITECTURAL_DECISION Session affinity uses terminal PID
/remember --type FAILED_APPROACH Don't use subshell for store_learning command
What It Does
- Stores the learning in PostgreSQL with BGE embeddings
- Auto-detects learning type if not specified
- Extracts tags from content
- Returns confirmation with ID
Learning Types
| Type | Use For |
|------|---------|
| WORKING_SOLUTION | Fixes, solutions that worked (default) |
| ARCHITECTURAL_DECISION | Design choices, system structure |
| CODEBASE_PATTERN | Patterns discovered in code |
| FAILED_APPROACH | What didn't work |
| ERROR_FIX | Specific error resolutions |
Execution
When this skill is invoked, run:
cd $CLAUDE_OPC_DIR && PYTHONPATH=. uv run python scripts/core/store_learning.py \
--session-id "manual-$(date +%Y%m%d-%H%M)" \
--type <TYPE or WORKING_SOLUTION> \
--content "<ARGS>" \
--context "manual entry via /remember" \
--confidence medium
Auto-Type Detection
If no --type specified, infer from content:
- Contains "error", "fix", "bug" → ERROR_FIX
- Contains "decided", "chose", "architecture" → ARCHITECTURAL_DECISION
- Contains "pattern", "always", "convention" → CODEBASE_PATTERN
- Contains "failed", "didn't work", "don't" → FAILED_APPROACH
- Default → WORKING_SOLUTION
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take parcadei/remember from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm.
Without those the skill loads but fails at the first command.