Back to Details

explore

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
You write the map as JSON; 
scripts/map.mjs
(next to this file, Node 18+) checks and renders it:
node <this skill's folder>/scripts/map.mjs check|outline|render <map.json> [--out <file.html>]
Read references/map-format.md before your first map in a session. Read maps back with 
outline
. Maps live at 
.scratch/maps/<slug>/map.json
, one folder per topic, unless the user names a place.
你以 JSON 格式编写 map；
scripts/map.mjs
（与本文件位于同一目录，要求 Node 18+）负责检查并渲染它：
node <this skill's folder>/scripts/map.mjs check|outline|render <map.json> [--out <file.html>]
首次在一次会话中创建 map 前，请阅读 references/map-format.md。 使用 
outline
读回 map。 除非用户指定存放位置，否则 map 位于 
.scratch/maps/<slug>/map.json
，每个主题使用一个文件夹。

1. Lens

1. 视角

The lens is who the map is for and what it feeds: a decision, a build, a talk, a hire. If the conversation lacks the topic or lens, ask one question for both. Note what the user already knows: never suggest it.
视角决定 map 面向谁，以及 map 服务于什么目标：决策、开发、演讲还是招聘。 如果对话中缺少主题或视角，请提出一个同时涵盖两者的问题。 记录用户已经知道的内容：绝不重复建议这些内容。

2. First map

2. 首张 map

One centre, four to six branches of three to six nodes, 20 to 35 nodes in all. Branches are angles the lens needs: vocabulary, laws, tools and measures, failure modes, adjacent fields, expert disagreements, primary sources.
  • At least a third of nodes are unknown unknowns: things the user would never have searched for.
  • Every node gets a one-sentence plain 
    summary
    .
  • Three to five highest-leverage nodes, across branches, are 
    suggested
    .
  • Suggested and non-obvious nodes add a 
    body
    (definition, then a concrete example from the user's world, with numbers) and an 
    ask
    (one question for their situation).
  • Three to eight cross-branch 
    links
    , only where one node changes how you read the other.
  • Check laws, numbers, names and attributions against a real source and list it in 
    sources
    . Generalise or cut what you cannot check.
包含一个中心节点、四到六个分支，每个分支有三到六个节点，总计二十到三十五个节点。 分支应覆盖视角所需的不同方面：术语体系、法律法规、工具与衡量指标、失效模式、相邻领域、专家分歧、一手资料。
  • 至少三分之一的节点属于 unknown unknowns（未知盲区）：用户根本不会主动搜索的内容。
  • 每个节点都要有一句简明的 
    summary
    。
  • 跨分支选出三到五个最高杠杆的节点，并将其标记为 
    suggested
    。
  • suggested
    节点和非显性节点需要提供 
    body
    （先给出定义，再结合用户所处的环境提供一个带数字的具体示例）以及 
    ask
    （针对用户实际情况提出一个问题）。
  • 添加三到八个跨分支的 
    links
    ，但仅限于一个节点会改变对另一个节点的理解方式时。
  • 对照真实来源核验法律条款、数字、名称和归属说明，并将来源列入 
    sources
    。无法核验的内容应泛化处理或删除。

3. Hand over

3. 交付

Run 
check
, fix all errors and warnings you have no reason to keep, then 
render
and open the page or give its path. Reply in three or four lines: node count, each suggested node with a phrase, and how to continue (click a label, then copy the panel prompt or say "go deeper on <node>").
运行 
check
，修复所有错误以及没有理由保留的警告，然后运行 
render
并打开页面或提供其路径。 用三到四行回复：节点数量、每个 
suggested
节点及其简短说明，以及继续探索的方式（点击标签，然后复制面板提示，或说“go deeper on <node>”）。

4. Grow

4. 扩展

  • "Go deeper on X": 
    outline
    , add three to six unknown-unknown children under X, suggest one or two, link across branches.
  • "What am I missing?": 
    outline
    , add nodes or a branch for uncovered angles, say what in one line.
  • How two nodes relate: answer in chat, add the link if it holds.
  • A node grown into its own topic, or a branch past four levels: start a new map centred on it, and say so.
After every change: 
check
, 
render
, one line on what changed. Ids are stable: keep every node the user has seen unless they ask.
  • “Go deeper on X”：运行 
    outline
    ，在 X 下添加三到六个 unknown unknowns（未知盲区）子节点，建议其中一到两个，并建立跨分支链接。
  • “What am I missing?”：运行 
    outline
    ，为尚未覆盖的角度添加节点或分支，并用一行说明补充了哪些内容。
  • 两个节点之间的关系：在聊天中回答；如果关系成立，则添加链接。
  • 某个节点已扩展为独立主题，或分支超过四层：以该节点为中心创建一张新 map，并告知用户。
每次更改后：运行 
check
、
render
，并用一行说明更改内容。 Id 保持稳定：除非用户提出要求，否则保留用户已经看到的每个节点。

Drawing a tree for another skill

为另一个 skill 绘制 tree

Take the tree or map file as given, custom 
states
included, adding nothing of your own. Run 
check
and 
render
, then return the page's path and the exact 
render
command for the caller to re-run.
按原样接收 tree 或 map 文件，包括自定义 
states
，不要添加任何自己的内容。 运行 
check
和 
render
，然后返回页面路径以及供调用方重新运行的确切 
render
命令。