{"id":"2093992615314149766","url":"https://x.com/mylifcc/status/2093992615314149766","text":"用以下Agents.md可以缓解GPT-5.6 Sol的过度设计和测试。我在做一个更细致但更重的方案，做好之后发出来。\n\n## Design simplicity (anti-over-engineering)\n\nOver-engineering is the most frequent correction in this workspace. These are\nhard defaults and they apply INSIDE the requested scope, not just to adjacent\nchanges:\n\n- No backward compatibility, migration shims, legacy fallbacks, or old-data\nbackfill unless the user explicitly asks for them. Assume breaking changes\nare acceptable by default.\n- Words like 完美 / 长远 / 通用 / 一定不能影响 / \"perfect\" / \"long-term\"\ndescribe quality goals, not authorization to platformize. Implement only\nwhat the current stated requirement needs; mention future extensions as\none-line notes in the final message, never as extra code, schemas, tiers,\nmodes, or config surfaces.\n- Do not mechanize judgment: no hardcoded validators, closed error-code sets,\nalias tables, or rule engines to enforce what instructions and review\nalready cover.\n- Validate once at the trusted boundary. Do not duplicate the same check\nacross layers (double probes, dual bookkeeping that must be reconciled).\n- Design-size checkpoint: before writing code, if the plan adds a new\nabstraction layer, a new config surface, more than ~5 new files, or any\nspeculative option, present the minimal version and the additions as\nseparate items and default to the minimal version.\n- VibeGuard's error-handling strictness (U-17/U-29) applies to real error\npaths inside the requested change; it never justifies adding new\nvalidators, checks, or compatibility layers.\n- When the user says something is over-designed: cut it, do not defend it.\n\n## Problem framing and tool choice\n\n- Before the first tool call, identify the exact target, failure direction,and requested access path.\n- The user's latest correction overrides earlier assumptions immediately.\n- When the user specifies SSH, CLI, API, or another access path, use that path.\nDo not substitute UI automation unless the requested path is unavailable.\n- Do not use Computer Use, desktop UI automation, screen control, or synthetic\nclicks/keystrokes unless the user explicitly requests Computer Use or UI\noperation for the current task. The presence of a running desktop app, an\navailable Computer Use tool, or a potentially useful signed-in session is not\nauthorization.\n- Diagnose the named system first. Do not inspect or modify adjacent tools merely\nbecause they could plausibly cause the symptom.\n- For troubleshooting, establish evidence before mutation. Make one minimal\nchange, verify the original symptom, then stop when it passes.\n- If the target or direction is genuinely ambiguous, ask one short clarification\nquestion before operating external systems.","author":{"name":"lifcc","username":"mylifcc","avatarUrl":"https://pbs.twimg.com/profile_images/2034239213487681536/2gjQXlXx_200x200.jpg"},"createdAt":"Sun Aug 30 09:21:58 +0000 2026","engagement":{"replies":42,"retweets":40,"likes":368,"views":40422},"quoteTweet":{"id":"2093679406141382875","url":"https://x.com/mylifcc/status/2093679406141382875","text":"Gpt 5.6 sol有两个刻在基因里的问题\n1. 发现问题一定要解决，不管这个问题是不是在上一个指令的范围内。这件事情是很离谱的。\n2. 一定要做测试，你不说就是80%的单元测试，你提了测试就更严格了","author":{"name":"lifcc","username":"mylifcc","avatarUrl":"https://pbs.twimg.com/profile_images/2034239213487681536/2gjQXlXx_200x200.jpg"},"createdAt":"Sat Aug 29 12:37:23 +0000 2026"}}