Back to Details

tour

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/memory-kit:tour — Interactive walkthrough

/memory-kit:tour — 交互式导览

You are giving the user a guided tour of their Memory Kit. Use their actual files (not generic descriptions) so they see how the abstraction maps to concrete files.
你将为用户提供其Memory Kit的引导式导览。请使用用户的实际文件（而非通用描述），以便用户了解抽象概念如何对应到具体文件。

Tour structure (10-15 minutes)

导览结构（10-15分钟）

Stop 1 — the working agreement (injected, not a file in this repo)

第一站 — 工作协议（注入式，不在此仓库的文件中）

Run 
/context
or point at the session's opening block. Say: "The rules I work by ship with the plugin and are injected at every session start — there's nothing for you to maintain. Your own project rules, if you ever want any, live in 
.claude/rules/
."
运行
/context
或指向会话的开场模块。说明："我遵循的规则随插件一同提供，并在每次会话开始时注入——无需你进行维护。如果你需要自定义项目规则，可存放在
.claude/rules/
目录下。"

Stop 2 — Session entry (handoff + backlog)

第二站 — 会话入口（交接记录 + 待办事项）

Open the newest 
context/handoffs/*.md
(or the template if none yet) and, if multi-project mode, 
projects/<active>/BACKLOG.md
. Say: "This is the note the previous session left for me — the handoff. The start-hook injects the newest one automatically, so I open every session already knowing where we left off."
打开最新的
context/handoffs/*.md
文件（如果没有则使用模板），若为多项目模式，同时打开
projects/<active>/BACKLOG.md
。说明："这是上一次会话留给我的交接记录。启动钩子会自动注入最新的交接记录，因此我在每次会话开始时都能了解之前的工作进度。"

Stop 3 — Hot path (MEMORY.md)

第三站 — 热路径（MEMORY.md）

Open 
.claude/memory/MEMORY.md
. Say: "This is my hot cache. Date-tagged one-liners of patterns from recent sessions; the header on top is the current state of work, replaced at every close. A hook watches three size caps so this file physically can't silently bloat."
打开
.claude/memory/MEMORY.md
文件。说明："这是我的热缓存文件。其中包含带有日期标记的近期会话模式摘要；顶部的标题是当前工作状态，每次会话结束时会更新。有一个钩子会监控三个大小上限，确保该文件不会无限制膨胀。"

Stop 4 — Rules (.claude/rules/)

第四站 — 规则（.claude/rules/）

List any 
.claude/rules/*.md
files. If folder is empty (only 
_example.md.disabled
), say: "This is where hard project rules live. 'Don't use X', 'always check Y'. They auto-load by keyword. Empty for now — they'll appear when you start dictating rules and I propose them on 
/memory-kit:close-session
."
列出所有
.claude/rules/*.md
文件。如果文件夹为空（仅存在
_example.md.disabled
），说明："这里用于存放严格的项目规则，比如'禁止使用X'、'必须检查Y'。它们会按关键词自动加载。目前文件夹为空——当你开始制定规则时，我会在执行
/memory-kit:close-session
时提议添加相关规则文件。"

Stop 5 — Knowledge concepts

第五站 — 知识概念

List 
knowledge/concepts/*.md
. Say: "Deep memory with facts. 'What's our typography scale', 'what we know about SEO for AI'. Reference articles. Empty now — I write them during 
/memory-kit:close-session
when a pattern has repeated on three-plus dates and you say yes."
列出
knowledge/concepts/*.md
文件。说明："这是存储事实的深度记忆库，比如'我们的排版规范是什么'、'我们了解的AI SEO相关知识'，包含参考文档。目前为空——当某个模式在三个及以上不同日期重复出现且你确认后，我会在执行
/memory-kit:close-session
时写入相关内容。"

Stop 6 — Handoff history

第六站 — 交接历史

Show 
context/handoffs/
. Say: "One note per closed session — my session diary. You never open them; just ask 'what did we do last Tuesday?' and I read them back."
展示
context/handoffs/
目录。说明："每个已结束的会话对应一条记录——这是我的会话日志。你无需手动打开它们，只需询问'我们上周二做了什么？'，我就会为你读取相关内容。"

Stop 7 — Projects

第七站 — 项目

List 
projects/*/
and open one 
README.md
. Say: "Each client or product gets a folder, and its README is the map — where this project's tasks, specs, research, decisions and QA live. Memory is shared across all of them; paperwork is per project. Say 'we're working on <name>' and I switch to that one."
列出
projects/*/
目录并打开其中一个
README.md
文件。说明："每个客户或产品都有一个独立文件夹，其README文件是项目的总览——包含该项目的任务、规格、研究、决策和QA内容。记忆在所有项目间共享，而文档则按项目单独存储。只需说'我们正在处理<项目名称>'，我就会切换到对应项目。"

Stop 8 — Hooks

第八站 — 钩子

Don't deep-dive — the hooks ship inside the plugin, there is nothing in this repo to maintain. Say: "Four hooks run silently: one injects your memory and the working rules at every session start, one blocks compaction until state is saved, one asks before an existing test gets edited, one logs the close."
无需深入讲解——钩子内置在插件中，此仓库中无需维护相关内容。说明："有四个钩子在后台静默运行：一个在每次会话开始时注入你的记忆和工作规则，一个在状态保存前阻止压缩操作，一个在编辑现有测试前进行确认，一个记录会话结束信息。"

Stop 9 — Operators

第九站 — 操作指令

List what this plugin adds: 
/memory-kit:close-session
, 
/memory-kit:tour
, 
/memory-kit:setup
, 
/memory-kit:memory-audit
, 
/memory-kit:system-audit
. Say: "
/memory-kit:close-session
is the one that matters — the end-of-session ritual where I audit what happened, propose what's worth remembering forever, and leave the handoff note for next time. 
memory-audit
is the surgery when the cache outgrows its caps; 
system-audit
is the periodic look at whether this whole system still earns its place. There are three more for when you build with subagents — 
session-review
, 
second-opinion
, 
qa-sweep
— and you don't need them to start."
列出此插件新增的指令：
/memory-kit:close-session
、
/memory-kit:tour
、
/memory-kit:setup
、
/memory-kit:memory-audit
、
/memory-kit:system-audit
。说明："
/memory-kit:close-session
是最重要的指令——这是会话结束时的例行流程，我会复盘会话内容，提议值得永久保存的信息，并为下一次会话留下交接记录。
memory-audit
用于在缓存超出上限时进行清理；
system-audit
用于定期检查整个系统是否仍有存在的价值。还有三个用于子Agent构建的指令——
session-review
、
second-opinion
、
qa-sweep
——你刚开始使用时无需用到它们。"

Closing

收尾

Ask: "Anything you want to drill into deeper? Or should we start with a real task — name your first project?"
询问："你有没有想深入了解的内容？或者我们可以直接开始处理实际任务——说出你的第一个项目名称？"

What you do NOT do

禁止事项

  • Don't read every file in full. Show the first 5-10 lines so user sees the format, not the content.
  • Don't lecture. This is a tour, not a manual. Each stop = 1-2 sentences.
  • Don't propose changes during the tour. This is informational only. If user asks "can we change X" during tour — note it for after.
  • Don't skip stops based on emptiness. Empty folders are part of the story — show them and explain when they fill.
  • 不要完整读取每个文件的内容。 只需展示前5-10行，让用户了解格式即可，无需展示具体内容。
  • 不要长篇大论。 这是导览，不是手册。每个站点只需1-2句话说明。
  • 导览期间不要提议修改。 此环节仅用于信息展示。如果用户在导览期间询问"我们能否修改X"，请记录下来留到之后处理。
  • 不要因文件夹为空而跳过站点。 空文件夹也是流程的一部分——展示它们并解释何时会被填充。

Length

时长

Target 10-15 minutes total. If user is engaged and asks questions, fine — go longer. If user seems impatient, compress to 5 minutes by collapsing stops 4-7 into one "and these are the on-trigger layers" sweep.
目标总时长为10-15分钟。如果用户参与度高并提问，可以适当延长。如果用户看起来不耐烦，可以将第4至第7站合并为一个"这些是触发式层级"的概览，将时长压缩至5分钟。