This skill should be used when the user asks to 'set up memory', 'create memory files', 'create MEMORY.md', 'set up topic files', 'improve memory organization', 'what should I remember', 'how to structure memory files', 'MEMORY.md is too long', 'what goes in memory vs topic files', 'memory best practices', or wants to establish a persistent knowledge base across Claude Code sessions.
SkillScore80Maintained
Automatic
◆Knowledge Management pack
Last verified 8/13/2026
What it changes
Passed 18 of 23 test cases with the skill, and 15 of 23 without it.
Without skill64%
With skill80%
Checks it passed that the model alone missed
Requires a column indicating when to consult each topic file
Points to references/patterns.md for writing style guides and anti-patterns
References examples/MEMORY.md and examples/topic-file.md for starter templates
and 6 more in the full report
7 fixed13 passed either way2 still failing3 broke
Pass-rate lift
+16 pp
Tokens
+42%
Agent turns
0%
Response time
-51%
Model gemini-3.6-flashMeasured 8/13/2026v120 of 25 cases passed with skill · 23 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
When creating the topic file index in `MEMORY.md`, what specific guidance must be provided alongside each listed file name?
What was checked, without and with the skill
Checked
Without skill
With skill
Requires a column indicating when to consult each topic file
Missed
Passed
case-19 · gemini-3.6-flash · 8/13/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md143 lines2 files
Auto Memory Management
Use persistent auto memory to retain project knowledge across Claude Code sessions. The memory directory (~/.claude/projects/<path>/memory/) stores a concise index file (MEMORY.md) and detailed topic files, creating a structured knowledge base that grows with the project.
Core Architecture
~/.claude/projects/<project-path>/memory/
├── MEMORY.md # Always loaded into system prompt (~200 lines max)
├── architecture.md # Topic file: system architecture decisions
├── patterns.md # Topic file: code patterns and conventions
├── debugging.md # Topic file: debugging insights
├── workflows.md # Topic file: development workflows
└── known-issues.md # Topic file: bug tracking
Two-Tier Design
MEMORY.md (always in context): Concise index with key facts, quick reference tables, and links to topic files. Lines after 200 are truncated — keep it tight.
Topic files (consulted as needed): Detailed reference organized by domain. No size limit, but keep each file focused on one topic.
This skill should be used when a new ArcKit command has been added and documentation needs updating across the repository. Triggers: update documentation for new command, update command count, add command to README, update DEPENDENCY-MATRIX, update docs/index.html, new command documentation checklist, update all docs for new command, add command to dependency matrix, update command tables, sync documentation after adding command, I added a new command what do I update, post-command documentation