[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-why-frontend-teams-should-stop-treating-ai-as-a-rewrite-mach-zh":3,"tags-why-frontend-teams-should-stop-treating-ai-as-a-rewrite-mach-zh":24,"related-lang-why-frontend-teams-should-stop-treating-ai-as-a-rewrite-mach-zh":25,"related-posts-why-frontend-teams-should-stop-treating-ai-as-a-rewrite-mach-zh":29,"series-industry-ab4dc6a3-8d25-4bfe-8963-16b42e057d2b":66},{"id":4,"title":5,"content":6,"summary":7,"source":8,"source_url":9,"author":10,"image_url":11,"keywords":10,"language":12,"translated_content":10,"views":13,"is_premium":14,"created_at":15,"updated_at":15,"cover_image":11,"published_at":16,"rewrite_status":17,"rewrite_error":10,"rewritten_from_id":18,"slug":19,"category":20,"related_article_id":21,"status":22,"google_indexed_at":23,"x_posted_at":10,"tweet_text":10,"title_rewritten_at":10,"title_original":10,"key_takeaways":10,"topic_cluster_id":10,"embedding":10,"is_canonical_seed":14},"ab4dc6a3-8d25-4bfe-8963-16b42e057d2b","為什麼前端團隊應該停止把 AI 當成重寫機器","\u003Cp>前端團隊應該停止把 AI 當成重寫機器，改把它當成受限編輯器。\u003C\u002Fp>\u003Cp>理由很直接：現在最有價值的 AI 能力，不是把穩定程式碼整段翻新，而是把必要的改動縮到最小。Habr 的一則技術摘要提到，研究者在 \u003Ca href=\"\u002Fnews\u002Fgoogle-plans-40b-bet-on-anthropic-zh\">400\u003C\u002Fa> 個 Big\u003Ca href=\"\u002Fnews\u002Fanthropic-claude-code-pro-pricing-test-zh\">Code\u003C\u002Fa>Bench 任務上觀察到 code assistant 的「過度編輯」現象，並發現只要在提示中加入「保留原始程式碼」這類約束，多數模型就會明顯減少不必要的變動。這不是小細節，而是前端工程的核心問題。前端最怕的從來不是改不動，而是改太多，把原本只需要一行修補的地方，變成一個新的 bug 來源。\u003C\u002Fp>\u003Ch2>第一個論點：重寫會破壞前端最依賴的東西，也就是局部可預測性\u003C\u002Fh2>\u003Cp>前端程式碼看起來常常很短，但短不代表簡單。一個只有 40 行的 component，可能同時包含版面行為、無障礙屬性、事件順序，以及框架特定的假設。當 AI 助手把一個精準 patch 擴寫成更大的 refactor，它改變的不只是語法，而是團隊對這段 UI 的心智模型。Habr 摘要裡另一個關於 JavaScript chain call 的觀察也指向同一件事：chain 一旦拉長，閱讀與除錯成本就會上升。AI 式重寫也是如此，它把變動擴散到更多行、更多分支、更多命名，最後讓 review 比原始 bug 更難。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1777334803961-exe5.png\" alt=\"為什麼前端團隊應該停止把 AI 當成重寫機器\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>那篇被摘要引用的研究之所以重要，是因為它不是憑感覺說「AI 太愛亂改」。研究量化了 token-level Levenshtein distance 與 cognitive complexity，樣本是 400 個任務。這種量化對前端團隊特別有意義，因為我們每天都在處理 diff 品質。修一個 button state、調一條 valida\u003Ca href=\"\u002Fnews\u002Fwhy-evolution-strategies-are-the-right-way-to-fine-tune-llms-zh\">tion\u003C\u002Fa> rule、改一個 hook dependency，本來都應該是小範圍變更；如果 AI 回傳的是 helper 重命名、guard 重排、再加三個 null check，那就不是幫忙，而是在製造 review 成本。更好的做法不是叫模型「想辦法重構」，而是要求它守住原本結構，只做必要修補。\u003C\u002Fp>\u003Ch2>第二個論點：真正有效的 AI 用法本來就該是受限任務，而且表現更好\u003C\u002Fh2>\u003Cp>看同一則摘要裡其他案例，就能看出方向。wasm-xlsxwriter 的價值，不在於它「很聰明」，而在於它把一件明確的工作移到瀏覽器與 Node.js 端，邊界清楚：產生 .xlsx 檔，僅此而已。Cloudflare 的 Agent Readiness Score 也是同樣思路，它檢查的是可發現性、content negotiation、access control 與 capabilities，並對照 robots.txt、Markdown fallback、API catalog support 等具體標準。它不是叫系統「把網站變好」，而是驗證特定屬性。前端 AI 也應該長這樣：輸入要窄，輸出要窄，成功標準要可測。\u003C\u002Fp>\u003Cp>效能面也支持這個結論。摘要提到 Cloudflare 文件在調整到新標準後，使用 Kimi-k2.5 搭配 OpenCode 的 agent 回答技術問題，速度快了 66%，token 用量少了 31%。這種提升來自結構，不來自自由發揮。當輸入空間被整理好，agent 就更便宜、更準確；當輸入空間混亂，它就會自信滿滿地產出一大段冗長改寫。前端團隊應該學的是這種結構化思維：把任務限制住，定義輸出格式，衡量結果。AI 很適合用在 code review 輔助、test generation、文件遷移、機械式小修補；不適合用在「幫我把這段改好」這種會默默引發設計漂移的寬鬆指令。\u003C\u002Fp>\u003Ch2>反方可能怎麼說\u003C\u002Fh2>\u003Cp>支持 AI 當重寫機器的人，最強的論點是速度。資深工程師看到一個 component，常常能直接判斷哪裡該拆、哪裡該抽、哪裡該簡化；AI 也能模仿這種模式，替重複性工作省下時間。對大型前端 codebase 來說，確實有不少地方本來就脆弱、重複、耦合過高。如果工具真的能把模組重寫成更乾淨的形狀，團隊看起來像是同時拿到更好的 code 和更快的 delivery。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1777334802732-v00z.png\" alt=\"為什麼前端團隊應該停止把 AI 當成重寫機器\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>這個說法不是假的。它在 code 已經隔離、測試很強、而且團隊本來就準備 refactor 的情境下，最有說服力。問題是日常產品開發大多不是這樣。日常任務的目標不是優雅，而是安全變更。前面提到的研究已經把方向講得很清楚：廣泛編輯會增加 cognitive load，而明確要求保留原始程式碼，則能減少 churn。界線應該畫在這裡：可以讓 AI 提出 refactor 建議，但不要讓它在沒有約束的情況下直接執行。只有當這本來就是一張 refactor ticket，且測試、review 時間都已經安排好，才值得接受較大的重寫。一般前端修補，助手就該待在 edit mode，不該進入 transformation mode。\u003C\u002Fp>\u003Ch2>你能做什麼\u003C\u002Fh2>\u003Cp>如果你是工程師，立刻改 prompt 和 review 習慣：要求模型保留結構、非必要不要改名、只碰最小範圍。如果你是 PM，不要用輸出看起來多戲劇化來衡量 AI 成功，而要看 escaped defects、review time、rollback rate。如果你是創辦人，投資 workflow integration，不要追求 demo 友善的魔法。前端真正會贏的 AI 工具，不會像自動重寫機器，而會像守規矩的編輯器，尊重既有程式碼、既有標準、既有意圖。這樣它才是在降低風險，而不是製造風險。\u003C\u002Fp>","前端團隊應該停止把 AI 助手當成大範圍重構引擎，改把它當成受限編輯器；真正的效益來自精準修改，而不是整段重寫。","habr.com","https:\u002F\u002Fhabr.com\u002Fru\u002Farticles\u002F1028734\u002F",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1777334803961-exe5.png","zh",0,false,"2026-04-28T00:06:27.781603+00:00","2026-04-28T00:06:27.551+00:00","done","e81b5d94-745c-4f3e-b62e-d4b2e37b1022","why-frontend-teams-should-stop-treating-ai-as-a-rewrite-mach-zh","industry","a80ab651-6796-4323-891f-dcfa33a6a779","published","2026-04-28T09:00:11.472+00:00",[],{"id":21,"slug":26,"title":27,"language":28},"why-frontend-teams-should-stop-treating-ai-as-a-rewrite-mach-en","Why frontend teams should stop treating AI as a rewrite machine","en",[30,36,42,48,54,60],{"id":31,"slug":32,"title":33,"cover_image":34,"image_url":34,"created_at":35,"category":20},"c3b45aac-c24c-4c09-9e95-73ff729d9a62","why-ai-infrastructure-is-now-the-real-moat-zh","為什麼 AI 基礎設施才是真正的護城河","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778875851377-xatg.png","2026-05-15T20:10:37.227561+00:00",{"id":37,"slug":38,"title":39,"cover_image":40,"image_url":40,"created_at":41,"category":20},"cd078ce9-0a92-485a-b428-2f5523250a19","circles-agent-stack-targets-machine-speed-payments-zh","Circle 推出 Agent Stack，瞄準機器速度支付","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778871663628-uyk5.png","2026-05-15T19:00:44.16849+00:00",{"id":43,"slug":44,"title":45,"cover_image":46,"image_url":46,"created_at":47,"category":20},"96d96399-f674-4269-997a-cddfc34291a0","iren-signs-nvidia-ai-infrastructure-pact-zh","IREN 綁上 Nvidia AI 基建","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778871057561-bukp.png","2026-05-15T18:50:37.57206+00:00",{"id":49,"slug":50,"title":51,"cover_image":52,"image_url":52,"created_at":53,"category":20},"de12a36e-52f9-4bca-8deb-a41cf974ffd9","circle-agent-stack-ai-payments-zh","Circle 推出 Agent Stack 做 AI 付款","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778870462187-t9xv.png","2026-05-15T18:40:30.945394+00:00",{"id":55,"slug":56,"title":57,"cover_image":58,"image_url":58,"created_at":59,"category":20},"e6379f8a-3305-4862-bd15-1192d3247841","why-nebius-ai-pivot-is-more-real-than-hype-zh","為什麼 Nebius 的 AI 轉型比炒作更真實","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778823044520-9mfz.png","2026-05-15T05:30:24.978992+00:00",{"id":61,"slug":62,"title":63,"cover_image":64,"image_url":64,"created_at":65,"category":20},"66c4e357-d84d-43ef-a2e7-120c4609e98e","nvidia-backs-corning-factories-with-billions-zh","Nvidia 出資 Corning 工廠擴產","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778822450270-trdb.png","2026-05-15T05:20:27.701475+00:00",[67,72,77,82,87,92,97,102,107,112],{"id":68,"slug":69,"title":70,"created_at":71},"ee073da7-28b3-4752-a319-5a501459fb87","ai-in-2026-what-actually-matters-now-zh","2026 AI 真正重要的事","2026-03-26T07:09:12.008134+00:00",{"id":73,"slug":74,"title":75,"created_at":76},"83bd1795-8548-44c9-9a7e-de50a0923f71","trump-ai-framework-power-speech-state-preemption-zh","川普 AI 框架瞄準電力、言論與州權","2026-03-26T07:12:18.695466+00:00",{"id":78,"slug":79,"title":80,"created_at":81},"ea6be18b-c903-4e54-97b7-5f7447a612e0","nvidia-gtc-2026-big-ai-announcements-zh","NVIDIA GTC 2026 重點拆解","2026-03-26T07:14:26.62638+00:00",{"id":83,"slug":84,"title":85,"created_at":86},"4bcec76f-4c36-4daa-909f-54cd702f7c93","claude-users-spreading-out-and-getting-better-zh","Claude 用戶更分散，也更會用","2026-03-26T07:22:52.325888+00:00",{"id":88,"slug":89,"title":90,"created_at":91},"bd903b15-2473-4178-9789-b7557816e535","openclaw-raises-hard-question-for-ai-models-zh","OpenClaw 逼問 AI 模型價值","2026-03-26T07:24:54.707486+00:00",{"id":93,"slug":94,"title":95,"created_at":96},"eeac6b9e-ad9d-4831-8eec-8bba3f9bca6a","gap-google-gemini-checkout-fashion-search-zh","Gap 把結帳搬進 Gemini","2026-03-26T07:28:23.937768+00:00",{"id":98,"slug":99,"title":100,"created_at":101},"0740e53f-605d-4d57-8601-c10beb126f3c","google-pushes-gemini-transition-to-march-2026-zh","Google 把 Gemini 轉換延到 2026 年 3…","2026-03-26T07:30:12.825269+00:00",{"id":103,"slug":104,"title":105,"created_at":106},"e660d801-2421-4529-8fa9-86b82b066990","metas-llama-4-benchmark-scandal-gets-worse-zh","Meta Llama 4 分數風波又擴大","2026-03-26T07:34:21.156421+00:00",{"id":108,"slug":109,"title":110,"created_at":111},"183f9e7c-e143-40bb-a6d5-67ba84a3a8bc","accenture-mistral-ai-sovereign-enterprise-deal-zh","Accenture 攜手 Mistral AI 賣主權 AI","2026-03-26T07:38:14.818906+00:00",{"id":113,"slug":114,"title":115,"created_at":116},"191d9b1b-768a-478c-978c-dd7431a38149","mistral-ai-faces-its-hardest-year-yet-zh","Mistral AI 迎來最硬的一年","2026-03-26T07:40:23.716374+00:00"]