@oxmumu3/dsh-incidental-learn 0.1.4 → 0.1.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +62 -22
- package/bin/incidental-learn-cli.mjs +2 -2
- package/client.js +56 -50
- package/lib/ledger.js +28 -11
- package/lib/prompt.js +1 -1
- package/lib/tools.js +3 -3
- package/package.json +2 -2
- package/shared/schema.js +56 -50
package/README.md
CHANGED
|
@@ -1,9 +1,9 @@
|
|
|
1
|
-
# 顺带私教 (
|
|
1
|
+
# 顺带私教 (@oxmumu3/dsh-incidental-learn)
|
|
2
2
|
|
|
3
3
|
> 作者:`牛村木木山 <157776623+oxmumu3@users.noreply.github.com>`
|
|
4
|
-
> 适用宿主:`DeepSeek Harness
|
|
4
|
+
> 适用宿主:`DeepSeek Harness 0.2.2-rc.2 || 0.2.2-rc.3`
|
|
5
5
|
|
|
6
|
-
|
|
6
|
+
平时照常跟 Agent 协作干活,顺带私教会在涉及真实工程、前端体验、AI 协作或产品策略取舍的回合末尾,附上一条默认折起的小学习卡;忙着赶进度时完全不用点任何按钮,系统会在后台静默存档;闲下来随时回到工作台,按 **前端与界面体验**、**架构与工程实践**、**AI 与 Agent 协作**、**产品与增长策略** 4 类通用技能库复习、闯关,沉淀属于自己的跨 Agent 个人技能库。
|
|
7
7
|
|
|
8
8
|
## 在 DeepSeek Harness 中安装
|
|
9
9
|
|
|
@@ -13,28 +13,66 @@
|
|
|
13
13
|
2. 复制下面这句话发给 Agent,弹出授权时点「允许」:
|
|
14
14
|
|
|
15
15
|
```text
|
|
16
|
-
请通过插件管理器,从 npm 官方源安装并启用 @oxmumu3/dsh-incidental-learn@
|
|
16
|
+
请通过插件管理器,从 npm 官方源安装并启用 @oxmumu3/dsh-incidental-learn@latest;保留已有的学习记录与技能库数据。完成后请核对版本和启用状态,再带我打开左侧「顺带私教」。
|
|
17
17
|
```
|
|
18
18
|
|
|
19
19
|
### 方式二:插件管理页直接添加
|
|
20
20
|
|
|
21
|
-
进入「插件 -> 添加插件」,填入 `@oxmumu3/dsh-incidental-learn@
|
|
21
|
+
进入「插件 -> 添加插件」,填入 `@oxmumu3/dsh-incidental-learn@latest`,安装后点击「立即启用」,再打开左侧「顺带私教」。
|
|
22
22
|
|
|
23
|
-
##
|
|
23
|
+
## 界面与日常用法一览
|
|
24
24
|
|
|
25
|
-
1.
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
2.
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
25
|
+
### 1. 刚装好就能看懂的三步上手引导(零 Token 开箱)
|
|
26
|
+
|
|
27
|
+
首次打开默认显示三步图解,不加载虚假历史数据,也不消耗模型额度;想先看完整成效时,可一键加载不耗 Token 的示例效果随时还原。
|
|
28
|
+
|
|
29
|
+

|
|
30
|
+
|
|
31
|
+
### 2. 对话末尾默认折起的「顺带补充」,绝不抢主回复风头
|
|
32
|
+
|
|
33
|
+
仅在出现值得留心的取舍时附上一条带「附 · 顺带补充(非本轮主回复)」分隔的柔和灰单行折起条;底部输入栏轻量显示 `顺带学习 · 已存 N 张`,普通闲聊或简单改字保持完全静默。
|
|
34
|
+
|
|
35
|
+

|
|
36
|
+
|
|
37
|
+
### 3. 点开就在右侧「顺带学习栏」边聊边学,主输入框草稿原样保留
|
|
38
|
+
|
|
39
|
+
有空想弄懂时,点「在右侧边聊边学」在右侧顺带学习栏完成一题点拨,左侧正在写到一半的业务草稿原封不动;点「加入重点学」可显式挂入待学清单。
|
|
40
|
+
|
|
41
|
+

|
|
42
|
+
|
|
43
|
+
### 4. 四类通用个人技能库,集中回看、三分钟闯关与四档掌握度
|
|
44
|
+
|
|
45
|
+
按 **前端与界面体验**、**架构与工程实践**、**AI 与 Agent 协作**、**产品与增长策略** 四个通用维度自动归类,优先置顶最值得学的一张,并独立记录 `1/4` 至 `4/4 能接住追问` 的过关证据。
|
|
46
|
+
|
|
47
|
+

|
|
48
|
+
|
|
49
|
+
## 为什么不会打断干活
|
|
50
|
+
|
|
51
|
+
- **默认折起、静默优先**:对话卡片以「附 · 顺带补充」单行柔和灰收起,不遮挡也不过度提示;无实质取舍的普通问答零卡片。
|
|
52
|
+
- **忙时不点也在后台自动存档**:只要当轮出现取舍,卡片默认折叠也会静默写入本机「后台自动存档」清单;待看超过 5 张时出现一键清理过期低价值卡片,误删可立即撤销。
|
|
53
|
+
- **右侧栏与草稿双保险**:点选项自测若主输入框已有未发送草稿,绝不直接覆盖,先弹出确认条;右侧学习栏与主对话完全隔离。
|
|
54
|
+
|
|
55
|
+
<details>
|
|
56
|
+
<summary>开发者与进阶说明(跨 Agent CLI / 技术架构 / 本地验证)</summary>
|
|
57
|
+
|
|
58
|
+
### 1. 五格客户端槽位 (`client.js`)
|
|
59
|
+
|
|
60
|
+
- `sidebar.panellist` + `main` (`key: 'incidental-learn'`):840px 单栏个人技能库、三步图文使用说明(0/0 空态直出、积累后可通过顶栏「使用说明」收放)、默认折叠的「效果预览」(`details` + `toolbar`) 与「后台自动存档」清单、15 分钟集中学、原生 `<dialog closedby="any">` 过关详情窗与零 Token 示例预览入口;打开旧版本账本时自动无损升级为四类通用技能维度,不丢失任何已有条目与自定义分类。
|
|
61
|
+
- `conversation.chat.markdown.fence` (`shield` / `learn-quiz` / `learn-pass`):独立于 `foldCompletedTurns`,流式阶段平稳占位,定稿后就地交互;其中 `shield` 以「附 · 顺带补充」引导线 + 默认折叠柔和灰折起条呈现,未展开也同样静默写入后台存档。选项作答内置草稿保护(非空不覆盖)与空闲直发(`useInput` + `inputActions`)。
|
|
62
|
+
- `sidebarRightTabs` + `sidebar.right.pane.tab` (`id: '@oxmumu3/dsh-incidental-learn/coach'`, `kind: 'incidental-learn-coach'`):右侧「顺带学习栏」边聊边学,独立升级掌握度至 `3/4 能复述`。
|
|
63
|
+
- `conversation.input.right`:顶部输入栏轻提醒胶囊(`顺带学习 · 已存 N 张`)。
|
|
64
|
+
- `tool.call.toolview`:`learn_save`、`learn_checkpoint`、`learn_triage` 紧凑单行执行回执。
|
|
65
|
+
|
|
66
|
+
### 2. 宿主侧能力 (`index.js` + `lib/`)
|
|
67
|
+
|
|
68
|
+
- 原子多进程共享账本 (`$DSH_HOME/incidental-learn/ledger.json`):支持 `mtimeMs` 外部变更合并、临时文件 + `renameSync` 原子落盘及 15 步撤销栈。
|
|
69
|
+
- 静态字节预算 `systemPrompt.section`(<= 1150 UTF-8 字节),仅在 `learn_board` 工具可见时注入。
|
|
70
|
+
- 4 个同源工具:`learn_board`、`learn_save`、`learn_checkpoint`、`learn_triage`。
|
|
71
|
+
- `/api/incidental_learn/view` 与 `/api/incidental_learn/action` 同源路由(带 CSRF/Origin、Content-Type 与包体上限校验)。
|
|
72
|
+
|
|
73
|
+
### 3. 跨 Agent CLI 桥 (`bin/incidental-learn-cli.mjs`)
|
|
74
|
+
|
|
75
|
+
供 Antigravity、Codex、Claude Code 或 Super Agent 验收脚本向同一份 `ledger.json` 追加候选卡片或导出笔记:
|
|
38
76
|
|
|
39
77
|
```bash
|
|
40
78
|
dsh-incidental-learn add \
|
|
@@ -49,7 +87,7 @@ dsh-incidental-learn status
|
|
|
49
87
|
dsh-incidental-learn export --out ./study-notes.md
|
|
50
88
|
```
|
|
51
89
|
|
|
52
|
-
|
|
90
|
+
### 4. 本地开发与四层门禁验证
|
|
53
91
|
|
|
54
92
|
```bash
|
|
55
93
|
npm run build # 将 shared/schema.js 与 src-client/* 编译为单文件 client.js
|
|
@@ -58,10 +96,12 @@ npm test # 原子账本并发、CLI、HTTP 安全校验、工具 Sch
|
|
|
58
96
|
npm run pack:release # 生成可重现 .tgz 与 .sha256
|
|
59
97
|
```
|
|
60
98
|
|
|
61
|
-
|
|
99
|
+
### 5. 安装本地离线包到 DeepSeek Harness Desktop
|
|
62
100
|
|
|
63
101
|
建议在退出当前运行的桌面端后通过官方 `dsh plugin` 安装离线包:
|
|
64
102
|
|
|
65
103
|
```bash
|
|
66
|
-
dsh plugin --profile desktop add ./oxmumu3-dsh-incidental-learn-0.1.
|
|
104
|
+
dsh plugin --profile desktop add ./oxmumu3-dsh-incidental-learn-0.1.6.tgz
|
|
67
105
|
```
|
|
106
|
+
|
|
107
|
+
</details>
|
|
@@ -34,7 +34,7 @@ function usage() {
|
|
|
34
34
|
' add Append a candidate card (or explicit item with --explicit)',
|
|
35
35
|
' --title <text> --why <text> [--rejected <text>] [--probe <text>]',
|
|
36
36
|
' [--source antigravity|codex|dsh-chat|superagent-review|manual]',
|
|
37
|
-
' [--track track-frontend|track-
|
|
37
|
+
' [--track track-frontend|track-engineering|track-ai|track-product] [--explicit]',
|
|
38
38
|
' status Print ledger summary [--json]',
|
|
39
39
|
' export Export study notes [--track <id>] [--out <path>]',
|
|
40
40
|
'',
|
|
@@ -64,7 +64,7 @@ async function main() {
|
|
|
64
64
|
rejected: flags.rejected ? String(flags.rejected) : '',
|
|
65
65
|
probe: flags.probe ? String(flags.probe) : '',
|
|
66
66
|
source: flags.source ? String(flags.source) : 'manual',
|
|
67
|
-
trackId: flags.track ? String(flags.track) : 'track-
|
|
67
|
+
trackId: flags.track ? String(flags.track) : 'track-engineering',
|
|
68
68
|
epistemic: flags.explicit ? 'explicit' : 'inferred',
|
|
69
69
|
}
|
|
70
70
|
const res = flags.explicit
|
package/client.js
CHANGED
|
@@ -43,22 +43,28 @@ const MASTERY_LABELS = {
|
|
|
43
43
|
const DEFAULT_TRACKS = [
|
|
44
44
|
{
|
|
45
45
|
id: 'track-frontend',
|
|
46
|
-
title: '
|
|
47
|
-
subtitle: '
|
|
46
|
+
title: '前端与界面体验',
|
|
47
|
+
subtitle: '自适应布局、原生组件、明暗主题与交互细节',
|
|
48
48
|
order: 1,
|
|
49
49
|
},
|
|
50
50
|
{
|
|
51
|
-
id: 'track-
|
|
52
|
-
title: '
|
|
53
|
-
subtitle: '
|
|
51
|
+
id: 'track-engineering',
|
|
52
|
+
title: '架构与工程实践',
|
|
53
|
+
subtitle: '接口边界、读写安全、并发控制与性能取舍',
|
|
54
54
|
order: 2,
|
|
55
55
|
},
|
|
56
56
|
{
|
|
57
|
-
id: 'track-
|
|
58
|
-
title: '
|
|
59
|
-
subtitle: '
|
|
57
|
+
id: 'track-ai',
|
|
58
|
+
title: 'AI 与 Agent 协作',
|
|
59
|
+
subtitle: '提示词结构、上下文省流、工具设计与多端配合',
|
|
60
60
|
order: 3,
|
|
61
61
|
},
|
|
62
|
+
{
|
|
63
|
+
id: 'track-product',
|
|
64
|
+
title: '产品与增长策略',
|
|
65
|
+
subtitle: '首次上手路径、信息层级、表达结构与分发转化',
|
|
66
|
+
order: 4,
|
|
67
|
+
},
|
|
62
68
|
]
|
|
63
69
|
|
|
64
70
|
const STARTER_SAMPLE_PACK = {
|
|
@@ -74,7 +80,7 @@ const STARTER_SAMPLE_PACK = {
|
|
|
74
80
|
why: '@container 本身不增加选择器权重;写在基础 repeat(2, 1fr) 规则之后,才能在 390px 分屏下真正覆写成单列。',
|
|
75
81
|
rejected: '用全局 @media(max-width:768px) 猜测面板宽度(宿主分屏时窗口虽宽,插件面板容器其实已变窄)。',
|
|
76
82
|
probe: '如果把 @container (max-width: 580px) { grid-template-columns: 1fr } 写在双列网格之前,390px 下还会变成单列吗?',
|
|
77
|
-
evidenceSummary: '
|
|
83
|
+
evidenceSummary: '在分屏窄栏场景中独立核对 @container 与基础规则先后顺序,待完成一次跨项目追问。',
|
|
78
84
|
priority: 100,
|
|
79
85
|
quiz: {
|
|
80
86
|
question: 'DSH 右侧栏只占 420px,而桌面端窗口宽度有 1440px。为什么这里不能靠 @media (max-width: 600px) 切换单列?',
|
|
@@ -115,87 +121,87 @@ const STARTER_SAMPLE_PACK = {
|
|
|
115
121
|
},
|
|
116
122
|
{
|
|
117
123
|
id: 'item-fence-vs-foldturns',
|
|
118
|
-
trackId: 'track-
|
|
119
|
-
title: '
|
|
124
|
+
trackId: 'track-ai',
|
|
125
|
+
title: '把长期要回看的学习卡放进正文自定义围栏,而不是塞进工具折叠区',
|
|
120
126
|
source: 'dsh-chat',
|
|
121
127
|
epistemic: 'verified',
|
|
122
128
|
masteryTier: 3,
|
|
123
|
-
why: '
|
|
124
|
-
rejected: '
|
|
125
|
-
probe: '
|
|
126
|
-
evidenceSummary: '
|
|
129
|
+
why: '助手在回合结束后通常会把 tool call 过程头折叠收起;放在正文自定义围栏里既不抢主正文风头,还能脱离单次调用常驻留存。',
|
|
130
|
+
rejected: '把每次回合结束的顺带学习卡做成一次 tool call(每轮多花一次工具往返,还容易随着过程记录一起折起来)。',
|
|
131
|
+
probe: '什么适合做成正文里的持久学习卡,什么更适合留作后台动作的工具回执?',
|
|
132
|
+
evidenceSummary: '对比过过程区自动折叠和正文自定义围栏的展示差异,能说清两者的边界。',
|
|
127
133
|
priority: 85,
|
|
128
134
|
},
|
|
129
135
|
{
|
|
130
136
|
id: 'item-atomic-mtime-ledger',
|
|
131
|
-
trackId: 'track-
|
|
132
|
-
title: '
|
|
137
|
+
trackId: 'track-engineering',
|
|
138
|
+
title: '多端共享 JSON 账本前先比对 mtimeMs 再原子 rename 落盘',
|
|
133
139
|
source: 'codex',
|
|
134
140
|
epistemic: 'verified',
|
|
135
141
|
masteryTier: 2,
|
|
136
|
-
why: '
|
|
137
|
-
rejected: '
|
|
138
|
-
probe: '
|
|
139
|
-
evidenceSummary: '
|
|
142
|
+
why: '桌面插件与外部命令行可能同时读写同一份 ledger.json;写入前比对文件修改时间重新合并,再通过临时文件 rename 原子替换,才能防并发覆盖。',
|
|
143
|
+
rejected: '启动时把文件整份缓存在内存里直接 writeFileSync 覆盖,或为此引入重型数据库依赖。',
|
|
144
|
+
probe: '如果外部命令行刚塞入一条新卡片,桌面端不做 mtimeMs 校验就直接写盘会发生什么?',
|
|
145
|
+
evidenceSummary: '已演练过双进程并发写盘的竞态保护,待在真实多端联动里验证一次。',
|
|
140
146
|
priority: 92,
|
|
141
147
|
},
|
|
142
148
|
{
|
|
143
149
|
id: 'item-wechat-search-firstscreen',
|
|
144
|
-
trackId: 'track-
|
|
145
|
-
title: '
|
|
150
|
+
trackId: 'track-product',
|
|
151
|
+
title: '冷启动图文卡片与熟人长文的首屏信息结构差异',
|
|
146
152
|
source: 'manual',
|
|
147
153
|
epistemic: 'explicit',
|
|
148
154
|
masteryTier: 3,
|
|
149
|
-
why: '
|
|
150
|
-
rejected: '
|
|
151
|
-
probe: '
|
|
152
|
-
evidenceSummary: '
|
|
155
|
+
why: '熟人订阅长文靠共鸣铺垫;公开信息流或搜索卡片依赖首屏前两秒用结构化利益点抓人,不能把长段落裁图硬塞。',
|
|
156
|
+
rejected: '把长文直接截成白底密字长图发进信息流(首屏看不出价值,划走率高)。',
|
|
157
|
+
probe: '面向老读者发长文和面向新用户发卡片,首屏第一眼各自最该放什么?',
|
|
158
|
+
evidenceSummary: '对比大段说明文与三步图文流程卡后,能独立把首屏核心价值收在两秒可读范围内。',
|
|
153
159
|
priority: 65,
|
|
154
160
|
},
|
|
155
161
|
],
|
|
156
162
|
triage: [
|
|
157
163
|
{
|
|
158
164
|
id: 'cand-draft-guard-lexical',
|
|
159
|
-
trackId: 'track-
|
|
160
|
-
title: '
|
|
165
|
+
trackId: 'track-frontend',
|
|
166
|
+
title: '点卡片快捷选项自动发送前,必须先检查输入框是否已有未发送草稿',
|
|
161
167
|
source: 'dsh-chat',
|
|
162
168
|
epistemic: 'inferred',
|
|
163
|
-
why: '
|
|
164
|
-
rejected: '
|
|
165
|
-
probe: '
|
|
169
|
+
why: '用户可能正在输入框写长段话,直接替用户提交会覆盖未发送的心血。',
|
|
170
|
+
rejected: '点击选择题卡片后不检查草稿状态直接覆写并提交。',
|
|
171
|
+
probe: '输入框已有草稿时,点击卡片按钮应该触发哪两步保护?',
|
|
166
172
|
lowValue: false,
|
|
167
173
|
},
|
|
168
174
|
{
|
|
169
175
|
id: 'cand-sidebar-right-id-kind',
|
|
170
|
-
trackId: 'track-
|
|
171
|
-
title: '
|
|
176
|
+
trackId: 'track-engineering',
|
|
177
|
+
title: '插件插槽注册 ID 与按 kind 打开抽屉必须一一对应',
|
|
172
178
|
source: 'superagent-review',
|
|
173
179
|
epistemic: 'verified',
|
|
174
|
-
why: '
|
|
175
|
-
rejected: '凭直觉把槽位 key
|
|
176
|
-
probe: '
|
|
180
|
+
why: '插槽定义表和侧栏激活接口往往分别按 id 和 kind 索引,混写会在打开侧栏时静音失败。',
|
|
181
|
+
rejected: '凭直觉把槽位 key 与打开参数硬传成同一字符串。',
|
|
182
|
+
probe: '当点击按钮开侧栏没报错却没反应时,最该先查哪两个注册字段?',
|
|
177
183
|
lowValue: false,
|
|
178
184
|
},
|
|
179
185
|
{
|
|
180
186
|
id: 'cand-optional-schema-no-false',
|
|
181
|
-
trackId: 'track-
|
|
182
|
-
title: '
|
|
187
|
+
trackId: 'track-ai',
|
|
188
|
+
title: '工具可选参数应省略在 required 数组外,避免写 required: false',
|
|
183
189
|
source: 'codex',
|
|
184
190
|
epistemic: 'verified',
|
|
185
|
-
why: 'JSON Schema 2020-12
|
|
186
|
-
rejected: '
|
|
187
|
-
probe: '
|
|
191
|
+
why: 'JSON Schema 2020-12 要求 required 是父对象的字符串数组,字段内写 required: false 会让模型工具注册校验失败。',
|
|
192
|
+
rejected: '按旧表单习惯在字段定义对象里写 { type: "string", required: false }。',
|
|
193
|
+
probe: '给大模型暴露一个可选字符串入参时,正确的 Schema 结构怎么写?',
|
|
188
194
|
lowValue: false,
|
|
189
195
|
},
|
|
190
196
|
{
|
|
191
197
|
id: 'cand-prompt-kv-cache',
|
|
192
|
-
trackId: 'track-
|
|
193
|
-
title: '
|
|
198
|
+
trackId: 'track-ai',
|
|
199
|
+
title: '常驻系统提示词必须保持前缀静止与严格字节预算,动态内容按需走工具读取',
|
|
194
200
|
source: 'antigravity',
|
|
195
201
|
epistemic: 'verified',
|
|
196
|
-
why: '
|
|
197
|
-
rejected: '
|
|
198
|
-
probe: '
|
|
202
|
+
why: '把不断变化的个人账本直接塞进系统提示词前缀,每轮都会击穿模型 KV Cache;保持前缀不变、查账本走工具才省钱又低延迟。',
|
|
203
|
+
rejected: '每次对话把用户所有历史盲区拼进 system prompt。',
|
|
204
|
+
probe: '为什么个人积累的卡片越多,系统提示词前缀越不能跟着变长?',
|
|
199
205
|
lowValue: false,
|
|
200
206
|
},
|
|
201
207
|
{
|
|
@@ -211,7 +217,7 @@ const STARTER_SAMPLE_PACK = {
|
|
|
211
217
|
},
|
|
212
218
|
{
|
|
213
219
|
id: 'cand-rename-readme-heading',
|
|
214
|
-
trackId: 'track-
|
|
220
|
+
trackId: 'track-product',
|
|
215
221
|
title: '文档格式微调:统一 README 二级标题序号格式',
|
|
216
222
|
source: 'manual',
|
|
217
223
|
epistemic: 'inferred',
|
|
@@ -333,7 +339,7 @@ function parseShieldFence(code) {
|
|
|
333
339
|
why: why || '已基于当前项目边界做出取舍。',
|
|
334
340
|
rejected: rejected || '已排除高维护成本或脆弱实现方案。',
|
|
335
341
|
probe: probe || `关于「${finalTitle}」,换到另一处模块时会不会遇到同样的边界?`,
|
|
336
|
-
trackId: cleanText(json.trackId, 60) || 'track-
|
|
342
|
+
trackId: cleanText(json.trackId, 60) || 'track-engineering',
|
|
337
343
|
source: normalizeSource(json.source || 'dsh-chat'),
|
|
338
344
|
epistemic: normalizeEpistemic(json.epistemic || 'inferred'),
|
|
339
345
|
quiz: sanitizeQuizBlock(json.quiz, finalTitle, why, rejected, probe),
|
|
@@ -368,7 +374,7 @@ function parseShieldFence(code) {
|
|
|
368
374
|
why: cleanText(why, 420) || '已基于当前项目边界做出取舍。',
|
|
369
375
|
rejected: cleanText(rejected, 420) || '已排除脆弱或高成本备选方案。',
|
|
370
376
|
probe: cleanText(probe, 320) || `换到另一个新模块时,如何避免重复踩中「${finalTitle}」的坑?`,
|
|
371
|
-
trackId: 'track-
|
|
377
|
+
trackId: 'track-engineering',
|
|
372
378
|
source: 'dsh-chat',
|
|
373
379
|
epistemic: 'inferred',
|
|
374
380
|
quiz: buildDefaultQuiz(finalTitle, why, rejected, probe),
|
package/lib/ledger.js
CHANGED
|
@@ -58,26 +58,43 @@ function cloneJson(value) {
|
|
|
58
58
|
return JSON.parse(JSON.stringify(value))
|
|
59
59
|
}
|
|
60
60
|
|
|
61
|
+
const LEGACY_DEFAULT_TRACK_IDS = new Set(['track-frontend', 'track-harness', 'track-growth'])
|
|
62
|
+
|
|
63
|
+
function isLegacyDefaultTracks(rawTracks) {
|
|
64
|
+
if (!Array.isArray(rawTracks) || !rawTracks.length) return false
|
|
65
|
+
const valid = rawTracks.filter(t => t && t.id && t.title)
|
|
66
|
+
if (!valid.length) return false
|
|
67
|
+
const onlyLegacyIds = valid.every(t => LEGACY_DEFAULT_TRACK_IDS.has(t.id))
|
|
68
|
+
const hasLegacyMarker = valid.some(t => t.id === 'track-harness' || String(t.title).includes('六格主线'))
|
|
69
|
+
return onlyLegacyIds && hasLegacyMarker
|
|
70
|
+
}
|
|
71
|
+
|
|
61
72
|
function normalizeTrackId(trackId, tracks) {
|
|
62
73
|
const list = Array.isArray(tracks) && tracks.length ? tracks : DEFAULT_TRACKS
|
|
63
74
|
if (trackId && list.some(t => t.id === trackId)) return trackId
|
|
64
75
|
const lowered = String(trackId || '').toLowerCase()
|
|
65
|
-
|
|
66
|
-
if (lowered
|
|
67
|
-
return
|
|
76
|
+
const has = id => list.some(t => t.id === id)
|
|
77
|
+
if ((lowered === 'track-harness' || /ai|agent|prompt|llm|fence|tool/.test(lowered)) && has('track-ai')) return 'track-ai'
|
|
78
|
+
if ((lowered === 'track-growth' || /product|growth|copy|onboarding|wechat|article/.test(lowered)) && has('track-product')) return 'track-product'
|
|
79
|
+
if (/front|css|dialog|ui|dom|layout|theme/.test(lowered) && has('track-frontend')) return 'track-frontend'
|
|
80
|
+
if (/eng|arch|backend|api|db|sql|ledger|mtime|perf/.test(lowered) && has('track-engineering')) return 'track-engineering'
|
|
81
|
+
const fallback = list.find(t => t.id === 'track-engineering') || list[0]
|
|
82
|
+
return fallback.id
|
|
68
83
|
}
|
|
69
84
|
|
|
70
85
|
function sanitizeLedger(raw) {
|
|
71
86
|
const base = emptyLedgerState()
|
|
72
87
|
if (!raw || typeof raw !== 'object') return base
|
|
73
|
-
const tracks =
|
|
74
|
-
?
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
88
|
+
const tracks = isLegacyDefaultTracks(raw.tracks)
|
|
89
|
+
? DEFAULT_TRACKS.map(t => ({ ...t }))
|
|
90
|
+
: Array.isArray(raw.tracks) && raw.tracks.length
|
|
91
|
+
? raw.tracks.filter(t => t && t.id && t.title).map((t, i) => ({
|
|
92
|
+
id: cleanText(t.id, 60),
|
|
93
|
+
title: cleanText(t.title, 90),
|
|
94
|
+
subtitle: cleanText(t.subtitle, 180),
|
|
95
|
+
order: Number.isFinite(t.order) ? t.order : i + 1,
|
|
96
|
+
}))
|
|
97
|
+
: base.tracks
|
|
81
98
|
|
|
82
99
|
const normalizeItem = (row, fallbackIdx = 0) => {
|
|
83
100
|
if (!row || typeof row !== 'object') return null
|
package/lib/prompt.js
CHANGED
|
@@ -10,7 +10,7 @@ export const LEARN_PROMPT_MAX_BYTES = 1150
|
|
|
10
10
|
export const LEARN_SYSTEM_PROMPT = [
|
|
11
11
|
'[顺带私教 | SHIELD]',
|
|
12
12
|
'1. 日常答疑/改字/常规脚本 0 额外输出;仅当本轮做出实质工程、架构或前端设计取舍时,在回答最末尾附 1 块 ```shield JSON:',
|
|
13
|
-
'{"title":"短标题","why":"为什么这么做","rejected":"被排除差方案","probe":"一句话摸底","trackId":"track-frontend|track-
|
|
13
|
+
'{"title":"短标题","why":"为什么这么做","rejected":"被排除差方案","probe":"一句话摸底","trackId":"track-frontend|track-engineering|track-ai|track-product","quiz":{"question":"题干","options":[{"key":"A","label":"选项A","correct":false,"feedback":"纠偏"},{"key":"B","label":"选项B","correct":true,"feedback":"解释"}]}}',
|
|
14
14
|
'2. 仅用户明说保存/记录盲区时才调 learn_save;不要静默写盘。',
|
|
15
15
|
'3. 若用户消息以 [顺带私教·专心闯关] 开头,走先探后讲+换景追问:第1轮先发 ```learn-quiz JSON(step:1,totalSteps:2,title,scenario,question,before,after,options,analogy)停下等答;第2轮诊断并出换项目迁移 learn-quiz;通过后调 learn_checkpoint(传人话 evidenceSummary 与 toTier:4)并输出 ```learn-pass JSON(itemId,title,fromTier,toTier,evidenceSummary,trackTitle)。',
|
|
16
16
|
].join('\n')
|
package/lib/tools.js
CHANGED
|
@@ -34,7 +34,7 @@ export function createLearnTools({ store }) {
|
|
|
34
34
|
type: 'object',
|
|
35
35
|
additionalProperties: false,
|
|
36
36
|
properties: {
|
|
37
|
-
trackId: str('可选,过滤单条路线:track-frontend | track-
|
|
37
|
+
trackId: str('可选,过滤单条路线:track-frontend | track-engineering | track-ai | track-product'),
|
|
38
38
|
},
|
|
39
39
|
},
|
|
40
40
|
output: { schema: { type: 'string' }, render: (_a, v) => textOut(v) },
|
|
@@ -78,7 +78,7 @@ export function createLearnTools({ store }) {
|
|
|
78
78
|
why: str('为什么这么做的核心原因'),
|
|
79
79
|
rejected: str('可选,被排除的差方案'),
|
|
80
80
|
probe: str('可选,一句话摸底追问'),
|
|
81
|
-
trackId: str('可选,目标路线:track-frontend | track-
|
|
81
|
+
trackId: str('可选,目标路线:track-frontend | track-engineering | track-ai | track-product'),
|
|
82
82
|
epistemic: str('可选,verified | explicit | inferred'),
|
|
83
83
|
},
|
|
84
84
|
},
|
|
@@ -89,7 +89,7 @@ export function createLearnTools({ store }) {
|
|
|
89
89
|
why: args.why,
|
|
90
90
|
rejected: args.rejected || '',
|
|
91
91
|
probe: args.probe || '',
|
|
92
|
-
trackId: args.trackId || 'track-
|
|
92
|
+
trackId: args.trackId || 'track-engineering',
|
|
93
93
|
source: 'dsh-chat',
|
|
94
94
|
epistemic: args.epistemic || 'explicit',
|
|
95
95
|
})
|
package/package.json
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@oxmumu3/dsh-incidental-learn",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.6",
|
|
4
4
|
"private": false,
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
7
7
|
"main": "index.js",
|
|
8
|
-
"description": "
|
|
8
|
+
"description": "在日常与 Agent 协作中顺手攒经验、沉淀个人技能库的 DeepSeek Harness 插件(对话末尾低调学习卡 + 后台自动存档 + 右侧边聊边学)",
|
|
9
9
|
"author": "牛村木木山 <157776623+oxmumu3@users.noreply.github.com>",
|
|
10
10
|
"repository": {
|
|
11
11
|
"type": "git",
|
package/shared/schema.js
CHANGED
|
@@ -34,22 +34,28 @@ export const MASTERY_LABELS = {
|
|
|
34
34
|
export const DEFAULT_TRACKS = [
|
|
35
35
|
{
|
|
36
36
|
id: 'track-frontend',
|
|
37
|
-
title: '
|
|
38
|
-
subtitle: '
|
|
37
|
+
title: '前端与界面体验',
|
|
38
|
+
subtitle: '自适应布局、原生组件、明暗主题与交互细节',
|
|
39
39
|
order: 1,
|
|
40
40
|
},
|
|
41
41
|
{
|
|
42
|
-
id: 'track-
|
|
43
|
-
title: '
|
|
44
|
-
subtitle: '
|
|
42
|
+
id: 'track-engineering',
|
|
43
|
+
title: '架构与工程实践',
|
|
44
|
+
subtitle: '接口边界、读写安全、并发控制与性能取舍',
|
|
45
45
|
order: 2,
|
|
46
46
|
},
|
|
47
47
|
{
|
|
48
|
-
id: 'track-
|
|
49
|
-
title: '
|
|
50
|
-
subtitle: '
|
|
48
|
+
id: 'track-ai',
|
|
49
|
+
title: 'AI 与 Agent 协作',
|
|
50
|
+
subtitle: '提示词结构、上下文省流、工具设计与多端配合',
|
|
51
51
|
order: 3,
|
|
52
52
|
},
|
|
53
|
+
{
|
|
54
|
+
id: 'track-product',
|
|
55
|
+
title: '产品与增长策略',
|
|
56
|
+
subtitle: '首次上手路径、信息层级、表达结构与分发转化',
|
|
57
|
+
order: 4,
|
|
58
|
+
},
|
|
53
59
|
]
|
|
54
60
|
|
|
55
61
|
export const STARTER_SAMPLE_PACK = {
|
|
@@ -65,7 +71,7 @@ export const STARTER_SAMPLE_PACK = {
|
|
|
65
71
|
why: '@container 本身不增加选择器权重;写在基础 repeat(2, 1fr) 规则之后,才能在 390px 分屏下真正覆写成单列。',
|
|
66
72
|
rejected: '用全局 @media(max-width:768px) 猜测面板宽度(宿主分屏时窗口虽宽,插件面板容器其实已变窄)。',
|
|
67
73
|
probe: '如果把 @container (max-width: 580px) { grid-template-columns: 1fr } 写在双列网格之前,390px 下还会变成单列吗?',
|
|
68
|
-
evidenceSummary: '
|
|
74
|
+
evidenceSummary: '在分屏窄栏场景中独立核对 @container 与基础规则先后顺序,待完成一次跨项目追问。',
|
|
69
75
|
priority: 100,
|
|
70
76
|
quiz: {
|
|
71
77
|
question: 'DSH 右侧栏只占 420px,而桌面端窗口宽度有 1440px。为什么这里不能靠 @media (max-width: 600px) 切换单列?',
|
|
@@ -106,87 +112,87 @@ export const STARTER_SAMPLE_PACK = {
|
|
|
106
112
|
},
|
|
107
113
|
{
|
|
108
114
|
id: 'item-fence-vs-foldturns',
|
|
109
|
-
trackId: 'track-
|
|
110
|
-
title: '
|
|
115
|
+
trackId: 'track-ai',
|
|
116
|
+
title: '把长期要回看的学习卡放进正文自定义围栏,而不是塞进工具折叠区',
|
|
111
117
|
source: 'dsh-chat',
|
|
112
118
|
epistemic: 'verified',
|
|
113
119
|
masteryTier: 3,
|
|
114
|
-
why: '
|
|
115
|
-
rejected: '
|
|
116
|
-
probe: '
|
|
117
|
-
evidenceSummary: '
|
|
120
|
+
why: '助手在回合结束后通常会把 tool call 过程头折叠收起;放在正文自定义围栏里既不抢主正文风头,还能脱离单次调用常驻留存。',
|
|
121
|
+
rejected: '把每次回合结束的顺带学习卡做成一次 tool call(每轮多花一次工具往返,还容易随着过程记录一起折起来)。',
|
|
122
|
+
probe: '什么适合做成正文里的持久学习卡,什么更适合留作后台动作的工具回执?',
|
|
123
|
+
evidenceSummary: '对比过过程区自动折叠和正文自定义围栏的展示差异,能说清两者的边界。',
|
|
118
124
|
priority: 85,
|
|
119
125
|
},
|
|
120
126
|
{
|
|
121
127
|
id: 'item-atomic-mtime-ledger',
|
|
122
|
-
trackId: 'track-
|
|
123
|
-
title: '
|
|
128
|
+
trackId: 'track-engineering',
|
|
129
|
+
title: '多端共享 JSON 账本前先比对 mtimeMs 再原子 rename 落盘',
|
|
124
130
|
source: 'codex',
|
|
125
131
|
epistemic: 'verified',
|
|
126
132
|
masteryTier: 2,
|
|
127
|
-
why: '
|
|
128
|
-
rejected: '
|
|
129
|
-
probe: '
|
|
130
|
-
evidenceSummary: '
|
|
133
|
+
why: '桌面插件与外部命令行可能同时读写同一份 ledger.json;写入前比对文件修改时间重新合并,再通过临时文件 rename 原子替换,才能防并发覆盖。',
|
|
134
|
+
rejected: '启动时把文件整份缓存在内存里直接 writeFileSync 覆盖,或为此引入重型数据库依赖。',
|
|
135
|
+
probe: '如果外部命令行刚塞入一条新卡片,桌面端不做 mtimeMs 校验就直接写盘会发生什么?',
|
|
136
|
+
evidenceSummary: '已演练过双进程并发写盘的竞态保护,待在真实多端联动里验证一次。',
|
|
131
137
|
priority: 92,
|
|
132
138
|
},
|
|
133
139
|
{
|
|
134
140
|
id: 'item-wechat-search-firstscreen',
|
|
135
|
-
trackId: 'track-
|
|
136
|
-
title: '
|
|
141
|
+
trackId: 'track-product',
|
|
142
|
+
title: '冷启动图文卡片与熟人长文的首屏信息结构差异',
|
|
137
143
|
source: 'manual',
|
|
138
144
|
epistemic: 'explicit',
|
|
139
145
|
masteryTier: 3,
|
|
140
|
-
why: '
|
|
141
|
-
rejected: '
|
|
142
|
-
probe: '
|
|
143
|
-
evidenceSummary: '
|
|
146
|
+
why: '熟人订阅长文靠共鸣铺垫;公开信息流或搜索卡片依赖首屏前两秒用结构化利益点抓人,不能把长段落裁图硬塞。',
|
|
147
|
+
rejected: '把长文直接截成白底密字长图发进信息流(首屏看不出价值,划走率高)。',
|
|
148
|
+
probe: '面向老读者发长文和面向新用户发卡片,首屏第一眼各自最该放什么?',
|
|
149
|
+
evidenceSummary: '对比大段说明文与三步图文流程卡后,能独立把首屏核心价值收在两秒可读范围内。',
|
|
144
150
|
priority: 65,
|
|
145
151
|
},
|
|
146
152
|
],
|
|
147
153
|
triage: [
|
|
148
154
|
{
|
|
149
155
|
id: 'cand-draft-guard-lexical',
|
|
150
|
-
trackId: 'track-
|
|
151
|
-
title: '
|
|
156
|
+
trackId: 'track-frontend',
|
|
157
|
+
title: '点卡片快捷选项自动发送前,必须先检查输入框是否已有未发送草稿',
|
|
152
158
|
source: 'dsh-chat',
|
|
153
159
|
epistemic: 'inferred',
|
|
154
|
-
why: '
|
|
155
|
-
rejected: '
|
|
156
|
-
probe: '
|
|
160
|
+
why: '用户可能正在输入框写长段话,直接替用户提交会覆盖未发送的心血。',
|
|
161
|
+
rejected: '点击选择题卡片后不检查草稿状态直接覆写并提交。',
|
|
162
|
+
probe: '输入框已有草稿时,点击卡片按钮应该触发哪两步保护?',
|
|
157
163
|
lowValue: false,
|
|
158
164
|
},
|
|
159
165
|
{
|
|
160
166
|
id: 'cand-sidebar-right-id-kind',
|
|
161
|
-
trackId: 'track-
|
|
162
|
-
title: '
|
|
167
|
+
trackId: 'track-engineering',
|
|
168
|
+
title: '插件插槽注册 ID 与按 kind 打开抽屉必须一一对应',
|
|
163
169
|
source: 'superagent-review',
|
|
164
170
|
epistemic: 'verified',
|
|
165
|
-
why: '
|
|
166
|
-
rejected: '凭直觉把槽位 key
|
|
167
|
-
probe: '
|
|
171
|
+
why: '插槽定义表和侧栏激活接口往往分别按 id 和 kind 索引,混写会在打开侧栏时静音失败。',
|
|
172
|
+
rejected: '凭直觉把槽位 key 与打开参数硬传成同一字符串。',
|
|
173
|
+
probe: '当点击按钮开侧栏没报错却没反应时,最该先查哪两个注册字段?',
|
|
168
174
|
lowValue: false,
|
|
169
175
|
},
|
|
170
176
|
{
|
|
171
177
|
id: 'cand-optional-schema-no-false',
|
|
172
|
-
trackId: 'track-
|
|
173
|
-
title: '
|
|
178
|
+
trackId: 'track-ai',
|
|
179
|
+
title: '工具可选参数应省略在 required 数组外,避免写 required: false',
|
|
174
180
|
source: 'codex',
|
|
175
181
|
epistemic: 'verified',
|
|
176
|
-
why: 'JSON Schema 2020-12
|
|
177
|
-
rejected: '
|
|
178
|
-
probe: '
|
|
182
|
+
why: 'JSON Schema 2020-12 要求 required 是父对象的字符串数组,字段内写 required: false 会让模型工具注册校验失败。',
|
|
183
|
+
rejected: '按旧表单习惯在字段定义对象里写 { type: "string", required: false }。',
|
|
184
|
+
probe: '给大模型暴露一个可选字符串入参时,正确的 Schema 结构怎么写?',
|
|
179
185
|
lowValue: false,
|
|
180
186
|
},
|
|
181
187
|
{
|
|
182
188
|
id: 'cand-prompt-kv-cache',
|
|
183
|
-
trackId: 'track-
|
|
184
|
-
title: '
|
|
189
|
+
trackId: 'track-ai',
|
|
190
|
+
title: '常驻系统提示词必须保持前缀静止与严格字节预算,动态内容按需走工具读取',
|
|
185
191
|
source: 'antigravity',
|
|
186
192
|
epistemic: 'verified',
|
|
187
|
-
why: '
|
|
188
|
-
rejected: '
|
|
189
|
-
probe: '
|
|
193
|
+
why: '把不断变化的个人账本直接塞进系统提示词前缀,每轮都会击穿模型 KV Cache;保持前缀不变、查账本走工具才省钱又低延迟。',
|
|
194
|
+
rejected: '每次对话把用户所有历史盲区拼进 system prompt。',
|
|
195
|
+
probe: '为什么个人积累的卡片越多,系统提示词前缀越不能跟着变长?',
|
|
190
196
|
lowValue: false,
|
|
191
197
|
},
|
|
192
198
|
{
|
|
@@ -202,7 +208,7 @@ export const STARTER_SAMPLE_PACK = {
|
|
|
202
208
|
},
|
|
203
209
|
{
|
|
204
210
|
id: 'cand-rename-readme-heading',
|
|
205
|
-
trackId: 'track-
|
|
211
|
+
trackId: 'track-product',
|
|
206
212
|
title: '文档格式微调:统一 README 二级标题序号格式',
|
|
207
213
|
source: 'manual',
|
|
208
214
|
epistemic: 'inferred',
|
|
@@ -324,7 +330,7 @@ export function parseShieldFence(code) {
|
|
|
324
330
|
why: why || '已基于当前项目边界做出取舍。',
|
|
325
331
|
rejected: rejected || '已排除高维护成本或脆弱实现方案。',
|
|
326
332
|
probe: probe || `关于「${finalTitle}」,换到另一处模块时会不会遇到同样的边界?`,
|
|
327
|
-
trackId: cleanText(json.trackId, 60) || 'track-
|
|
333
|
+
trackId: cleanText(json.trackId, 60) || 'track-engineering',
|
|
328
334
|
source: normalizeSource(json.source || 'dsh-chat'),
|
|
329
335
|
epistemic: normalizeEpistemic(json.epistemic || 'inferred'),
|
|
330
336
|
quiz: sanitizeQuizBlock(json.quiz, finalTitle, why, rejected, probe),
|
|
@@ -359,7 +365,7 @@ export function parseShieldFence(code) {
|
|
|
359
365
|
why: cleanText(why, 420) || '已基于当前项目边界做出取舍。',
|
|
360
366
|
rejected: cleanText(rejected, 420) || '已排除脆弱或高成本备选方案。',
|
|
361
367
|
probe: cleanText(probe, 320) || `换到另一个新模块时,如何避免重复踩中「${finalTitle}」的坑?`,
|
|
362
|
-
trackId: 'track-
|
|
368
|
+
trackId: 'track-engineering',
|
|
363
369
|
source: 'dsh-chat',
|
|
364
370
|
epistemic: 'inferred',
|
|
365
371
|
quiz: buildDefaultQuiz(finalTitle, why, rejected, probe),
|