产品判断:三种加载方式属于实现细节,文档里说清"要不要在常驻里留索引"就够了。 ⇒ 表格和「为什么必须分开」整段删掉,留三句: · 常驻的成本是**所有业务线常驻之后的总和**,而规则越多每条被遵守的概率越低 · 所以只有主职责常驻;次要的活写成单独一篇,常驻里只留一行索引 · 实测:问"前面那两批怎么样了",模型第一步就自己去取了做法⚠ ️ 自查:上一版我把 `_guide` / `open_playbook` 的机制差异写了满满一节 —— 那是**实现**,不是产品设计。读者要知道的是"次要业务线不常驻",⛔ 不是"它用哪种方式送到模型手上"。 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
| Name |
Last commit
|
Last update |
|---|---|---|
| .claude | Loading commit data... | |
| .design-sync | Loading commit data... | |
| apps | Loading commit data... | |
| clickhouse/config.d | Loading commit data... | |
| deploy | Loading commit data... | |
| docs | Loading commit data... | |
| packages | Loading commit data... | |
| scripts | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .gitlab-ci.yml | Loading commit data... | |
| .npmrc | Loading commit data... | |
| .prettierrc | Loading commit data... | |
| README.md | Loading commit data... | |
| docker-compose.expose.yml | Loading commit data... | |
| docker-compose.managed.yml | Loading commit data... | |
| docker-compose.prod.yml | Loading commit data... | |
| docker-compose.yml | Loading commit data... | |
| eslint.config.mjs | Loading commit data... | |
| liu.cjs | Loading commit data... | |
| package.json | Loading commit data... | |
| pnpm-lock.yaml | Loading commit data... | |
| pnpm-workspace.yaml | Loading commit data... | |
| tsconfig.base.json | Loading commit data... | |
| turbo.json | Loading commit data... |