Back to Details

learn

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Learn from Mistakes

从错误中学习

You made a mistake. Good - this is an opportunity to prevent it from happening again.
你犯了一个错误。很好——这是一个防止此类错误再次发生的机会。

Process

流程

1. Analyze the Mistake

1. 分析错误

Identify:
  • What went wrong: The specific action or omission
  • Why it happened: The reasoning or assumption that led to the mistake
  • Correct behavior: What should have been done instead
确定：
  • 问题所在：具体的错误行为或遗漏事项
  • 原因：导致错误的推理过程或假设
  • 正确做法：原本应该采取的行动

2. Formulate the Lesson

2. 总结经验教训

Create a concise entry for AGENTS.md:
  • Common Mistake: Brief description of the anti-pattern (what NOT to do)
  • Correct Behavior: Clear instruction of what TO do instead
The lesson should be:
  • Actionable (tells you exactly what to do)
  • Specific (not vague platitudes)
  • Generalizable (applies beyond this one instance)
为AGENTS.md创建一个简洁的条目：
  • 常见错误：简要描述反模式（即不要做什么）
  • 正确做法：明确说明应该做什么
经验教训需满足：
  • 可执行（明确告知具体操作）
  • 具体（避免空泛的套话）
  • 可推广（适用于不止这一个场景）

3. Find the Right Section

3. 找到合适的章节

Read 
AGENTS.md
and identify which section the lesson belongs in:
  • General: Cross-cutting concerns, workflow issues, process mistakes
  • TypeScript: Language-specific patterns
  • Database: Migration and schema issues
  • Orchestration Model: Agent/skill workflow issues
  • Or create a new section if none fits
阅读
AGENTS.md
，确定经验教训所属的章节：
  • 通用：跨领域问题、工作流问题、流程错误
  • TypeScript：语言特定模式
  • 数据库：迁移和架构问题
  • 编排模型：Agent/skill工作流问题
  • 如果没有合适的章节，可创建新章节

4. Update AGENTS.md

4. 更新AGENTS.md

Add a new row to the appropriate table:
markdown
| <Common Mistake> | <Correct Behavior> |
在对应表格中添加新行：
markdown
| <常见错误> | <正确做法> |

5. Confirm the Update

5. 确认更新内容

Read back the updated section to verify the entry is clear and correctly formatted.
重新阅读更新后的章节，验证条目表述清晰、格式正确。

Example

示例

If the mistake was "Ignored reviewer feedback about missing integration test":
markdown
| Ignoring review findings marked "Should fix" or "NEEDS USER DECISION" | Address ALL review findings before proceeding. If flagged as "NEEDS USER DECISION", ask the user. Never skip items marked "Should fix (Important)" |
如果错误是“忽略了评审者关于缺失集成测试的反馈”：
markdown
| 忽略标记为“应修复”或“需要用户决策”的评审意见 | 在继续推进前处理所有评审意见。如果标记为“需要用户决策”，请询问用户。绝不跳过标记为“应修复（重要）”的事项 |

Arguments

参数

$ARGUMENTS
$ARGUMENTS