memory-management

仓库创建 2026年6月30日最近提交 21 天前SkillHot 收录 21 天前
▸ 精选理由

帮助团队与智能体保持长期项目连续性与上下文一致性。

这个 Skill 做什么

管理不同层级的信息记忆并指导如何在会话恢复时重建上下文。

帮你决定信息该放在哪层记忆:项目记忆(CLAUDE.md)、文档型记忆(spec、ADR)还是用户记忆,并给出在会话恢复时如何重建上下文的步骤。适合记录决策、约定或在重新接手项目时恢复背景知识。特别在于分层管理持久信息与会话临时信息,并提供可执行的“会话重建”流程,避免信息丢失或上下文断裂。

▸ 展开 SKILL.md 英文原文

Use when deciding where information lives across sessions — project memory (CLAUDE.md) vs docs-as-memory (specs, ADRs, assumptions) vs user memory — and rehydrating context on resume.

Skill 开发管理会话记忆项目记忆上下文恢复决策记录通用
0
Stars
0
Forks
40
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/muxammadmamajonov/dot-claude/main/.claude/skills/memory-management/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/muxammadmamajonov/dot-claude/main/.claude/skills/memory-management/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
# Memory Management: What Lives Where, and How to Rehydrate

## When to use
- You learned something durable (a decision, an assumption, a constraint, a risk) and must decide where to record it.
- You are starting a session on an existing project and need to reconstruct prior context.
- `/continue-work` is invoked, or the user asks "where were we / what did we decide".
- Project memory (`CLAUDE.md`) is getting bloated, contradictory, or used as a scratchpad.
- You need to separate project-specific facts from user-wide preferences.

This applies to every project type. The three tiers below are universal; only the contents differ. See `.claude/docs/MEMORY_STRATEGY.md` for the full model.

## Wo
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有