memory-curator

Append structured architectural decisions and insights to memory.jsonl.

181|22|Updated Nov 13, 2025
One-click install
npx skills add https://github.com/markmdev/meridian --skill memory-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-curator
Source: https://github.com/markmdev/meridian/tree/main/.claude/skills/memory-curator
Command: npx skills add https://github.com/markmdev/meridian --skill memory-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Claude often struggles with context loss and forgetting past decisions or lessons learned across sessions. This Skill provides a persistent, searchable memory for critical architectural decisions, problems solved, and insights gained, ensuring that valuable knowledge is never lost and preventing the AI from repeating mistakes.

Core Features & Use Cases

  • Persistent Knowledge Base: Automatically store and retrieve architectural decisions, lessons learned, and problem resolutions in memory.jsonl.
  • Structured Documentation: Enforce a consistent format for memory entries, making them easy to read, reference, and query for future tasks.
  • Use Case: After fixing a complex performance bottleneck or making a significant architectural choice, use this Skill to document the root cause, the solution, and the architectural implications, ensuring future projects avoid similar pitfalls and build upon past successes.

Quick Start

Use the memory-curator skill to add a new memory entry. The summary is "Refactored authentication flow to use JWTs for better scalability." Tag it with "architecture,decision". Link it to "TASK-091 src/auth/jwt.ts".

Frequently Asked Questions about memory-curator

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

FAQPage Schema
How do I document architectural decisions so I don't repeat past mistakes?

Document architectural decisions and lessons learned by persisting them into memory.jsonl using the add_memory_entry.py script. Each entry captures the decision, root cause, solution, and implications with a mem-XXXX ID and UTC timestamp, creating a searchable knowledge base that prevents repeating past pitfalls.

What's the best way to persist codebase insights and knowledge across sessions?

Use structured memory entries to capture insights, problems solved, and patterns discovered. The memory-curator Skill enforces consistent JSON formatting with summary, tags, and file links, ensuring knowledge remains accessible and queryable for future work without context loss.

Can I link architectural decisions to specific code files and track them over time?

Yes. Each memory entry includes links to relevant code locations and a UTC timestamp. The memory.jsonl format supports tagging decisions with categories like architecture or performance, making it easy to retrieve and reference related decisions across your codebase history.

How do I organize and retrieve documented lessons learned from past projects?

Memory entries are tagged with keywords like architecture, decision, or performance and stored in memory.jsonl with consistent JSON structure. Query by tags or links to quickly surface relevant lessons learned and architectural decisions from previous work.

What format does the memory system use for storing and retrieving documented insights?

The memory-curator Skill stores insights as JSON objects appended to memory.jsonl with fields for summary, tags, links to code files, a mem-XXXX ID, and UTC timestamp. This structured format makes entries machine-readable and easy to parse for future analysis.

Do I need to manually format entries when documenting architectural decisions?

No. The add_memory_entry.py script enforces a strict workflow that handles formatting automatically. You provide the summary, tags, and file links; the script generates the mem-XXXX ID, timestamp, and JSON structure before appending to memory.jsonl.