How do I install the Ccc Memory skill?

Run npx skillmds@latest add kevinzai/ccc-memory in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ccc Memory safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ccc Memory?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ccc Memory free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ccc Memory?

KevinZai (@kevinzai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ccc Memory by kevinzai — Agent Skill

Name: Ccc Memory
Author: KevinZai

File contents

/ccc-memory — Two-Tier Persistent Memory

Claude Code sessions forget everything at the end. Memory makes the important bits stick.

When to use

After resolving a tricky bug — save the root cause so next time the same class of issue is faster
After making an architectural decision — record the reasoning so future-you doesn't re-argue with past-you
When a project grows beyond one CLAUDE.md section — split into a memory/ tree
Before a big /clear when you want to carry forward a specific insight

Not for

Session-scoped state that ends with this session — use /ccc-save-session for that
Searchable cross-project knowledge — use /ccc-recall for that
Per-skill notes — put those inline in the skill's body

How it works

Two layers, different load patterns:

Layer 1 — CLAUDE.md (always-loaded)

Every file Claude reads in a session is relative to CLAUDE.md. Put here:

Project type + tech stack (once)
Key paths + conventions
Commands Kevin runs daily
Cross-cutting style rules

Keep it tight — everything here costs context on every turn.

Layer 2 — memory/ directory (on-demand)

Dated markdown files for things that don't belong in the always-loaded layer:

memory/YYYY-MM-DD-{slug}.md — daily learnings, decisions, corrections
memory/decisions/ — one file per big call (why we picked Postgres over Mongo)
memory/gotchas/ — known footguns (tailwind v4 syntax, framer-motion v11 rename)
memory/preferences.md — curated long-term prefs that didn't fit CLAUDE.md

Load on demand by reading the specific file — Claude sees only what's needed.

Process

Start of session: ls memory/ (if exists) → skim filenames → read the few that matter for today's task
When you learn something: add a dated entry to memory/YYYY-MM-DD-{slug}.md
Corrections from Kevin: append to memory/preferences.md with date — corrective framing ("You should X — are you doing it?")
Weekly (or before big work): consolidate — move frequently-referenced items from memory/ into CLAUDE.md; prune stale dated notes

Example

After Kevin says "no more /ccc-style: prefix, use /ccc-*" — you write:

memory/2026-04-23-ccc-prefix-dash.md

## Correction: /ccc- not /ccc:

Date: 2026-04-23
Source: Kevin (chat)

All skill names use dash prefix /ccc-* not colon /ccc:*. Colon form is stale
from v3. Check: grep -rn "/ccc:" should return zero results outside CHANGELOG.

Test that guards this: commander/tests/dispatch-security.test.js — runKc('ccc:') rejected.

Depends on

tasks/memory/ or memory/ directory in project root (create if missing)
Project CLAUDE.md as Layer 1

Adapted from knowledge-work-plugins/productivity/memory-management under Apache-2.0 license. Fitted to CC Commander's save-session / resume-session pattern.

⚙️ Fable contract: plan before build · verifier ≠ worker · prove before alarm · loops need gates · leave durable state — rules/fable-method.md

---name: ccc-memorydescription: Two-tier persistent memory for Claude Code sessions. Layer 1 is CLAUDE.md (always-loaded context). Layer 2 is a memory/ directory with dated notes, decisions, and…---# /ccc-memory — Two-Tier Persistent MemoryClaude Code sessions forget everything at the end. Memory makes the important bits stick.## When to use- After resolving a tricky bug — save the root cause so next time the same class of issue is faster- After making an architectural decision — record the reasoning so future-you doesn't re-argue with past-you- When a project grows beyond one CLAUDE.md section — split into a memory/ tree- Before a big /clear when you want to carry forward a specific insight## Not for- Session-scoped state that ends with this session — use /ccc-save-session for that- Searchable cross-project knowledge — use /ccc-recall for that- Per-skill notes — put those inline in the skill's body## How it worksTwo layers, different load patterns:### Layer 1 — CLAUDE.md (always-loaded)Every file Claude reads in a session is relative to CLAUDE.md. Put here:- Project type + tech stack (once)- Key paths + conventions- Commands Kevin runs daily- Cross-cutting style rulesKeep it tight — everything here costs context on every turn.### Layer 2 — memory/ directory (on-demand)Dated markdown files for things that don't belong in the always-loaded layer:- `memory/YYYY-MM-DD-{slug}.md` — daily learnings, decisions, corrections- `memory/decisions/` — one file per big call (why we picked Postgres over Mongo)- `memory/gotchas/` — known footguns (tailwind v4 syntax, framer-motion v11 rename)- `memory/preferences.md` — curated long-term prefs that didn't fit CLAUDE.mdLoad on demand by reading the specific file — Claude sees only what's needed.## Process1. **Start of session:** `ls memory/` (if exists) → skim filenames → read the few that matter for today's task2. **When you learn something:** add a dated entry to `memory/YYYY-MM-DD-{slug}.md`3. **Corrections from Kevin:** append to `memory/preferences.md` with date — corrective framing ("You should X — are you doing it?")4. **Weekly (or before big work):** consolidate — move frequently-referenced items from memory/ into CLAUDE.md; prune stale dated notes## ExampleAfter Kevin says "no more /ccc-style: prefix, use /ccc-*" — you write:```memory/2026-04-23-ccc-prefix-dash.md## Correction: /ccc- not /ccc:Date: 2026-04-23Source: Kevin (chat)All skill names use dash prefix /ccc-* not colon /ccc:*. Colon form is stalefrom v3. Check: grep -rn "/ccc:" should return zero results outside CHANGELOG.Test that guards this: commander/tests/dispatch-security.test.js — runKc('ccc:') rejected.```## Depends on- `tasks/memory/` or `memory/` directory in project root (create if missing)- Project CLAUDE.md as Layer 1---Adapted from `knowledge-work-plugins/productivity/memory-management` under Apache-2.0 license. Fitted to CC Commander's save-session / resume-session pattern.---> ⚙️ **Fable contract:** plan before build · verifier ≠ worker · prove before alarm · loops need gates · leave durable state — `rules/fable-method.md`

Frequently asked questions

Ccc Memory