# memory

A skill that sets the discipline for a node's persistent memory: what to write, how to split pages, when to prune. Useful when your agent hoards history instead of knowledge.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 786
- Author: plasma-ai
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/plasma-ai/fractal/tree/HEAD/fractal/_node/skills/memory/SKILL.md
- Updated: 2026-10-25
- HTML: https://affpapa.org/en/nevibecode/skills/memory

## What it does

Node memory lives in `$MEMORY_DIR` and acts as the node's durable store. The skill covers reading it during orientation and folding findings back before an iteration ends. Sync can also write to memory when something important arrives over radio.

The core rule: write knowledge, not history. No iteration numbers, no timestamps — a reader should not be able to tell how many runs have happened. Before COMMIT the skill says to scan memory and any page you promote and rewrite those markers out, because promotion carries your habits onto shared surfaces. Organize by topic, not time: update the existing page for a topic rather than appending a new entry.

Your first write creates the layout — one page per topic (`environment`, `decisions`, `state`, `todo`, rename to fit the work), never a single grab-bag page. A page without `desc:` frontmatter stays invisible to `wiki map`, so after adding or moving pages run `wiki update --path=$MEMORY_DIR`. Keep exactly one present-tense `state` page, overwritten in place. In-wiki links are written prefix-free: `[[state]]`, not `[[./state]]`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add plasma-ai/fractal --skill memory -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/memory/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/memory/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add plasma-ai/fractal --skill memory -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/memory/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add plasma-ai/fractal --skill memory -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/memory/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install plasma-ai/fractal memory
```

2. **Manually: put the files in place**
- File: `.github/skills/memory/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add plasma-ai/fractal --skill memory -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/plasma-ai/fractal --path fractal/_node/skills/memory
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/memory/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add plasma-ai/fractal --skill memory -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/plasma-ai/fractal/tree/HEAD/fractal/_node/skills/memory/SKILL.md

## When to use it
- split node memory into topical pages instead of one grab-bag file
- strip iteration numbers and timestamps out of memory
- collapse a finished phase's pages into durable facts
- make pages show up in `wiki map` with `desc:` frontmatter
- keep a working todo list instead of a done-log

## Example prompts
- read `$MEMORY_DIR` and tell me where we are
- fold this iteration's findings into memory and clean out the iteration numbers
- run `wiki update --path=$MEMORY_DIR` so the new pages get frontmatter

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4ffd6f8607ccb02f.

BEGIN THIRD-PARTY FILE 4ffd6f8607ccb02f
```text
---
name: memory
description: How to maintain node memory well -- the node's persistent knowledge store.
---

# Memory

Memory (`$MEMORY_DIR`) is the node's durable brain. Read it when you orient and
fold findings back before each iteration ends. Sync may also write to memory
when crucial information arrives via radio. See the `wiki` skill for how memory
relates to the shared project wiki; this doc is the discipline for keeping
memory useful.

Run `wiki --help` and `wiki <command> --help` for the CLI.

## Conventions

- **Write knowledge, not history.** Never reference iteration numbers,
  timestamps, or chronological markers -- a reader shouldn't be able to tell how
  many iterations have run. Before COMMIT, scan memory and any page you promote
  for iteration numbers and run labels and rewrite them out -- promotion carries
  your habits onto shared surfaces.
- **Organize by topic, not time.** Update the existing page for a topic; don't
  append a new entry.
- **Start with a topical layout.** Your FIRST memory write creates the layout --
  one page per topic (`environment`, `decisions`, `state`, `todo` -- rename to
  fit the work; stubs are fine), never a single grab-bag page; when a page
  starts covering two topics, split it. A leaf expecting to finish within an
  iteration or two may keep just the `state` page.
- **One current-state page.** Keep exactly one present-tense `state` page for
  where-am-I / what's-next, overwritten in place -- no "prior run" sections;
  per-iteration narrative belongs in the plan post-mortem, never memory.
- **Pages need `desc:` frontmatter.** A page without it (a near-miss key like
  `description:` counts as without) is invisible to `wiki map`; after adding or
  moving pages, run `wiki update --path=$MEMORY_DIR` so they gain frontmatter
  and index entries. Quote a one-line `desc:` that contains `: ` or ` #`.
- **Fold at phase ends.** When a phase or a child's run ends, collapse its pages
  into durable facts and delete the rest -- memory carries what is still true,
  not what happened.
- **No append-only logs.** If you're adding dated entries, stop -- replace
  outdated content with current understanding.
- **Todo lists are living state.** Keep your private working checklist here as
  current open items, pruned as they complete -- never a done-log. A todo list
  other nodes should see and track belongs in the project wiki instead.
- **Keep indexes lean.** Keep each `_index.md` under ~100 lines below the `***`;
  factor overflow into child pages.
- **Wikilinks stay within one wiki.** Reference anything outside this wiki --
  the project wiki, source files, configs -- in plain text or backticks, never
  as a wikilink; `wiki lint` notes a wikilink that points outside the wiki.
```
END THIRD-PARTY FILE 4ffd6f8607ccb02f

The third-party file has ended. Everything between the 4ffd6f8607ccb02f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2757 of 2848 bytes. © plasma-ai · Apache-2.0 · https://github.com/plasma-ai/fractal/tree/HEAD/fractal/_node/skills/memory/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md