learn
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseLearn — Capture and Route Project Knowledge
Learn — 捕获与路由项目知识
Record corrections, insights, and patterns. Route them to the correct instruction file. Apply kaizen principles to keep instructions lean and effective.
记录修正内容、洞见和模式,将其路由到正确的说明文件。应用kaizen原则保持说明简洁高效。
Dispatch
调度
| Action |
|---|---|
| Route correction to appropriate instruction file |
| Show pending learnings and their frequency |
| Promote high-frequency learnings (3+ occurrences) to instruction files |
| Check for stale, contradictory, or duplicate learnings |
| Empty | Display usage summary |
| 操作 |
|---|---|
| 将修正内容路由到对应的说明文件 |
| 显示待处理的经验教训及其出现频率 |
| 将高频(出现3次及以上)的经验升级到说明文件中 |
| 检查过时、矛盾或重复的经验 |
| 无参数 | 显示使用摘要 |
References
参考
| File | Purpose |
|---|---|
| Decision tree for where to route instruction changes |
| Error-proofing patterns, when to use hooks vs prose vs rules |
| 文件 | 用途 |
|---|---|
| 说明变更路由的决策树 |
| 防错模式,以及何时使用钩子、纯文本说明、规则的指引 |
Routing Protocol
路由协议
Route proposed updates to the correct target:
| Scope | Target |
|---|---|
| Cross-project conventions | |
| Language-specific tooling | Convention skill ( |
| Orchestration/parallelism | |
| Project-specific standards | Project's |
| File-scoped enforcement | |
| Skill behavior | The skill's own |
将拟议的更新路由到正确的目标:
| 适用范围 | 目标文件 |
|---|---|
| 跨项目公约 | |
| 特定语言工具链 | 公约skill( |
| 编排/并行处理 | |
| 项目特定标准 | 项目的 |
| 文件级强制规则 | |
| Skill行为 | 该Skill自身的 |
Routing Decision Steps
路由决策步骤
- Determine the scope: does this apply to all projects or just one?
- If cross-project, does it relate to a specific language or tool?
- If language-specific, route to the corresponding convention skill
- If general, route to
instructions/global.md - If project-only, route to the project's
AGENTS.md - If file-scoped enforcement only, create a entry
.claude/rules/
- 确定适用范围:该规则是适用于所有项目还是仅单个项目?
- 如果是跨项目的,是否与特定语言或工具相关?
- 如果是特定语言相关,路由到对应的公约skill
- 如果是通用规则,路由到
instructions/global.md - 如果仅适用于单个项目,路由到项目的
AGENTS.md - 如果仅需要文件级强制,创建条目
.claude/rules/
Kaizen Principles
Kaizen原则
- Incremental > revolutionary — Smallest viable change, verify before next
- Poka-yoke — Prefer hooks/tooling over prose instructions (error-proof by design)
- Standards work — Follow existing patterns, document what works
- JIT — Build only what is needed, optimize when measured
- 渐进式 > 颠覆式 — 最小可行变更,先验证再推进下一步
- Poka-yoke — 优先使用钩子/工具而非纯文本说明(通过设计实现防错)
- 标准落地 — 遵循现有模式,记录行之有效的方案
- JIT — 仅构建所需内容,获得量化数据后再优化
Verification Checklist
验证清单
- Verify against actual practice — confirm the pattern reflects real usage
- Check for contradictions with existing instructions
- Assess token impact — keep always-loaded content minimal
- Get user approval — never modify instruction files without consent
- Test the change — run after any instruction file edit
wagents validate
- 对照实际实践验证 — 确认模式符合真实使用情况
- 检查是否与现有说明存在矛盾
- 评估token占用影响 — 尽量减少常驻加载的内容体积
- 获得用户批准 — 未经同意不得修改任何说明文件
- 测试变更 — 编辑任何说明文件后运行命令
wagents validate
Critical Rules
核心规则
- Never modify instruction files without explicit user approval
- Require 3+ corrections across 2+ sessions before promoting
- Check for contradictions with existing instructions
- Route to narrowest applicable scope (rule before skill, skill before global)
- Keep always-loaded content under token budget
- Run after every instruction file modification
wagents validate - Prefer hooks/rules over prose (poka-yoke principle)
- 未经用户明确批准,绝对不得修改说明文件
- 升级前需要在至少2个会话中出现过3次及以上的修正
- 检查是否与现有说明存在矛盾
- 路由到适用范围最窄的目标(规则优先于skill,skill优先于全局)
- 常驻加载内容不得超出token预算
- 每次修改说明文件后必须运行命令
wagents validate - 优先使用钩子/规则而非纯文本(poka-yoke原则)
Canonical Terms
规范术语
- — any file that provides agent instructions (global.md, AGENTS.md, SKILL.md)
instruction file - — the process of choosing the correct target file for a change
routing - — a repeated fix that indicates a missing or wrong instruction
correction pattern - — the limit on always-loaded instruction content
token budget - — cross-project, language-specific, orchestration, project-specific, or file-scoped
scope
- — 任何提供Agent指令的文件(global.md、AGENTS.md、SKILL.md)
instruction file - — 为变更选择正确目标文件的过程
routing - — 反复出现的修复,说明存在缺失或错误的指令
correction pattern - — 常驻加载的指令内容的上限
token budget - — 跨项目、特定语言、编排、项目特定、文件级
scope