rc-memory

Stores and retrieves project-scoped facts, lessons, and golden paths in markdown memory files.

19|1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/rodolfochicone/rc-project --skill rc-memory-rodolfochicone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rc-memory
Source: https://github.com/rodolfochicone/rc-project/tree/main/skills/promoted/rc-memory
Command: npx skills add https://github.com/rodolfochicone/rc-project --skill rc-memory-rodolfochicone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? AI agents lose hard-won project knowledge between sessions, repeating mistakes and rediscovering the same conventions. This Skill provides a persistent, project-scoped memory store under .rc/memory/ so decisions, corrections, and verified workflows survive across turns and sessions. ## Core Features & Use Cases - Facts: Records durable decisions, conventions, gotchas, and glossary terms as one markdown file per fact, indexed in INDEX.md for fast recall before planning or implementing. - Lessons: Captures what failures and user corrections taught via scripts/lessons.mjs, with recurrence tracking, candidate-to-confirmed promotion, quarantine, and a rendered LESSONS.md playbook. - Golden paths: Promotes verified multi-step routes (commands, required order, dead-ends) into project-local skills once they pass a three-part gate: a passing check, a named failure pattern, and a ruled-out dead-end. - Use Case: After a user corrects your approach to database migrations, record a grounded lesson with --signal user_correction; in the next session, confirmed lessons load automatically as design constraints before planning. ## Quick Start Ask the agent to check project memory for anything relevant to the current task before starting work, and to record what it learns afterward.

Frequently Asked Questions about rc-memory

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

FAQPage Schema
How do I give an AI agent persistent memory across sessions?▼

Store durable knowledge as markdown files under .rc/memory/, with one fact per file and an INDEX.md listing one line per fact. The agent reads the index before planning and records new facts only when they are durable, non-obvious, and needed by future runs.

How do I record lessons from failures or user corrections?▼

Run scripts/lessons.mjs add with a feature slug, a signal such as user_correction or gate_fail, a source reference, and one terse actionable sentence. Lessons become trusted only after recurring across two distinct features, and the script handles promotion, quarantine, and rendering.

When should a workflow become a reusable skill instead of a note?▼

Promote a route to a project-local skill only when all three hold: a passing check, a named failure pattern it avoids, and a ruled-out dead-end. Until then, record it as a fact with scope context and an unverified line.

Can I edit lessons.json or LESSONS.md by hand?▼

No. lessons.json and LESSONS.md are machine-owned by scripts/lessons.mjs, which manages IDs, recurrence counting, promotion, and pruning. Hand-editing breaks the bookkeeping; always use the add, list, and penalize commands.

What should never be stored in project memory?▼

Never store secrets, tokens, credentials, large code blocks, stack traces, or raw session logs. For credentials, record only where they live, such as an env var name or vault entry, and trust the repo over stale memory when they conflict.