File Organization + Memory Strategies

Learning objectives

• Explain what the memory tool does and how it differs from the Project knowledge base.
• Apply "just-in-time" retrieval instead of front-loading all context every session.
• Implement the "define once, reference everywhere" shared-context-file pattern.
• Design a folder structure for a Reddit-ops Claude Code repo covering skills, memory, agents, and context.
• Decide, for any given fact, whether it belongs in memory, the Project KB, or CLAUDE.md.

Prerequisites: Lesson 6.2.1.

Core concepts

The memory tool lets Claude create, read, update, and delete files in a persistent memory directory that survives across sessions, enabling "just-in-time" retrieval instead of front-loading everything at the start of every conversation; Anthropic reports that combining the memory tool with context editing improved performance 39% over baseline (Anthropic memory-tool docs; context-management blog). The practical distinction to hold onto: the Project knowledge base (Lesson 6.1.1) is the source-of-truth library a human curates and uploads; the memory tool is scratch space Claude itself writes to and reads from between sessions, a running log of what it learned last time, not a document you authored.

A practical file pattern worth adopting from working marketing-ops practitioners: keep one shared context file, product, audience, positioning, defined once, that every skill reads from, so all outputs stay on-brand, the same "define once, reference everywhere" logic as Project custom instructions (coreyhaines31/marketingskills; Insightful Pipe's brand-voice skill pattern). For a Reddit operation, that means a single reddit-context/ folder every skill, subagent, and slash command points back to, rather than five skills each holding a slightly stale copy of your ICP.

reddit-ops/
├── CLAUDE.md                       # top-level conventions, ethics rules
├── reddit-context/
│   ├── icp.md                      # define once
│   ├── brand-voice.md               # define once
│   ├── subreddit-map.md            # define once
│   └── ethics-red-lines.md         # define once
├── .claude/
│   ├── skills/
│   │   ├── reddit-intent-scorer/
│   │   ├── reddit-reply-drafter/
│   │   └── reddit-humanizer/
│   ├── agents/                     # subagent definitions (Lesson 6.3.3)
│   └── memory/                     # Claude-written, cross-session scratch
└── weekly-digests/                 # Skill 6.4.1 output, human-reviewed

Every skill's SKILL.md should reference reddit-context/ files rather than restating their contents, this is what keeps a rebrand, an ICP shift, or a subreddit-map update a single-file edit instead of a five-file hunt. Alex Op's synthesis of how MCP, Skills, subagents, hooks, CLAUDE.md, and slash commands fit together (alexop.dev) is worth reading end to end before you finalize this structure, since getting the file layout wrong now compounds across every lesson left in this stage.

Video lessons

Supporting reading

• Memory tool, Claude Platform Docs (https://platform.claude.com/docs/en/agents-and-tools/tool-use/memory-tool), the primary source on persistent, cross-session memory-file CRUD.
• coreyhaines31/marketingskills (GitHub) (https://github.com/coreyhaines31/marketingskills), a concrete, forkable library of marketing SKILL.md files built on the shared-context-file pattern this lesson teaches.
• Understanding Claude Code's Full Stack: MCP, Skills, Subagents, and Hooks Explained, alexop.dev (https://alexop.dev/posts/understanding-claude-code-full-stack/), the clearest synthesis of how every primitive in this repo structure fits together.

Exercise

Stand up the reddit-ops/ folder structure above. Migrate your Stage 1-5 ICP, brand-voice, and subreddit-map content into the four reddit-context/ files, then rewrite reddit-intent-scorer's SKILL.md to reference them instead of restating their contents.

Assignment

Submit your finished repo tree (or a screenshot/listing of it) plus a short note on one piece of context you almost duplicated across two skills before catching it with this pattern.

Claude workflow

• Skill idea: a "context-drift-checker" skill that periodically diffs the shared reddit-context/ files against recent memory-tool entries to catch drift before it produces off-brand output.
• Automation: a weekly memory-tool write-back that logs what changed in the Reddit landscape (new subreddits found, ICP language that tested better) as a candidate update to the human-curated context files, never as a silent auto-edit.

Expected outcomes

• reddit-ops/ repo structure live with a shared reddit-context/ folder.
• reddit-intent-scorer skill successfully refactored to reference shared files instead of restating them.
• Can explain the memory tool vs. Project knowledge base distinction without notes.