rc-memory

Solid

The single place for RC's durable, cross-session memory and learning. Records and recalls curated project facts (decisions, conventions, gotchas, glossary), distills recurring corrections/workflows into confidence-scored learnings, and harvests a proven multi-step golden path into a project-local skill. Use to consult memory before working, to record durable facts or distilled learnings afterward, and whenever a task only worked after several attempts or revealed a non-obvious operational route — reaching a database, deploying, running migrations, verifying live — in which case harvest it unprompted. Do not use for workflow/task-scoped notes (use rc-workflow-memory) or for on-demand reflection on a diff (use lesson-learned).

AI & Automation 19 stars 1 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
43
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Memory The one place for what RC should remember about *this project* across turns and sessions. It is project-scoped only — never copy memory or learnings to another project or a global location. It holds three kinds of durable knowledge as plain markdown — no database, no binary, and this skill never edits source code: 1. **Facts** — curated decisions, conventions, gotchas, glossary, and context (`.rc/memory/`). 2. **Learnings** — recurring corrections/workflows distilled into confidence-scored `trigger → action` rules (`.rc/memory/`, the continuous-learning loop fed by the `observe` hook). 3. **Golden paths** — a proven multi-step operational route, harvested into a project-local skill, because a route does not survive being compressed into one line. It is separate from `rc-workflow-memory` (ephemeral, per-workflow notes under `.rc/tasks/<slug>/`) and from `lesson-learned` (on-demand reflection on a diff, not a store). ## Routing The shape of the knowledge decides where it goes; the first match wins: | The knowledge is… | Goes to | | --- | --- | | a standalone statement — a decision, convention, gotcha, term | **A — Facts** | | a `trigger → action` reflex that fits one line | **B — Learnings** | | a multi-step route with commands, a required order, and dead-ends | **C — Golden paths** | | specific to one task's execution | `rc-workflow-memory`, not here | | a one-off unlikely to recur | nowhere — drop it | ## Store layout ``` .rc/memory/ INDEX.md ...

Details

Author
rodolfochicone
Repository
rodolfochicone/rc-project
Created
1 months ago
Last Updated
2 weeks ago
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

rc-workflow-memory

Maintains workflow-scoped task memory for RC runs using .rc/tasks/{name}/memory/ files. Use when a task prompt provides workflow memory paths and requires the agent to read, update, compact, and promote durable context across PRD task executions. Do not use for PR review remediation, global user preferences, or programmatic event-log summarization.

19 Updated 2 weeks ago
rodolfochicone
AI & Automation Solid

rc-lessons

Deterministic loop-lessons machine — records grounded engineering lessons from verification signals (AC gaps, surviving mutants, spec deviations, gate failures) and loads the corroborated ones at plan/design time, so autonomous or repeated loops stop re-making the same mistake. All bookkeeping (IDs, distinct-feature recurrence, candidate→confirmed promotion, quarantine, prune) is owned by scripts/lessons.mjs, not prose. Use to record a lesson after a verify/review failure, or to load confirmed lessons before planning a task or roadmap phase. Do not use for user-correction trigger→action learnings (rc-memory), per-task working notes (rc-workflow-memory), or on-demand reflection on a diff.

19 Updated 2 weeks ago
rodolfochicone
AI & Automation Listed

cf-remember

Extract project knowledge from conversation to docs/memory — for AI recall in future sessions. Use when the user wants to save project context, capture decisions, document conventions, or preserve knowledge — e.g. "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "note this", "record this convention". Auto-invoke when: (1) a bug fix had a non-obvious root cause, a workaround, or took multiple attempts — save to bugs/; (2) an explicit architecture or approach decision was made — save to decisions/; (3) a new project-wide convention or pattern was established — save to conventions/; (4) a substantial session ends with new feature flows, non-obvious API behavior, or gotchas — save to features/. Do NOT auto-invoke for trivial fixes, simple config changes, or purely educational exchanges (use $cf-learn for those). Unlike $cf-learn (educational notes for humans), this saves project context for AI recall.

3 Updated today
dinhanhthi