AGENT

1. Think Before Coding Don’t assume. Don’t hide confusion. Surface tradeoffs.

Before implementing:

State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don’t pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what’s confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative.

No features beyond what was asked. No abstractions for single-use code. No “flexibility” or “configurability” that wasn’t requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: “Would a senior engineer say this is overcomplicated?” If yes, simplify.

3. Surgical Changes Touch only what you must. Clean up only your own mess.

When editing existing code:

Don’t “improve” adjacent code, comments, or formatting. Don’t refactor things that aren’t broken. Match existing style, even if you’d do it differently. If you notice unrelated dead code, mention it - don’t delete it. When your changes create orphans:

Remove imports/variables/functions that YOUR changes made unused. Don’t remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user’s request.

4. Goal-Driven Execution Define success criteria. Loop until verified.

Transform tasks into verifiable goals:

“Add validation” → “Write tests for invalid inputs, then make them pass” “Fix the bug” → “Write a test that reproduces it, then make it pass” “Refactor X” → “Ensure tests pass before and after” For multi-step tasks, state a brief plan:

1. [Step] → verify: [check]
2. [Step] → verify: [check]
3. [Step] → verify: [check] Strong success criteria let you loop independently. Weak criteria (“make it work”) require constant clarification.

开始执行，注意以下原则

1. Think Before Coding Don’t assume. Don’t hide confusion. Surface tradeoffs.

Before implementing:

State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don’t pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what’s confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative.

No features beyond what was asked. No abstractions for single-use code. No “flexibility” or “configurability” that wasn’t requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: “Would a senior engineer say this is overcomplicated?” If yes, simplify. 3. 测试是为了发现设计缺陷进而优化 测试是为了发现问题并优化项目，不能遇到问题就简化测试，测试遇到问题应该先评估问题根因，如果是测试脚本问题修复测试脚本即可，如果是系统设计问题就应该优先修复系统设计问题，例如补充缺失代码或修正错误代码。然后按照指南进行下一步测试-发现问题-修复/优化-再测试的闭环优化流程 4. 使用sed 或者 nodejs脚本替换 批量替换使用 Windows 编辑器、PowerShell、批处理等方式会破坏文件编码；sed 可保持编码不变，但 Windows 下转义易失败；最优方案是使用 Node.js 脚本执行替换，完美支持 UTF-8 且稳定无异常。