[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"report-2026-02-27":3,"3NJ78qnWTn":762,"d3r5ieSOMx":777,"vBfL5BNoYH":787,"iCihbQtAla":797,"dLKCwV4Rrp":807,"6f7kyCjEzH":860,"2DGTpkdL4T":925,"K99hyQY5Tv":959,"pvmBsZNMnD":988,"WaRLV58K6I":1031,"ergGRWGEko":1098,"AcgBreD9Kr":1108,"vZk8TRhGVT":1118,"jR5dnP6bvZ":1128,"rsFDoFn7HV":1138,"rFNUGzxXL9":1148,"IEFrUTes9y":1158,"8BNOMHJcFC":1168,"yB9EAvEPRV":1178,"fVldwcb5o5":1188,"rqxEAD1AXB":1198,"ZqYOCmzVft":1208,"VQd3yUhAM8":1218,"2DFLciG8AY":1228,"5xkDVd2Hl5":1238,"E9Y1aNjjTR":1248,"fXVLzv2GIH":1306,"OYpRD2InVy":1317,"M85xUy3tRr":1343,"2LOwfVYnMK":1369,"DwQiXH6ooQ":1396,"TLt66NKFxw":1525,"WOg3OND78v":1690,"ry85YIB1vj":1711,"Rb1JuzHrQB":1732,"OEPqwOABEs":1742,"PVmN8lZRDS":1752,"w25wKBgBsS":1762,"ilxoVrX0LO":1772,"uvRiAQvutQ":1782,"7A3VfwENGV":1792,"ZK40yFBqHe":1825,"0qs0yWMYOw":1896,"tudDHWIZkw":1906,"03eBuOTvV0":1916,"sr8Q0Dyara":1940,"KmEYjwIwwB":2001,"pZWENJYWeh":2011,"qhD0Dkz7ce":2021,"31pS1CDd1i":2031,"E4TivuNare":2041,"TrJPgR4xhM":2051,"JgMSbf34rM":2061,"iq1SmaclbW":2071,"3gMCgU8OCh":2081,"KLXrpBbZR5":2091,"aJD1jdaOoJ":2101,"7GuMHxvQGS":2111,"CpI96411hB":2155,"ebE596AVnR":2166,"xMzdiPWChp":2222,"KVl8Z762jp":2248,"h3DAHuBNpE":2274,"cVewo968ci":2385,"vVRjtFUSPr":2401,"rWZ2U1cqpv":2426,"s7Wqw2OXvp":2443,"MCxaQbEdiS":2453,"ay0JVhl0PT":2463,"1JRvxIVohx":2473,"CJTPYcATJz":2483,"c4bEgSdKT9":2493,"1K2wM5vjjW":2503,"s91A4s5lQC":2547,"CaKgqFkX5y":2573,"VLKw5uqP9O":2632,"LfLWTsdB8U":2684,"yE03yFuJc6":2743,"RhhKm2b0iI":2858,"7nY32WeJnB":2883,"Xhz9tXtNZn":2900,"WvS2kWrerx":2910,"uwxVYIPLsb":2920,"ERUQPbgDAC":2930,"HbOEXN9pZH":3004,"vSJl8DBCjm":3027,"qJYDUw6u2k":3037,"sJ2wYjeayy":3073,"sGGxKL1PSq":3116,"o8E7QeMuiR":3126,"Y0UABDPikI":3136,"Ah3vCa3iLC":3240,"320v9ilQL5":3250,"4uJ3DFRd7U":3260,"tMETRK9W0v":3303,"bRxqNeZWiz":3313,"fMWOOc9HX3":3323,"bMM8tXIwlM":3352,"PPu4BqtcQ5":3412,"FVjdmlRJKT":3430,"C0ddnvLuC9":3440,"ES6PWHUg7c":3523,"lvMoFqWSqU":3543,"VMSaVbYTmz":3553,"AAjoLqqxHX":3592,"KbZyKL34LG":3634,"pot3wQ6IqO":3662,"ZbhUgguaR5":3672,"lGVctpsrxw":3722,"CkwezUJCdH":3776,"u8DZNQt3Ss":3792,"5gmdFhpgMT":3808,"8nhth55Evz":3833,"MfOFAsxidG":3879,"MLuSUawfqa":3889,"s6AMrTinFA":3899,"vTA1ElR51p":3950,"tcpamhdGAy":3970,"oJRRB0nuD8":3980,"a9zR21sYc9":4190,"Erh44fHKhJ":4200,"jm2mUgLbBe":4652,"1smT6p9byA":4836},{"report":4,"adjacent":760},{"version":5,"date":6,"title":7,"sources":8,"hook":13,"deepDives":14,"quickBites":418,"communityOverview":733,"dailyActions":734,"outro":759},"20260301.0","2026-02-27","AI 趨勢日報：2026-02-27",[9,10,11,12],"community","github","google","openai","API 安全信任模型悄然崩潰、消費級 GPU 突破百億參數本地推論門檻、技能生態在 24 小時內引爆自發工具浪潮——雲端 AI 的三大隱性假設同日受到挑戰。",[15,130,208,273,342],{"category":16,"source":11,"title":17,"subtitle":18,"publishDate":6,"tier1Source":19,"supplementSources":22,"tldr":39,"context":51,"devilsAdvocate":52,"community":55,"hypeScore":72,"hypeMax":73,"adoptionAdvice":74,"actionItems":75,"policyDetail":85,"complianceImpact":86,"industryImpact":96,"timeline":97},"policy","Google API 金鑰本非機密，但 Gemini 改變了規則","近 3,000 個公開金鑰已可靜默驗證 Gemini，帳單風險與隱私洩露同步浮現",{"name":20,"url":21},"Truffle Security","https://trufflesecurity.com/blog/google-api-keys-werent-secrets-but-then-gemini-changed-the-rules",[23,27,31,35],{"name":24,"url":25,"detail":26},"Gemini API Troubleshooting(Google AI for Developers)","https://ai.google.dev/gemini-api/docs/troubleshooting","Google 官方說明金鑰封鎖機制與帳單申訴流程",{"name":28,"url":29,"detail":30},"Firebase security checklist","https://firebase.google.com/support/guides/security-checklist","至今仍聲稱 Firebase API 金鑰非機密的官方文件",{"name":32,"url":33,"detail":34},"Previously harmless Google API keys now expose Gemini AI data(BleepingComputer)","https://www.bleepingcomputer.com/news/security/previously-harmless-google-api-keys-now-expose-gemini-ai-data/","主流資安媒體跟進報導，事件進入公眾視野",{"name":36,"url":37,"detail":38},"trufflesecurity/trufflehog(GitHub)","https://github.com/trufflesecurity/trufflehog","Truffle Security 開源金鑰偵測工具，可整合至 CI/CD 管線",{"tagline":40,"points":41},"你以為的「公開金鑰」，正在被人刷你的 Gemini 帳單",[42,45,48],{"label":43,"text":44},"政策","Google 長年告知開發者 API 金鑰非機密，Firebase 文件至今仍如此聲稱，但 Gemini 上線後同一組金鑰已具備呼叫 LLM 與消耗配額的能力，形成靜默的安全邊界轉移。",{"label":46,"text":47},"合規","Truffle Security 在 Common Crawl 資料集中發現 2,863 個可用的 Google API 金鑰，驗證後均可呼叫 Gemini 端點，波及私人檔案、快取資料與 LLM 使用費用。",{"label":49,"text":50},"影響","Google 已主動封鎖部分外洩金鑰並在 AI Studio 加入狀態通知，但既有文件矛盾未解，開發者應立即為所有舊有金鑰設定 API 範圍限制並輪替曾公開的金鑰。","Google 多年來在 Firebase 等平台文件中明確告知開發者：API 金鑰不是機密，可以放入前端程式碼、公開 Git 儲存庫，甚至 Common Crawl 可索引的網頁中。這個「公開即安全」的前提，讓無數開發者在無意間將金鑰曝光於公共網路。Truffle Security 的研究揭露，這個延續多年的安全假設，在 Gemini 服務上線後已悄然失效。\n\n#### 前因 1：文件明文說「非機密」的歷史\n\nFirebase 的安全檢查清單至今（2026-01-21 更新版本）仍寫明 Firebase API 金鑰不是機密，Maps JavaScript API 文件（2026-02-26 更新）同樣展示前端直接嵌入金鑰的做法，並僅以「未限制的金鑰可能遭濫用」輕描淡寫帶過風險。這套文件策略使開發者長期低估金鑰管理的必要性，形成系統性的安全認知缺口。\n\n#### 前因 2：Gemini 上線帶來「特權提升」路徑\n\n2025 年起，Google 陸續在各 GCP 專案中推出 Gemini 與 Generative Language API。問題的核心在於：一個已存在的 GCP 專案 API 金鑰，一旦有人——或自動化流程——在同一專案內啟用了生成式語言 API，該金鑰便可立即用於呼叫 Gemini 端點，無需重新核發、無需額外授權。Truffle Security 將此定義為「單服務特權提升」 (Single-Service Privilege Escalation) ，Google 在 2026-01-13 接受了這個分類。\n\n> **名詞解釋**\n> Single-Service Privilege Escalation（單服務特權提升）：指原本僅具低風險存取權限的憑證，因同一系統的新服務被啟用，導致其實際可存取範圍大幅擴張，而憑證持有人毫不知情。",[53,54],"Google 金鑰的設計原本就是用於低風險服務，舊有文件並非錯誤而是設計邊界的歷史遺留；真正的責任在於未在新服務上線時同步更新安全指引，而非整個金鑰架構的系統性失敗。","2,863 個受影響金鑰佔整體 GCP 用戶比例極小，且 Google 已主動封鎖已知外洩金鑰，媒體報導的緊迫程度可能造成不必要的恐慌，讓原本不需重構的小型靜態網站浪費工時。",[56,60,63,65,68],{"platform":57,"user":58,"quote":59},"Hacker News","neop1x","是的，但每位管理員都必須使用他們的產品 (Cloud Functions) ，設定 IAM，並對每個專案重複執行這些步驟。這顯然只是個權宜之計。",{"platform":57,"user":61,"quote":62},"gowld","我很想知道你以為把信用卡綁定進去是要幹嘛的。",{"platform":57,"user":61,"quote":64},"也許是有經驗的資安審查人員都被裁員了。",{"platform":57,"user":66,"quote":67},"SoftTalker","這只是公用事業模式而已，沒什麼特別惡意的。想想你的電力公司、水務公司等等。你用多少就付多少。如果有人來接上你戶外的水龍頭偷水，或把延長線插進你外牆插座偷電，你還是得付錢——除非你能抓到竊賊讓他賠償。",{"platform":69,"user":70,"quote":71},"X","@_JohnHammond（資安研究員暨 YouTuber）","Google API 金鑰過去不被視為「機密」，所以它們散落在整個網路上——但現在它們成了 Gemini 的一扇敞開的大門。Truffle Security 研究的快速摘要：近 3,000 個網站受影響⋯⋯包括 Google 自己 😅",4,5,"追整體趨勢",[76,79,82],{"type":77,"text":78},"Try","登入 Google AI Studio，檢視現有 API 金鑰的狀態面板，確認是否出現外洩警告通知，並對每個金鑰設定 API 範圍限制（僅允許必要的服務）與應用程式限制（綁定來源 IP 或 HTTP referrer）。",{"type":80,"text":81},"Build","在 CI/CD 管線中整合 TruffleHog，掃描所有 `AIza` 前綴字串（Google API 金鑰的常見前綴），偵測到金鑰時自動阻擋 PR 合併，定期稽核 GCP Console 的 Credentials 頁面。",{"type":83,"text":84},"Watch","追蹤 Firebase 安全文件的更新，觀察 Google 是否正式撤回「API 金鑰非機密」的官方聲明，以及是否在金鑰啟用新服務時引入顯式確認機制。","#### 核心條款\n\nGoogle 的應對措施分為兩層。第一層為事後封鎖：針對在 Common Crawl 等公開資料集中被偵測到的外洩金鑰，Google 已主動阻止其存取 Gemini 端點，受影響的金鑰呼叫時會收到錯誤訊息：`Your API key was reported as leaked. Please use another API key.` 第二層為預防性設計建議：Google 建議開發者改用 AI Studio 核發的金鑰，這類金鑰預設僅限 Google AI Studio 與 Gemini 使用範圍，降低跨服務特權提升的風險。\n\n#### 適用範圍\n\n所有持有 GCP 專案 API 金鑰的開發者均受影響，尤其是：\n\n- 曾在公開 Git 儲存庫、前端程式碼或可索引網頁中嵌入金鑰的開發者\n- 使用 Firebase、Maps JavaScript API 等歷史上文件明示「金鑰非機密」的服務的開發者\n- 其 GCP 專案中已啟用或未來將啟用 Generative Language API 的帳戶\n\n#### 執法機制\n\n目前 Google 的執法機制為被動偵測：僅對已知外洩（如 Common Crawl 資料集）的金鑰採取封鎖行動。未被偵測到的外洩金鑰仍可正常使用，產生的帳單風險由金鑰持有者自行承擔。Google 的帳單申訴流程可處理部分情況，但審核結果因案而異，並非保證退款。",[87,90,93],{"label":88,"markdown":89},"工程改造需求","開發者需要完成以下技術改造：\n\n- 稽核現有 GCP 專案的 API 金鑰清單，確認哪些金鑰所屬專案已啟用 Generative Language API\n- 為所有 API 金鑰設定 API 限制（僅允許必要的服務）與應用程式限制（綁定來源 IP 或 HTTP referrer）\n- 將前端直接使用的 API 金鑰遷移至伺服器端代理或短效憑證 (ephemeral tokens)\n- 輪替 (rotate) 所有曾公開出現過的舊有金鑰",{"label":91,"markdown":92},"合規成本估計","對於小型開發者或個人專案，金鑰審計通常可在半天內完成。對於擁有大量 GCP 專案的企業，則需要：\n\n- 人力：資安工程師盤點所有專案金鑰（視規模需 1-5 人天）\n- 工具：TruffleHog 等開源工具可掃描程式碼儲存庫（免費，但需整合進 CI/CD 管線）\n- 時間：金鑰輪替與應用程式重新部署的耗時視服務數量而定",{"label":94,"markdown":95},"最小合規路徑","最低限度的合規步驟：\n\n1. 登入 Google AI Studio，檢視金鑰狀態警告面板\n2. 前往 GCP Console → APIs & Services → Credentials，對每個金鑰加上 API 限制\n3. 搜尋程式碼儲存庫中所有 `AIza` 開頭字串（Google API 金鑰的常見前綴）\n4. 若發現曾公開曝光的金鑰，立即建立新金鑰並停用舊有金鑰","#### 直接影響者\n\n首當其衝的是：\n\n- 使用 Firebase 並已在前端嵌入 API 金鑰的 Web 開發者（Firebase 文件長期宣稱金鑰非機密）\n- 在 Common Crawl 可索引網頁中出現金鑰的網站所有人（已有 2,863 個確認受影響）\n- 使用 Maps JavaScript API 的開發者，相關文件至今仍示範前端嵌入方式\n\n#### 間接波及者\n\n- GCP 服務商與受管服務提供商 (MSP) ：需協助客戶稽核並修補金鑰配置\n- 使用 Google Cloud 金鑰管理的 SaaS 供應商：若客戶的 GCP 專案啟用了 Gemini，其金鑰風險等級已悄然提升\n- 企業資安合規部門：需重新評估組織內 Google 憑證的分類標準與存取控制政策\n\n#### 成本轉嫁效應\n\n攻擊者可利用外洩金鑰呼叫 Gemini API，產生的 LLM 推理費用直接計入金鑰所有者的 GCP 帳單。若未設定配額上限，受害者可能在短時間內累積大量費用。Google 的帳單申訴流程可處理部分情況，但審核結果因案而異，並非保證退款，最終費用風險仍由終端開發者承擔。",[98,102,105,108,111,114,117,121,126],{"date":99,"text":100,"phase":101},"2025-11-21","Truffle Security 向 Google 提交漏洞報告","past",{"date":103,"text":104,"phase":101},"2025-12-02","Google 將問題重新分類為已知錯誤 (bug)",{"date":106,"text":107,"phase":101},"2026-01-13","Google 正式將其分類為「單服務特權提升」",{"date":109,"text":110,"phase":101},"2026-02-12","Google 更新 Gemini API 疑難排解文件，說明金鑰封鎖機制與帳單申訴流程",{"date":112,"text":113,"phase":101},"2026-02-25","Truffle Security 公開發布研究報告",{"date":115,"text":116,"phase":101},"2026-02-26","BleepingComputer 等媒體跟進報導，事件進入主流視野",{"date":118,"label":119,"text":120,"phase":101},"0-6 月","短期","現有已外洩金鑰遭主動封鎖；開發者社群展開大規模金鑰稽核；Firebase 與 Maps 官方文件是否更新值得持續觀察",{"date":122,"label":123,"text":124,"phase":125},"6-18 月","中期","Google 可能修訂跨服務金鑰繼承的設計，要求新服務啟用時需明確授權而非自動繼承；第三方金鑰掃描工具更新偵測規則","future",{"date":127,"label":128,"text":129,"phase":125},"18 月+","長期","GCP 金鑰管理機制可能走向更細粒度的 OAuth scope 模型，逐步取代全域 API 金鑰的設計模式",{"category":131,"source":9,"title":132,"subtitle":133,"publishDate":6,"tier1Source":134,"supplementSources":137,"tldr":154,"context":166,"mechanics":167,"benchmark":168,"useCases":169,"engineerLens":178,"businessLens":179,"devilsAdvocate":180,"community":183,"hypeScore":199,"hypeMax":73,"adoptionAdvice":200,"actionItems":201},"tech","Qwen3.5 旗艦在高難度程式任務上大幅崩落","APEX benchmark 以 70 個真實 repo 測試揭露：397B 旗艦在最高難度跌至 1194 分，比自家 27B 版本還低",{"name":135,"url":136},"Reddit r/LocalLLaMA","https://www.reddit.com/r/LocalLLaMA/comments/1reds0p/qwen_35_craters_on_hard_coding_tasks_tested_all/",[138,142,146,150],{"name":139,"url":140,"detail":141},"Alibaba Cloud：Qwen3.5 官方發布說明","https://www.alibabacloud.com/blog/qwen3-5-towards-native-multimodal-agents_602894","Qwen3.5-397B-A17B 官方規格，包含 SWE-bench Verified 76.4% 的成績",{"name":143,"url":144,"detail":145},"OpenAI：為何 SWE-bench Verified 不再衡量前沿程式能力","https://openai.com/index/why-we-no-longer-evaluate-swe-bench-verified/","2026-02-23 發布，說明 SWE-bench Verified 已受污染，建議改用 SWE-bench Pro",{"name":147,"url":148,"detail":149},"HuggingFace：Qwen3.5-397B-A17B 模型卡","https://huggingface.co/Qwen/Qwen3.5-397B-A17B","架構細節：Gated DeltaNet 加稀疏 MoE、262,144 token 原生上下文",{"name":151,"url":152,"detail":153},"HuggingFace：Qwen3-Coder-Next 模型卡","https://huggingface.co/Qwen/Qwen3-Coder-Next","80B 總參數、3B 活躍參數的 48 層混合架構程式碼代理模型",{"tagline":155,"points":156},"規格越大不代表越強——真實難度的程式任務讓 Qwen3.5-397B 露出破綻",[157,160,163],{"label":158,"text":159},"技術","APEX 以 70 個真實 GitHub repo 和 ELO 評分測試，Qwen3.5-397B 在最高難度 (master) 跌至 1194 分，比自家 27B 版本低 190 分，比 GLM-4.7 量化版低 378 分，顯示大模型在高難度程式任務上存在非線性能力上限。",{"label":161,"text":162},"成本","397B 全尺寸模型需要 100GB+ VRAM，效果卻輸給 27B 版本；Apple Silicon 上的 Qwen3.5-27B 已可實用，本地部署性價比更高。",{"label":164,"text":165},"落地","agentic 框架選擇可造成同一模型超過 50% 的分數波動；APEX 排行榜正在遷移重算，現階段不宜以單一 benchmark 作為部署決策的唯一依據。","程式碼代理 (coding agent) 的能力評估在 2026 年陷入一場信任危機。一方面，各大廠商爭相在 SWE-bench Verified 上刷新紀錄，Qwen3.5-397B 官方宣稱達到 76.4%；另一方面，OpenAI 在 2026-02-23 正式宣告 SWE-bench Verified 已被污染，不再能衡量前沿模型的真實程式能力。社群因此迫切需要更可信的獨立評測管道，而 Reddit 社群分享的 APEX benchmark 結果，正是在這個背景下引爆討論。\n\n#### 痛點 1：標準 benchmark 已被訓練資料污染\n\nSWE-bench Verified 長期以來是程式碼代理的黃金標準，但隨著前沿模型規模擴大、訓練資料範圍擴展，測試集題目越來越容易被「見過」。OpenAI 的公告直接指出這一問題並建議改用 SWE-bench Pro。這意味著模型在 SWE-bench 上的高分，部分可能來自「記住答案」而非真正的推理與修復能力，使得官方數字對開發者的參考價值大打折扣。\n\n> **名詞解釋**\n> SWE-bench Verified 是由 Princeton NLP 建立的程式碼修復 benchmark，要求模型根據 GitHub issue 自動提交正確的程式碼修復 patch；Verified 版本由人工驗證確保題目的可解性與品質。\n\n#### 痛點 2：模型規模與任務難度之間的非線性落差\n\n直覺上，更大的模型應該在更難的任務上表現更好。但 APEX 測試數據顯示，Qwen3.5-397B 在 hard/expert 難度取得約 1550 分，卻在 master 難度大幅滑落至 1194 分——而 Qwen3.5-27B 在同場景維持 1384 分，GPT-OSS-20B 更達到 1405 分。「更多參數 = 更強能力」的假設在高難度程式任務上並不成立，暗示旗艦模型的能力天花板可能與訓練資料分佈或架構選擇有關。\n\n#### 舊解法\n\n過去開發者通常依賴官方 benchmark 分數（SWE-bench Verified、HumanEval、MBPP）做模型選型決策。這些數字生產容易、易於比較，但多在單一函式修復或合成測試集上測量，未必反映面對複雜依賴關係的完整 repo 時的真實 agentic 表現。","Qwen3.5-397B 在標準 benchmark 上的亮眼數字，為何到了 APEX 真實 repo 測試就顯著下滑？理解這個問題需要拆解三個機制：測試方法的差異、模型架構的特性，以及框架對 agentic 任務的隱性影響。\n\n#### 機制 1：APEX 的真實 repo 測試方法論\n\nAPEX 從 GitHub 蒐集 70 個真實 repo 的程式任務，讓模型在 agentic tool-use 設定下執行——可呼叫 shell、搜尋程式碼、讀寫檔案，模擬真實工程師的工作流程。評分採用 pairwise ELO 制度，從正確性、完整性、品質與效率四個維度評估，截至測試時排行榜收錄 51 個模型、累積 3,431 次執行。這與合成測試集的「給一個函式、改一行程式碼」有本質差異。\n\n> **名詞解釋**\n> ELO 制度源自西洋棋排名系統，用來計算玩家（或模型）的相對實力分數；pairwise ELO 讓每對模型在同一任務上互相比較，獲勝方得分、落敗方扣分，最終形成連續分數排行榜，能處理模型數量不等、執行次數不一的情況。\n\n#### 機制 2：Qwen3.5-397B 的架構特性與難度崩落\n\nQwen3.5-397B-A17B 採用 Gated DeltaNet 加上稀疏 MoE 的混合架構，總參數 397B 但每次推理僅啟動 17B 活躍參數。官方宣傳的 SWE-bench Verified 76.4% 令人印象深刻，但在 APEX 的 master 難度任務上分數僅 1194——低於 Qwen3.5-27B 的 1384，更遠低於 GLM-4.7 量化版的 1572。可能的解釋是：master 難度任務需要更深度的跨檔案推理與狀態追蹤，而稀疏啟動架構在這類需要全域一致性的任務上存在固有局限。\n\n> **名詞解釋**\n> MoE（Mixture of Experts，混合專家架構）是一種神經網路設計，模型由多個「專家」子網路組成，每次推理只激活其中少數幾個，使超大參數模型能以較低計算成本運作，但可能在需要跨專家協調的複雜任務上表現不穩定。\n\n#### 機制 3：框架敏感性——benchmark 的隱藏變數\n\nReddit 社群評論指出一個關鍵問題：agentic 框架的設計會大幅影響模型的 benchmark 分數，在 Terminal Bench 2 和 Sanity Harness 上，同一模型換框架可以出現超過 50% 的分數波動。開源模型對「糟糕」的框架尤其敏感，因為它們的 instruction following 和工具呼叫格式比商業 API 更不穩定。APEX 目前使用自訂框架，尚未與 SWE-agent、OpenHands、Agentless 等主流框架交叉驗證，因此 Qwen3.5-397B 的低分有多少來自模型本身、多少來自框架，仍無定論。\n\n> **白話比喻**\n> 就像一位頂尖廚師被迫使用劣質廚具——廚師的技術沒有改變，但出餐品質大打折扣。agentic 框架就是那套廚具，選得好不好直接決定模型能發揮多少真實能力。","#### APEX ELO 分數（master 難度，Reddit 引用快照）\n\n| 模型 | APEX ELO(master) |\n|---|---|\n| GLM-4.7 量化版 | 1572 |\n| GPT-OSS-20B | 1405 |\n| Qwen3.5-27B | 1384 |\n| Qwen3-Coder-Next | 1328 |\n| Qwen3.5-35B MoE | 1256 |\n| Qwen3.5-397B-A17B | 1194 |\n\n#### 重要注意事項\n\n- 以上數字來自 Reddit 貼文引用的 APEX 排行榜快照，2026-02-27 資料正在遷移重算，最終數字可能有所調整\n- GLM-4.7 的具體版本（GLM-4.7-Flash 小模型 vs. Unsloth 版 100GB+ 全尺寸）尚未經社群確認\n- Codex 5.3 分數「接近 GPT-5.2」，但貼文未提供具體 ELO 數字\n- Qwen3.5-397B 在 hard/expert 難度約 1550 分，master 難度大幅下滑約 356 分\n\n#### 官方 benchmark（Qwen3.5-397B，供對照）\n\n- SWE-bench Verified：76.4%（已知存在污染問題）\n- Terminal Bench 2：52.5%",{"recommended":170,"avoid":174},[171,172,173],"中等難度的程式輔助任務（bug 修復、功能補全）：選擇 Qwen3.5-27B 或 35B MoE 版本，master 難度以下的性價比更高","本地部署低延遲補全：Apple M2 Ultra（192GB 統一記憶體）上跑 27B 版本，prefill 速度已足夠實際使用","多模型協作工作流：以 Qwen3.5 負責程式實作，搭配策略規劃型模型分工，降低單一模型的能力瓶頸",[175,176,177],"僅憑官方 SWE-bench 分數就將 397B 部署為生產 coding agent：master 難度任務可能表現遠低預期","不控制框架變數就直接比較跨 benchmark 分數：換框架可造成 50%+ 分數波動，跨測試數字無可比性","量化版 GLM-4.7 的盲目跟進：具體版本（Flash vs. 全尺寸）尚未確認，採購前需先釐清","#### 環境需求\n\n- Qwen3.5-397B-A17B：FP8 量化需要約 250GB+ VRAM，建議多 GPU 節點；全精度需求更高\n- Qwen3.5-27B：單張 A100 80GB 可完整載入 (BF16) ；Apple M2 Ultra（192GB 統一記憶體）可本地運行\n- agentic 框架：SWE-agent、OpenHands、Agentless 均可選用，但框架選擇是首要變數，建議先固定框架再比較模型\n\n#### 最小 PoC\n\n```python\n# 使用 OpenHands 快速驗測 Qwen3.5-27B（需先啟動 vLLM 端點）\nfrom openhands.controller import AgentController\nfrom openhands.llm.llm import LLM\n\nllm = LLM(\n    model=\"openai/Qwen3.5-27B\",\n    base_url=\"http://localhost:8000/v1\",\n    api_key=\"your-key\"\n)\n\ncontroller = AgentController(llm=llm)\nresult = controller.run(task=\"Fix the failing test in tests/test_parser.py\")\nprint(result)\n```\n\n#### 驗測規劃\n\n建議在你的實際 codebase 上選取 10–20 個已知難度的 issue，分別用至少兩個主流框架（如 SWE-agent 和 OpenHands）測試同一模型。若分數差異超過 20%，代表框架影響大於模型本身，應優先最佳化框架設定，再評估模型選型。\n\n#### 常見陷阱\n\n- 直接引用 SWE-bench Verified 分數做採購決策：已知污染問題使高分不等於真實場景領先\n- 忽略 ELO 分數的難度分層：Qwen3.5-397B 在 hard/expert 難度表現良好，問題出在 master 難度以上\n- 沒有控制框架變數就比較不同 benchmark 的數字：跨測試的分數沒有可比性\n\n#### 上線檢核清單\n\n- 觀測：記錄模型在你的任務難度分布下的 pass@1 率，與 APEX ELO 分數交叉驗證\n- 成本：397B 模型的 API 費用或硬體折舊 vs. 27B 本地部署的 TCO，建議先試算再決定\n- 風險：APEX 排行榜更新後（預計 24 小時內）重新核對數字；GLM-4.7 版本確認前暫不跟進","#### 競爭版圖\n\n- **直接競品**：GLM-4.7（量化版 APEX 1572 暫居第一，但版本未確認）、GPT-OSS-20B(1405) 、Codex 5.3（接近 GPT-5.2）\n- **間接競品**：Anthropic Claude Sonnet（API 服務）、Google Gemini 系列、Meta Llama 系列的程式碼代理能力\n\n#### 護城河類型\n\n- **工程護城河**：Qwen3.5 的混合 Gated DeltaNet + 稀疏 MoE 架構提供 262,144 token 的原生上下文，對多檔案 agentic 任務有結構性優勢；Qwen3-Coder-Next 的訓練配方已複用於 Qwen3.5，技術路徑具延續性\n- **生態護城河**：開源授權使社群遷移門檻低；Alibaba Cloud 提供商業部署路徑，對亞太企業有採購便利性\n\n#### 定價策略\n\nQwen3.5 系列以開源授權發布，本地部署無 API 費用。商業場景可透過阿里雲 API 調用，具體定價尚未在本次測試報告中揭露。競爭對手 GLM-4.7 的定價策略亦未公開，現階段成本比較有限。\n\n#### 企業導入阻力\n\n- 397B 全尺寸模型的硬體門檻高（需多 GPU 節點），多數中小型企業無法本地部署，必須依賴 API\n- benchmark 結果的不確定性（框架敏感、排行榜遷移中）使企業難以建立信心，採購決策難以加速\n- 競爭格局快速變化（GLM-4.7、GPT-OSS-20B 均有競爭力），採購週期與模型迭代速度不匹配\n\n#### 第二序影響\n\n- 若 APEX 排行榜更新後 Qwen3.5-397B 數字改善，可能觸發社群重新評估，帶動採用率回升\n- GLM-4.7 若確認以全尺寸版本奪冠，將使智譜 AI 聲量大幅提升，可能吸引企業採購評估\n- SWE-bench Verified 被廢棄的趨勢加速後，缺乏公認替代標準將使模型選型更依賴內部測試，增加企業研究成本\n\n#### 判決：先觀望（benchmark 數字尚在重算，框架敏感性未解）\n\nQwen3.5-397B 的官方 benchmark 與社群獨立測試之間存在顯著落差。APEX 排行榜正在遷移重算，框架敏感性問題尚未有交叉驗證，現階段不宜以旗艦規模做部署決策。若有本地部署需求，27B 版本在 master 難度表現更穩定且硬體門檻低；建議等待排行榜更新與多框架交叉驗證結果出爐後再做評估。",[181,182],"APEX 使用自訂 agentic 框架，且社群已指出框架選擇可造成 50%+ 分數波動——Qwen3.5-397B 的低分可能是框架相容性問題，而非模型能力的真實反映，換用主流框架後結果可能大幅改變","70 個任務的樣本量在統計上相對有限，ELO 排名在小樣本下容易因少數困難案例而劇烈波動；排行榜正在遷移重算也意味著目前引用的數字具有時效性限制",[184,187,190,193,196],{"platform":135,"user":185,"quote":186},"u/metigue","你是在用自訂的 agentic 框架嗎？你應該用幾個主流框架測試，看看是不是框架拖累了某些模型的表現。主要原因是，在 Terminal Bench 2 和 Sanity Harness 上，同一個模型換框架可以看到超過 50% 的分數波動，而開源模型對「糟糕」的 agentic 框架特別敏感。其他 benchmark 的結果也顯示，哪個模型「最強」會根據你選擇的框架而大幅改變。",{"platform":135,"user":188,"quote":189},"u/UmpireBorn3719","嗯……根據你的結果，gpt-oss-20b（1405 分）比 qwen3 coder next（1328 分）還要強？",{"platform":135,"user":191,"quote":192},"u/soyalemujica","談到量化版的 GLM-4.7，你說的是特定的 GLM-4.7-Flash 小模型，還是 Unsloth 那個 100GB+ 的大版本？",{"platform":69,"user":194,"quote":195},"@olympum（Bruno Fernandez-Ruiz，科技主管）","Qwen 3.5 在 M2 Ultra 上的預填充速度實際上夠快，可以用於程式碼撰寫。搭配 Gemini 3.1 Pro（策略制定）、GPT 5.3 Codex（規劃）和 Minimax M2.5（程式碼審查）使用後，Anthropic 終於遇到了真正的競爭對手。",{"platform":69,"user":197,"quote":198},"@wzhao_nlp（Wenting Zhao，Qwen 團隊 NLP 研究員）","對於 Qwen-3.5，我們採用了 Qwen3-Coder-Next 的訓練配方並擴大了模型參數，這帶來了更強大的程式碼代理能力。非常期待聽到你的使用案例、我們應該關注的新 benchmark，以及如何改進我們的模型。",3,"先觀望",[202,204,206],{"type":77,"text":203},"用 Qwen3.5-27B（而非 397B）在你自己的 repo 上跑 5–10 個 issue，並用兩個不同框架（如 SWE-agent 和 OpenHands）比較分數差異，確認框架影響程度後再決定模型選型",{"type":80,"text":205},"設計一組 10–20 個「內部 benchmark」任務，覆蓋你實際工作流中的難度分布，建立可重複驗測的 agentic 評估流水線，不依賴單一外部 benchmark 做選型決策",{"type":83,"text":207},"追蹤 APEX 排行榜更新（預計 24 小時內重算完成）、GLM-4.7 全尺寸版本的社群確認，以及 OpenAI SWE-bench Pro 的採用情況——這三件事決定了下一輪模型選型的基準線",{"category":16,"source":11,"title":209,"subtitle":210,"publishDate":6,"tier1Source":211,"supplementSources":214,"tldr":227,"context":236,"policyDetail":237,"complianceImpact":238,"industryImpact":245,"timeline":246,"devilsAdvocate":261,"community":264,"hypeScore":199,"hypeMax":73,"adoptionAdvice":265,"actionItems":266},"Google 與麻州 AI 樞紐攜手，為全州居民提供免費 AI 培訓","麻州率先以政府主導方式推動全民 AI 技能升級，Google 課程免費開放至 2027 年底",{"name":212,"url":213},"Google Blog","https://blog.google/company-news/outreach-and-initiatives/grow-with-google/google-ai-training-massachusetts-residents/",[215,219,223],{"name":216,"url":217,"detail":218},"Massachusetts Governor's Press Release","https://www.mass.gov/news/governor-healey-and-google-announce-new-statewide-partnership-to-provide-free-ai-training-to-residents","Governor Healey 官方聲明與計畫詳細內容",{"name":220,"url":221,"detail":222},"Massachusetts AI Hub - Grow with Google","https://aihub.masstech.org/google-certificates","報名入口與完整課程清單",{"name":224,"url":225,"detail":226},"Boston.com 報導","https://www.boston.com/news/local-news/2026/02/26/all-mass-residents-to-get-free-access-to-google-ai-training-classes-healey-says/","在地媒體報導與背景說明",{"tagline":228,"points":229},"麻州全民免費 AI 培訓：政府與科技巨頭合作的新範本",[230,232,234],{"label":43,"text":231},"麻州政府與 Google 攜手，為全州居民免費提供 AI 培訓課程至 2027 年底，涵蓋 AI Professional Certificate 及多項職涯發展證書，無學歷與年齡限制。",{"label":46,"text":233},"課程採自進度線上形式，零財務成本，居民填寫意願表單即可開始，時間投入從 10 小時到 6 個月不等，適合學生、在職員工及小型企業主。",{"label":49,"text":235},"此合作模式可能成為其他州政府效仿的藍本，預示政府在 AI 人才培育上將扮演更積極的角色，並對在地付費培訓市場形成一定程度的競爭壓力。","麻州 (Massachusetts) 長期以來是美國科技人才的重要基地，哈佛、MIT 等頂尖學府坐落於此，但隨著 AI 浪潮席捲全球就業市場，州政府開始面臨如何確保非技術背景居民不被時代淘汰的壓力。\n\n#### 前因 1：AI 技能缺口威脅中低收入勞工\n\n隨著生成式 AI 工具在職場中快速普及，雇主對具備基礎 AI 素養的員工需求急速上升。麻州製造業、零售、行政支援等傳統職類正面臨自動化衝擊，這些領域的從業者往往缺乏自行投資再訓練的資源。傳統職訓計畫的資金多集中在特定行業或高學歷族群，一般居民難以受惠。\n\n#### 前因 2：Google 已在麻州累積深厚基礎\n\nGoogle 的 Grow with Google 計畫自 2017 年起在全美各州推動數位技能培訓，據報已有超過 25 萬名麻州居民完成數位技能課程。全球超過 100 萬人取得 Google Career Certificate，其中逾 70% 在 6 個月內獲得正面職涯影響。這個既有基礎讓麻州政府得以在現有機制上快速擴展，而非從零開始建立培訓體系。","此次公告的核心是麻州政府透過 MassTech 旗下的麻州 AI 樞紐 (Massachusetts AI Hub) ，與 Google 合作提供無需額外費用的 AI 相關課程。\n\n#### 核心條款\n\n主要提供課程包括 Google AI Professional Certificate、Google AI Essentials、Google Agile Essentials，以及 Data Analytics、IT Support、Project Management 等職涯發展證書。其中 AI Professional Certificate 包含 20 餘項實作活動，並附贈 3 個月免費 Google AI Pro 存取權限。課程全為自進度線上形式，完成後可取得 Google 官方認證。\n\n> **名詞解釋**\n> Google AI Professional Certificate：Google 官方推出的 AI 實務技能認證課程，涵蓋機器學習基礎、AI 工具應用與實作專案，面向非學術背景的職場人士設計。\n\n#### 適用範圍\n\n所有麻州居民均可申請，無學歷、職業或年齡限制。免費存取期間至 2027 年 12 月 31 日止，涵蓋學生、在職員工及小型企業主。\n\n#### 執法機制\n\n本計畫屬志願性質的公共服務計畫，無罰則機制。執行機構為麻州 AI 樞紐（MassTech 旗下部門），申請流程如下：\n\n1. 前往 MA AI Hub 網站填寫意願表單\n2. 自行開始自進度線上課程\n3. 完成課程後取得 Google 認證",[239,241,243],{"label":88,"markdown":240},"就個別開發者而言，AI Professional Certificate 的課程設計以實作為主，建議具備基礎 Python 操作能力。對企業而言，若希望將此培訓納入員工發展計畫，HR 部門需與麻州 AI 樞紐協調批次報名流程，並評估課程內容與現有技能地圖的對應關係。",{"label":91,"markdown":242},"本計畫本身無財務成本（課程全數免費）。時間投入方面，Google AI Essentials 估計需 10 至 15 小時，AI Professional Certificate 依個人進度約需 3 至 6 個月。企業若大規模推動員工報名，需投入一定的行政協調人力。",{"label":94,"markdown":244},"- 前往 aihub.masstech.org/google-certificates 填寫意願表單\n- 根據自身程度選擇入門課程（推薦先從 AI Essentials 開始）\n- 依自進度完成課程並申請 Google 認證","#### 直接影響者\n\n- **麻州居民**：尤其是中低收入、非技術背景的勞工，可免費獲得具市場認可的 AI 技能認證\n- **在地職訓機構**：社區大學與職業培訓學校可能面臨部分生源轉移，原有的付費數位技能課程市場受到衝擊\n- **在地 AI 培訓新創**：原以麻州市場為主的付費課程提供者需重新評估定價策略，面對政府補貼帶來的免費競爭\n\n#### 間接波及者\n\n麻州雇主可更容易招募到具備 Google 認證基礎 AI 素養的員工，降低內部培訓成本。其他州政府（尤其是科技產業集中的加州、紐約、德州）可能效仿此模式，推動類似的州政府與科技巨頭培訓合作計畫。\n\n#### 成本轉嫁效應\n\n短期內課程費用由 Google 與州政府共同補貼，居民無需自付。然而長期而言，若大量居民取得 AI 相關認證後進入就業市場，相關技能的薪資溢價可能逐漸收窄，對已持有相關證書的從業者形成供給側壓力。",[247,249,252,255,258],{"date":115,"text":248,"phase":101},"Governor Healey 與 Google 公開宣布合作計畫",{"date":250,"text":251,"phase":125},"2027-12-31","全州居民免費存取課程截止日期",{"date":253,"label":119,"text":254,"phase":101},"0 至 6 個月","早期採用者完成 AI Essentials 課程，麻州 AI 樞紐網站流量大增，媒體與政治人物持續關注",{"date":256,"label":123,"text":257,"phase":125},"6 至 18 個月","首批 AI Professional Certificate 持證者進入就業市場，雇主開始評估此認證的實際職場價值",{"date":259,"label":128,"text":260,"phase":125},"18 個月以上","觀察其他州政府是否跟進類似計畫，以及 Google 是否將此模式複製至其他州",[262,263],"Google 認證的市場認可度仍有疑問：雇主對「Google AI Professional Certificate」的評價可能遠不如傳統學位或頂尖 MOOC 平台的付費認證，持證者在求職市場的實際競爭力有待驗證。","線上自進度課程的完課率長期偏低，業界平均不到 10%，「全州居民免費」的政治宣傳效果恐遠大於實際職涯轉換成效，計畫最終可能淪為形象工程。",[],"值得一試",[267,269,271],{"type":77,"text":268},"若你是麻州居民，可前往 aihub.masstech.org/google-certificates 填寫意願表單，免費試讀 Google AI Essentials，評估課程品質後再決定是否投入完整的 AI Professional Certificate。",{"type":80,"text":270},"若負責企業培訓或 HR 計畫，可研究如何將 Google Career Certificates 納入現有員工發展路徑，並與麻州 AI 樞紐協調批次報名機制，以降低企業培訓成本。",{"type":83,"text":272},"追蹤其他州政府是否效仿麻州推出類似的州政府×科技巨頭免費 AI 培訓合作，並關注麻州計畫公布的完課率與就業轉換數據，以評估此類政策的實際效益。",{"category":274,"source":12,"title":275,"subtitle":276,"publishDate":6,"tier1Source":277,"supplementSources":280,"tldr":301,"context":310,"mechanics":311,"benchmark":312,"useCases":313,"engineerLens":322,"businessLens":323,"devilsAdvocate":324,"community":327,"hypeScore":72,"hypeMax":73,"adoptionAdvice":200,"actionItems":335},"ecosystem","OpenAI Codex 與 Figma 打通雙向工作流：設計稿與程式碼的圍牆正在拆除","透過 Figma MCP Server，開發者可在程式碼與可編輯設計稿之間雙向轉換——但方案配額限制讓個人用戶幾乎無法受惠",{"name":278,"url":279},"OpenAI Blog","https://openai.com/index/figma-partnership/",[281,285,289,293,297],{"name":282,"url":283,"detail":284},"Figma Blog","https://www.figma.com/blog/introducing-codex-to-figma/","Figma 官方說明 Codex 整合的設計端工作流",{"name":286,"url":287,"detail":288},"Figma MCP Server 遠端安裝文件","https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/","OAuth 設定與 CLI 指令說明",{"name":290,"url":291,"detail":292},"Figma MCP Server 方案與權限文件","https://developers.figma.com/docs/figma-mcp-server/plans-access-and-permissions/","各方案工具呼叫配額明細",{"name":294,"url":295,"detail":296},"TechCrunch 報導","https://techcrunch.com/2026/02/26/figma-partners-with-openai-to-bake-in-support-for-codex/","第三方媒體對此合作的背景分析",{"name":298,"url":299,"detail":300},"OpenAI Skills：figma-implement-design","https://raw.githubusercontent.com/openai/skills/main/skills/.curated/figma-implement-design/SKILL.md","官方 Skill 實作範本與 Prompt 結構",{"tagline":302,"points":303},"設計稿與程式碼之間的單向傳送帶，現在可以雙向走了",[304,306,308],{"label":158,"text":305},"Figma MCP Server 提供遠端與本地兩種模式，讓 Codex 可讀取 Figma 設計脈絡生成程式碼，也能從現有 UI 逆向生成可編輯的 Figma 設計檔案，實現真正的雙向工作流。",{"label":161,"text":307},"Enterprise 每日 600 次工具呼叫、Org/Pro 每日 200 次；Starter 方案每月僅 6 次，個人用戶幾乎無法在日常開發中穩定使用此功能。",{"label":164,"text":309},"Codex 已有超過 100 萬週活躍用戶，使用量自 2026 年初成長超過 400%，Figma 整合是擴張設計×工程協作場景的關鍵卡位動作。","OpenAI Codex 與 Figma 的整合，代表設計與工程之間長達十年的協作裂縫，正試圖以 AI 為橋梁縫合。Codex 產品負責人 Alexander Embiricos 明確表示，這個工作流「不預設你是設計師還是工程師」，而是讓兩種角色都能從自己熟悉的工具出發，無縫進入對方的領域。\n\n#### 痛點 1：設計稿與程式碼之間的永恆鴻溝\n\n傳統工作流中，Figma 是設計師的主場，程式碼編輯器是工程師的戰場。兩者之間的資訊傳遞仰賴截圖、Slack 訊息、以及充滿誤解的口頭描述。設計稿改一個色票，工程師需要重新比對手動更新；工程師加了一個響應斷點，設計師完全不知情。這種「設計→標注→開發→回設計」的單向循環，消耗了大量跨職能溝通成本，在快速迭代的產品環境中格外致命。\n\n#### 痛點 2：現有 AI 工具仍是各守一方的單向助手\n\nGitHub Copilot、Cursor 等 AI 程式碼工具擅長從文字描述生成程式碼，但無法理解或輸出 Figma 原生格式；Figma AI（如 Make）可生成設計稿草稿，但缺乏與真實程式碼庫的雙向同步能力。開發者仍需在兩套工具之間手動搬運設計意圖，AI 只解決了各自領域的局部問題，橋接點依然是人工。\n\n#### 舊解法：第三方插件轉碼工具的侷限\n\nLocofy、Anima、Builder.io 等工具試圖解決 Figma→程式碼的轉換問題，但方向仍是單向的，且轉換品質參差不齊，無法處理複雜的互動邏輯與狀態管理，最終仍需大量人工修正才能進入生產環境。","Figma MCP Server 是這次整合的核心基礎設施，讓 Codex 能以標準化協議讀寫 Figma 設計資源，實現真正的雙向工作流，而非過去工具鏈中的單向輸出。\n\n#### 機制 1：雙模式 MCP 端點\n\nFigma MCP Server 提供兩種接入模式：**遠端模式**透過 `https://mcp.figma.com/mcp` 以 OAuth 認證連接 Figma 雲端服務；**本地模式**透過 `http://127.0.0.1:3845/mcp` 接入 Figma 桌面應用程式。遠端模式適合 CI/CD 環境或無頭伺服器場景；本地模式則能存取未發布的設計稿草稿與本地資源，適合開發階段的快速迭代。\n\n> **名詞解釋**\n> MCP(Model Context Protocol) 是 Anthropic 提出的開放標準，讓 AI 模型透過統一介面呼叫外部工具與資料來源，功能上類似 AI 應用的 REST API 規範，讓不同 AI 客戶端（Codex、Gemini CLI 等）都能用相同方式接入同一個工具服務。\n\n#### 機制 2：雙向設計↔程式碼工作流\n\n整合支援兩個方向的轉換：**Figma → Code** 方向允許 Codex 讀取 Figma Design、Make、FigJam 的設計脈絡（元件樣式、層級結構、尺寸標注），直接生成對應前端程式碼；**Code → Figma** 方向讓開發者可以從現有 UI 程式碼或描述生成可編輯的 Figma 設計檔案，反向輸出設計稿供設計師繼續迭代。後者是本次整合最具突破性的部分，過去幾乎所有工具都只走單向。\n\n#### 機制 3：工具呼叫配額管理\n\nFigma 對 MCP 工具呼叫設有方案分級限制：Enterprise 方案每日 600 次、Org／Pro 開發席位每日 200 次、Starter／檢視者／協作者每月僅 6 次。超出配額後請求將被拒絕，不會自動升級計費。此設計將「AI 功能」直接綁定付費席位，意味著個人免費用戶幾乎無法在日常工作中建立穩定的工作流。\n\n> **白話比喻**\n> 這就像在設計師的 Figma 和工程師的程式碼編輯器之間裝了一條雙向傳送帶：以前只能從設計→程式碼單向走，現在可以把寫好的程式碼「逆送」回設計稿，讓設計師繼續在熟悉的工具裡修改——前提是你付了夠多的月費。","#### 用量成長數據\n\nOpenAI 報告 Codex 目前擁有超過 100 萬週活躍用戶，自 2026 年初以來使用量成長超過 400%，顯示 Codex CLI 的採用率正在加速。然而本次 Figma 整合剛於 2026-02-26 發布，目前尚無公開的設計↔程式碼轉換精確度、往返一致性或元件還原度的基準測試數據，實際效果需待社群進行獨立評測後才有更清晰的參考依據。",{"recommended":314,"avoid":319},[315,316,317,318],"前端 UI 組件開發：從 Figma 設計稿直接生成 React／Vue 組件，減少標注溝通成本","設計系統維護：讓程式碼組件與 Figma Design Token 保持同步，降低版本飄移風險","快速原型驗證：從 FigJam 白板草稿生成可運行的前端原型，加速設計決策循環","舊有前端移植：將無型別 JS 舊版前端遷移至 TypeScript 時，用設計稿作為視覺錨點輔助重構",[320,321],"需要精密動畫與互動邏輯的場景：Figma MCP 目前以靜態設計稿轉換為主，複雜的動畫狀態機難以雙向同步","Starter 方案個人用戶的日常工作流：每月 6 次工具呼叫配額在實際專案測試階段即可能耗盡，建議先評估方案升級成本再導入","#### 環境需求\n\n需要安裝 Codex CLI，並持有有效的 OpenAI API Key。Figma 帳號需達 Org／Pro 開發席位以上（每日 200 次工具呼叫）；若使用 Starter 方案則每月僅 6 次，不適合日常開發使用。本地模式需保持 Figma 桌面應用程式持續開啟。\n\n#### 遷移／整合步驟\n\n**遠端模式**（推薦用於 CI/CD 環境）：\n\n```bash\ncodex mcp add figma --url https://mcp.figma.com/mcp\n```\n\n**本地模式**（透過 Figma 桌面應用，可存取未發布草稿）：\n\n```toml\n# ~/.codex/config.toml\n[mcp_servers.figma]\nurl = \"http://127.0.0.1:3845/mcp\"\n```\n\n設定後在 Figma 桌面應用啟用 MCP Server，即可在 Codex CLI 提示詞中直接引用 Figma 設計稿進行轉換。\n\n#### 驗測規劃\n\n建議先用一個現有 UI 組件做端對端測試：從 Figma 匯出組件描述 → Codex 生成 React 程式碼 → 再將修改後程式碼逆向生成 Figma 稿。比對生成稿與原稿的元件樣式一致性（間距、色票、字體大小），評估在你的設計系統中的還原度，再決定是否納入正式工作流。\n\n#### 常見陷阱\n\n- 配額耗盡無預警：Starter 方案每月 6 次極易在測試階段耗盡，建議先確認方案等級再制定 PoC 規劃\n- 本地端點依賴桌面應用：本地模式若 Figma 應用關閉，`http://127.0.0.1:3845/mcp` 端點即斷線，建議腳本中加入端點健康檢查\n- 逆向生成的是全新檔案：Code → Figma 方向生成的是全新設計檔，不會修改原始 Figma 稿，組件庫連結與 Auto Layout 設定不會被保留，需手動合併差異\n\n#### 上線檢核清單\n\n- 觀測：工具呼叫次數（追蹤配額消耗速率）、生成程式碼與設計稿的還原度差異、CI 流程中 MCP 連線穩定性\n- 成本：Figma 方案升級費用（Pro/Org 席位）、OpenAI API token 消耗量估算\n- 風險：設計稿資料透過遠端 MCP 傳輸的資安合規（特別是含有 NDA 保護設計資產的場景）、生成程式碼的智慧財產權歸屬確認","#### 競爭版圖\n\n- **直接競品**：GitHub Copilot Workspace（微軟生態，缺乏 Figma 原生整合）、Cursor IDE（有視覺設計稿讀取功能但非雙向）、Vercel v0（文字→UI，無 Figma 可編輯稿輸出）\n- **間接競品**：Locofy、Anima 等 Figma 插件轉碼工具；Builder.io 的視覺→程式碼平台；Gemini CLI（同樣支援 Figma MCP，競爭同一工作流入口）\n\n#### 護城河類型\n\n- **生態護城河**：Figma 擁有設計師社群的高黏著度，OpenAI Codex 控制了 AI 程式碼生成入口；雙方生態的交叉授權形成競品難以單獨複製的組合優勢\n- **資料護城河**：Codex 100 萬週活用戶的實際使用數據，可持續訓練設計↔程式碼雙向轉換模型的精確度，形成飛輪效應\n\n#### 定價策略\n\nFigma MCP 以方案分級限制工具呼叫次數，將 AI 功能綁定高階付費席位，形成向上銷售機制。OpenAI Codex 另按 API token 計費。兩層計費疊加，對企業用戶而言成本仍屬可控，但對個人開發者或 Starter 用戶形成明顯進入門檻，降低了有機傳播的速度。\n\n#### 企業導入阻力\n\n- 需同時持有 Figma 企業方案與 OpenAI API 授權，IT 採購決策鏈較長，評估周期可能達 3-6 個月\n- 設計稿透過遠端 MCP 傳遞涉及資料主權疑慮，金融、醫療等高合規產業需額外進行資安審查\n\n#### 第二序影響\n\n- Figma 插件生態（Locofy、Anima 等）的商業模式受到威脅，MCP 原生整合可能逐步取代付費插件的市場空間\n- 設計師與前端工程師的職責邊界將進一步模糊，「能寫 code 的設計師」或「理解設計系統的全端工程師」需求上升\n\n#### 判決：生態卡位戰成功（設計×程式碼雙入口已被兩強壟斷）\n\nOpenAI 與 Figma 此舉不是在創造新市場，而是在 AI 工作流中搶占設計→程式碼這個高頻接觸點。對 Figma 而言，MCP 整合鞏固了其作為「設計稿唯一事實來源」的地位，並透過配額機制將 AI 功能變現；對 OpenAI 而言，Codex 的應用場景從純程式碼延伸至設計迭代，進一步拉高用戶黏著度。短期內這仍是新鮮整合，但雙向傳送帶一旦被開發者工作流採用，切換成本將大幅提高，護城河效應會隨時間持續加深。",[325,326],"配額設計幾乎把個人用戶排除在外：Starter 方案每月 6 次工具呼叫，意味著大多數獨立開發者與學生根本無法在日常工作中試驗這個工作流，「設計×程式碼民主化」的敘事在定價結構面前顯得空洞。","逆向生成 (Code → Figma) 的實用性存疑：生成的是全新 Figma 檔案而非修改原始稿，所有精心建立的組件庫連結、版本歷史、Auto Layout 設定都會遺失，在有嚴謹設計系統的團隊中，此功能可能製造更多混亂而非節省時間。",[328,332],{"platform":329,"user":330,"quote":331},"HN","CompoundEyes（HN 用戶）","正在把大量無型別的 JS 舊版前端程式碼移植到 Vue + TypeScript，搭配 Figma 設計稿，是高度可設定的 B2B 應用（也就是排列組合超多）。每個人似乎都有自己的一套「系統」。我推薦參考 OpenAI Cookbook 的長執行計畫方案，並把 TDD 做到極致。",{"platform":69,"user":333,"quote":334},"@parhamb","如果你想在 OpenAI Codex 中使用 Figma MCP：1. 前往 ~/.codex 並開啟 config.toml 2. 加入此設定：[mcp_servers.figma] url = \"http://127.0.0.1:3845/mcp\" 3. 執行 codex mcp-server 4. 在 Codex CLI 輸入提示詞。親測有效！#Figma #Codex #MCP",[336,338,340],{"type":77,"text":337},"用 Codex CLI 本地模式接 Figma MCP（`http://127.0.0.1:3845/mcp`），取一個現有 UI 組件試試從 Figma 設計稿生成程式碼，評估在你的設計系統中的元件還原度。",{"type":80,"text":339},"若組件還原度達到 80% 以上，考慮在 PR 流程中加入 Figma MCP 步驟，讓設計稿的改動自動觸發對應程式碼建議，縮短設計→開發的同步週期。",{"type":83,"text":341},"追蹤 Figma 是否調整 MCP 配額方案（特別是 Starter 方案的月限），以及社群對 Code → Figma 逆向生成還原精確度的獨立評測結果出爐後，再決定全面導入時機。",{"category":274,"source":10,"title":343,"subtitle":344,"publishDate":6,"tier1Source":345,"supplementSources":348,"tldr":365,"context":376,"mechanics":377,"benchmark":378,"useCases":379,"engineerLens":388,"businessLens":389,"devilsAdvocate":390,"community":394,"hypeScore":72,"hypeMax":73,"adoptionAdvice":265,"actionItems":411},"anthropics/skills — AI Agent 技能的開放標準生態","Anthropic 將 Agent Skills 開源並制定跨平台規格，GitHub Copilot 已率先支援，社群工具快速湧現",{"name":346,"url":347},"GitHub: anthropics/skills","https://github.com/anthropics/skills",[349,353,357,361],{"name":350,"url":351,"detail":352},"Anthropic Blog: Equipping agents for the real world with Agent Skills","https://claude.com/blog/equipping-agents-for-the-real-world-with-agent-skills","Anthropic 官方介紹 Agent Skills 概念與設計理念，含 2025-12-18 開放標準更新公告",{"name":354,"url":355,"detail":356},"Agent Skills 規格文件","https://agentskills.io/specification","開放標準完整規格，包含 YAML frontmatter 欄位定義與目錄結構說明",{"name":358,"url":359,"detail":360},"GitHub Changelog: Copilot now supports Agent Skills","https://github.blog/changelog/2025-12-18-github-copilot-now-supports-agent-skills/","GitHub Copilot 宣布支援 Agent Skills 及現有 .claude/skills 目錄相容性",{"name":362,"url":363,"detail":364},"The Verge coverage","https://www.theverge.com/ai-artificial-intelligence/800868/anthropic-claude-skills-ai-agents","The Verge 對 Agent Skills 的早期報導，聚焦企業情境客製化價值",{"tagline":366,"points":367},"把 AI Agent 的企業知識包成資料夾，跨 Claude、Copilot 通用",[368,371,374],{"label":369,"text":370},"生態","anthropics/skills 是 Anthropic 主導的開放標準倉庫，每個「技能」是一個含 SKILL.md 的資料夾，分為 Apache-2.0 授權的通用技能與 source-available 的文件技能兩大類，截至 2026-02-25 仍持續維護更新。",{"label":372,"text":373},"整合","GitHub Copilot 於 2025-12-18 宣布支援 Agent Skills，與現有 .claude/skills 目錄完全相容，代表同一套技能資料夾可跨 Claude Code 與 Copilot 複用，打破 AI 工具孤島格局。",{"label":164,"text":375},"建立技能只需一個含 YAML frontmatter 的 SKILL.md，前端設計技能僅 42 行指令即可讓 Agent 具備領域知識；社群已出現桌面管理工具 Skill Studio，技能安裝流程趨近 npm install 的體驗。","AI Agent 的能力上限，長期被「如何讓它理解我們的工作方式」卡住。提示詞可以寫，系統指令可以調，但這些知識散落在各工具的設定頁，換一個 AI 平台就要重來一遍，企業的最佳實踐也難以模組化傳承給整個團隊。\n\n#### 痛點 1：AI 工具的情境知識格式各自為政\n\nClaude 有 CLAUDE.md，Cursor 有 .cursorrules，GitHub Copilot 有 copilot-instructions.md——每個平台都要求開發者用不同格式複製一次領域知識。跨工具複用幾乎不可能，企業投入大量工程時間做的 AI 調整，切換工具後全部歸零，形成嚴重的知識重複建設問題。\n\n#### 痛點 2：團隊 AI 最佳實踐難以結構化共享\n\n即便在同一工具內，個人積累的「有效提示詞」也無法輕易分享給整個團隊。新成員往往需要數週才能摸索出讓 Agent 在特定技術棧上表現良好的指令模式。缺乏標準化格式，讓組織內的 AI 使用知識無法形成可複用的制度資本，資深工程師的隱性經驗也難以傳承。\n\n#### 舊解法：CLAUDE.md 全域設定\n\n過去 Anthropic 提供 CLAUDE.md 讓開發者在專案根目錄放置指令，這確實有效，但本質是平坦的單一檔案，難以按功能模組化，不支援附帶腳本、參考資料或二進位資產的複合結構，更無法跨 AI 工具互通，是解決了個人工作流卻未解決生態孤島的方案。","Agent Skills 規格的核心設計哲學是「漸進式揭露 (progressive disclosure) 」——AI 先讀取輕量的 metadata，確認技能與當前任務相關後才載入完整指令，最後在需要時才拉取外部資源，有效避免浪費寶貴的 context window。\n\n> **名詞解釋**\n> progressive disclosure（漸進式揭露）：一種 UX 與系統設計原則，指資訊按需分層提供，使用者（或 AI）只在需要時才接觸下一層細節，以減少認知負荷或計算成本。\n\n#### 機制 1：SKILL.md 為技能的單一入口\n\n每個技能是一個資料夾，根目錄必須有 SKILL.md。YAML frontmatter 定義兩個必要欄位：`name` 和 `description`，讓 AI 能快速判斷是否啟用此技能。其餘欄位如 `license`、`compatibility`、`metadata` 和實驗性的 `allowed-tools` 均為選填，讓技能作者在不破壞基本規格相容性的前提下擴充附加功能。\n\n#### 機制 2：資料夾結構支援複合資源\n\n技能資料夾除 SKILL.md 外，可包含三類選填子目錄：\n\n- `scripts/`：可執行的自動化腳本\n- `references/`：技能執行時可查閱的靜態文件\n- `assets/`：圖片、範本等二進位資源\n\n這使得「前端設計技能」可以附帶完整的設計規範文件，「部署技能」可以附帶 CI/CD 腳本範本，技能從純指令升級為自包含的工作流程套件。\n\n#### 機制 3：開放標準確保跨平台相容\n\n2025-12-18 Anthropic 將規格發布為開放標準 (agentskills.io) ，同日 GitHub Copilot 宣布相容 `.claude/skills` 目錄。規格層面，技能路徑尚有社群討論 (`.claude/skills/` vs `.agents/skills/`) ，但跨平台相容的方向已明確確立：同一套技能資料夾可被多個 AI 工具載入，無需重複維護。\n\n> **白話比喻**\n> 把 Agent Skills 想成 npm 套件，但裝的不是程式碼而是「工作方式」。寫一次 `SKILL.md` 就像發布一個 package，任何支援此規格的 AI 工具都能 \"install\" 這套領域知識，一次撰寫，多處生效。","",{"recommended":380,"avoid":385},[381,382,383,384],"企業內部技術棧的 AI 最佳實踐標準化——將團隊的 code review 規範、部署流程、命名慣例打包成可版本控管的技能資料夾","多工具 AI 工作流整合——同一套前端設計技能可讓 Claude Code 和 GitHub Copilot 遵循相同的設計系統規範，消除工具切換帶來的行為不一致","新成員 onboarding 加速——將資深工程師的隱性 AI 使用知識編碼為技能，縮短新人摸索有效提示詞模式的學習曲線","開源社群貢獻——在 anthropics/skills 倉庫貢獻垂直領域技能（如特定框架最佳實踐），讓社群整體受益",[386,387],"需要高度動態判斷或即時外部資料的場景——技能是靜態指令集，不適合替代需要即時查詢的 MCP 工具或 API 呼叫","機密或高安全性業務情境——技能資料夾存放於版本控管系統，含敏感業務邏輯的指令需謹慎評估儲存位置與共享範圍","#### 環境需求\n\n建立技能無需額外依賴，只需在專案根目錄建立 `.claude/skills/\u003Cskill-name>/` 資料夾結構。Claude Code 會自動偵測並載入，GitHub Copilot 亦相容此路徑。若要從 anthropics/skills 倉庫安裝現有技能，可使用社群工具 `npx skills add \u003Cskill-name>` 指令，或手動將技能資料夾複製至 `~/.claude/skills/`（全域）或 `./.claude/skills/`（專案層級）。\n\n#### 最小 PoC\n\n```yaml\n# .claude/skills/frontend-design/SKILL.md\n---\nname: frontend-design\ndescription: 前端設計規範，適用於元件開發、CSS 架構決策與無障礙合規審查\n---\n\n## 元件命名\n- 使用 PascalCase 命名 React 元件\n- 容器元件加 Container 後綴\n\n## CSS 架構\n- 採用 CSS Modules，禁止全域樣式污染\n- 色彩變數集中定義於 tokens/colors.css\n\n## 無障礙\n- 互動元件必須有 aria-label 或 aria-labelledby\n```\n\n#### 驗測規劃\n\n建立技能後，在 Claude Code 中觸發相關任務（如「幫我建一個按鈕元件」），觀察 Agent 是否自動遵循技能中的命名與 CSS 規範，無需在提示詞中重複說明。可準備一份刻意違反規範的 code snippet，請 Agent review 並確認它能主動指出問題所在。\n\n#### 常見陷阱\n\n- `description` 欄位過於籠統會導致 Agent 在不相關任務中載入技能，白白消耗 context；建議描述精確到「適用情境」而非「包含內容」\n- 技能指令與 CLAUDE.md 規範衝突時，優先順序行為需實測確認，避免兩套規則互相覆蓋造成行為不穩定\n- `allowed-tools` 欄位目前為實驗性功能，跨平台行為尚未穩定，生產環境暫時不依賴此功能\n- 技能路徑規範尚有 `.claude/skills/` vs `.agents/skills/` 社群爭議，建議持續觀察 agentskills.io 規格更新再做路徑選擇\n\n#### 上線檢核清單\n\n- 觀測：技能是否在正確情境被自動載入；Agent 輸出是否實際反映技能指令而非通用預設行為\n- 成本：單份技能 SKILL.md 建議控制在 500 tokens 以內，避免技能數量過多導致 context 成本失控\n- 風險：確認技能資料夾未意外提交含商業機密的 `references/` 文件；審查 `scripts/` 中的腳本是否有潛在的命令注入風險","#### 競爭版圖\n\n- **直接競品**：Cursor 的 .cursorrules 系統、各家 AI IDE 的私有自訂指令機制（目前均為平台綁定格式）\n- **間接競品**：LangChain 的 prompt templates、Dust.tt 的知識庫配置、企業級 RAG 系統（如 Glean）提供的情境知識注入方案\n\n#### 護城河類型\n\n- **生態護城河**：anthropics/skills 倉庫作為官方技能目錄，社群貢獻的技能累積量形成先發優勢；Andrew Ng 等 AI 教育者為此規格開設課程，大幅提升標準採用率與認可度\n- **工程護城河**：progressive disclosure 的 context 效率設計，使技能格式在長任務中比平坦 CLAUDE.md 更具成本優勢；GitHub Copilot 相容性則打破了「技能綁定 Claude」的採用疑慮\n\n#### 定價策略\n\n規格本身開放免費，anthropics/skills 倉庫中大多數技能採 Apache-2.0 授權可商業使用。文件技能（docx/pdf/pptx/xlsx 處理）採 source-available 而非完全開源，暗示 Anthropic 保留部分商業化空間。企業建立私有技能目錄的技術成本極低（純資料夾結構），但維護情境知識品質所需的人力成本不可低估。\n\n#### 企業導入阻力\n\n- 技能路徑標準尚未完全定案，企業可能顧慮未來規格收斂後的遷移成本\n- 缺乏類似 npm audit 的技能安全審查機制，企業安全團隊可能要求全面審查社群來源技能的指令內容\n- 與現有知識管理系統（Confluence、Notion）的雙向同步路徑尚未成熟，知識更新需要手動維護兩套來源\n\n#### 第二序影響\n\n- 若 Agent Skills 成為業界標準，AI 工具廠商將被迫宣布支援此規格，否則面臨生態孤立風險，這反過來持續強化 Anthropic 的生態話語權\n- 垂直領域技能市集 (Skill Marketplace) 的商業模式可期——類似 VSCode Extension Marketplace，法律合規、金融分析、特定框架等付費技能套件將逐步出現\n\n#### 判決：值得現在跟進（低成本卡位、高槓桿的生態先機）\n\nAgent Skills 的採用成本極低（一個 Markdown 檔案），而標準一旦確立，後進者的整合成本將顯著上升。現在跟進等同於以最小代價參與一個即將成為業界基礎設施的規格制定期，同時積累的技能資產在跨工具互通成熟後將直接轉化為生產力紅利。",[391,392,393],"SKILL.md 本質上是精心格式化的提示詞，與各家 AI 工具現有的自訂指令功能高度重疊，「開放標準」的定位更像是 Anthropic 的生態圈擴張策略，而非解決真實互通技術痛點","文件技能（pdf/docx 等）採 source-available 而非完全開源，規格中商業價值最高的部分仍受 Anthropic 控制，宣稱的跨平台中立性存在根本性矛盾","技能路徑（.claude/skills/ vs .agents/skills／）的標準爭議顯示生態尚未收斂，過早投入企業級整合可能面臨規格變更帶來的遷移成本，現在觀望或許更務實",[395,398,401,404,407],{"platform":69,"user":396,"quote":397},"@AndrewYNg（AI 教育者，DeepLearning.AI 與 Coursera 創辦人）","重要新課程：與 Anthropic 合作的 Agent Skills，由 @AnthropicAI 開發並由 @eschoppik 教授！技能以指令資料夾的形式構建，為 Agent 提供按需知識與工作流程。這門短課將教你如何按照最佳實踐來建立它們。",{"platform":329,"user":399,"quote":400},"onmyway133（HN 用戶）","我最近大量使用 Claude Code，想要更輕鬆地探索和管理技能，所以我建了 Skill Studio——一款免費的 macOS 開源桌面應用。功能包括：瀏覽社群技能倉庫（Anthropic、Vercel 等）、完整 Markdown 渲染的技能文件預覽、一鍵安裝（透過 npx skills add 或複製到 ~/.claude/skills／）、新增自訂 GitHub 倉庫、依名稱或安裝狀態搜尋篩選、加入我的最愛。",{"platform":69,"user":402,"quote":403},"@nityeshaga（X 用戶）","這真的太棒了。Anthropic 不僅知道如何打造最好的模型，更懂得如何最佳化地使用它們。看看這個前端設計技能——它只是一個 42 行指令的單一檔案，讀起來就像前端 lead 為團隊寫的那種備忘錄。",{"platform":329,"user":405,"quote":406},"westurner（HN 用戶）",".claude/skills/ 是 agentskills 的原始路徑，Anthropic Claude 創建並在 agentskills.io 開放規格。.agents/skills/ 是否較少工具綁定？skill.sh README 列出了他們工具支援的多個 agent skills 路徑，但 agentskills.io 規格本身並未明確說明。如果規格能指定通用的家目錄相對路徑和倉庫根相對路徑，對整個生態會更好。",{"platform":408,"user":409,"quote":410},"GitHub anthropics/skills","rdu（GitHub 用戶）","我遇到了完全相同的問題。我所有的技能突然消失了——即使我只使用過標準內建技能，從未自訂過任何東西。現在每次嘗試進入技能區塊都會收到「找不到」的錯誤。查看瀏覽器網路日誌，list-skills 請求回傳的是 not_found_error，訊息顯示「Not found」。",[412,414,416],{"type":77,"text":413},"在現有專案建立 .claude/skills/ 資料夾，從 anthropics/skills 倉庫複製 frontend-design 或 git-commit 技能，觀察 Claude Code 在相關任務中的行為變化，感受「零提示詞重複」的體驗差異。",{"type":80,"text":415},"將團隊最常在提示詞中重複說明的規範（命名慣例、部署流程、程式碼審查標準）打包成一份 SKILL.md，測試能否顯著減少每次對話中的背景說明量，量化 context token 節省效益。",{"type":83,"text":417},"追蹤 agentskills.io 規格更新，關注 .claude/skills/ 與 .agents/skills/ 路徑標準是否收斂，以及 Cursor、Windsurf 等主流 AI IDE 是否陸續宣布支援，作為企業大規模導入的決策時機訊號。",[419,462,483,524,555,588,622,642,674,698],{"category":131,"source":11,"title":420,"publishDate":6,"tier1Source":421,"supplementSources":424,"coreInfo":437,"engineerView":438,"businessView":439,"viewALabel":440,"viewBLabel":441,"bench":442,"communityQuotes":443,"verdict":460,"impact":461},"Nano Banana 2：以 Flash 速度達到 Pro 品質的圖像生成模型",{"name":422,"url":423},"Google AI Blog","https://blog.google/innovation-and-ai/technology/ai/nano-banana-2/",[425,429,433],{"name":426,"url":427,"detail":428},"DeepMind 模型頁面：Gemini 3.1 Flash Image","https://deepmind.google/models/gemini-image/flash/","官方模型規格與限制說明",{"name":430,"url":431,"detail":432},"Google AI for Developers：圖像生成文件","https://ai.google.dev/gemini-api/docs/image-generation","API 名稱對應與使用範例",{"name":434,"url":435,"detail":436},"The Verge 報導","https://www.theverge.com/tech/885275/google-nano-banana-2-ai-image-model-gemini-launch","第三方媒體報導","#### 核心升級：以 Flash 速度達到 Pro 品質\n\nGoogle 於 2026 年 2 月 26 日發布 Nano Banana 2（API 識別碼：`gemini-3.1-flash-image-preview`），定位為「Flash 速度、Pro 品質」的圖像生成模型，已同步在 Gemini 應用程式、Google Search、AI Studio／API、Vertex AI 及 Google Ads 全面推出。主要能力包括：\n\n- 即時網路搜尋與圖片搜尋接地，生成內容可反映最新世界知識\n- 精確文字渲染與多語翻譯\n- 最多支援 5 個角色、14 個物件的主體一致性\n- 輸出解析度從 512px 至 4K，適合量產場景\n\n> **名詞解釋**\n> Grounding（接地）：讓模型在生成時查詢外部真實資料（如 Google 搜尋），而非僅依賴訓練時的靜態知識。\n\n#### 溯源機制：SynthID 與 C2PA\n\n所有生成圖像均內嵌 SynthID 不可見浮水印，Google 表示自 2025 年 11 月以來已被驗證逾 2,000 萬次；C2PA 內容憑證功能也即將登陸 Gemini 應用程式。已知限制包含小字渲染不穩定、角色一致性在長工作流中可能漂移，以及偶發性逾時問題。","模型支援多模態輸入，context window 達 100 萬 token，可接受最多 14 張參考圖像進行多圖工作流。目前仍為 preview 狀態，建議在生產環境加入重試機制與輸出品質驗證邏輯。SynthID 浮水印可透過 [google-deepmind/synthid-text](https://github.com/google-deepmind/synthid-text) 驗證；C2PA 介接尚未上線，溯源暫以 SynthID API 為主。","Nano Banana 2 在 Artificial Analysis Image Arena 文字生圖評測中排名第一，定價約為 Nano Banana Pro 的一半，大幅降低高品質圖像生成的成本門檻。Google Ads 與 Google Vids 的整合意味著廣告創意與影片製作場景已可直接落地。SynthID 加 C2PA 溯源機制有助於企業提前因應 AI 生成內容標示的法規要求。","工程師視角","商業視角","#### 效能基準\n\n- GenAI-Bench Overall Preference：1079.0 ± 7.0（含 Thinking、文字搜尋、圖片搜尋三項增強變體）\n- GenAI-Bench Visual Quality：1140.0 ± 6.0\n- Artificial Analysis Image Arena 文字生圖排名：**第 1 名**（定價約為 Nano Banana Pro 的一半）",[444,447,451,454,457],{"platform":57,"user":445,"quote":446},"zorked（HN 用戶）","那些還未成名的藝術家，目前可以靠插畫師、佈景設計師、駐場音樂人等工作維生。這些職位將隨著生成工具進步而逐漸消失，從事藝術的風險將愈來愈高。藝術最終將再度成為富人的專屬——就像歷史上那樣——與大眾文化之間的落差也將持續擴大。",{"platform":448,"user":449,"quote":450},"Reddit r/singularity","u/THE--GRINCH(Reddit 82 upvotes)","圖像生成問題愈來愈接近被徹底解決了。",{"platform":448,"user":452,"quote":453},"u/bentendo93(Reddit 70 upvotes)","我拿以前效果很差的場景來測試（幫自家翻新裝潢），結果好得驚人，讓我當下就想掏錢開工了。",{"platform":69,"user":455,"quote":456},"@artificialanlys（AI 評測社群帳號）","Google 的 Nano Banana 2(Gemini 3.1 Flash Image Preview) 在 Artificial Analysis Image Arena 文字生圖評測中登上第一名，而定價只有 Nano Banana Pro 的一半！",{"platform":57,"user":458,"quote":459},"tlh（HN 用戶）","AI 藝術在許多圈子裡現在肯定被視為不酷。不過我在想，過去有沒有其他創新在早期也被認為不酷，但現在大家完全接受了？這種看法的轉變，究竟只是世代更迭或時間流逝的問題嗎？","追","Flash 速度加搜尋接地讓圖像 API 正式進入量產門檻，以最低成本拿下圖像生成榜首，適合立即整合進廣告創意與內容製作流程。",{"category":463,"source":9,"title":464,"publishDate":6,"tier1Source":465,"supplementSources":468,"coreInfo":473,"engineerView":474,"businessView":475,"viewALabel":476,"viewBLabel":477,"bench":378,"communityQuotes":478,"verdict":74,"impact":482},"funding","Mistral AI 與埃森哲簽署多年策略合作協議",{"name":466,"url":467},"TechCrunch","https://techcrunch.com/2026/02/26/mistral-ai-inks-a-deal-with-global-consulting-giant-accenture/",[469],{"name":470,"url":471,"detail":472},"Accenture Newsroom","https://newsroom.accenture.com/news/2026/accenture-and-mistral-ai-accelerate-enterprise-reinvention-with-scalable-ai-that-delivers-strategic-autonomy-for-customers","Accenture 官方新聞稿","#### 合作重點：主權 AI 的企業交付\n\nAccenture 與 Mistral AI 於 2026 年 2 月 26 日宣布多年策略合作，目標是在歐洲及全球為企業大規模部署進階 AI 解決方案。雙方將聯合開發企業 AI 方案，Accenture 亦成為 Mistral 客戶並在內部導入 Mistral AI Studio。\n\n#### 架構：多押注策略下的主控優先\n\n合作特別強調「主權 AI」定位，針對歐洲資料在地化與監管需求提供安全、大規模的合規部署。交付模型結合 Mistral 的模型能力與 Accenture 的企業架構、治理及規模化專長，並含客戶培訓認證、微調與運維支援。值得注意的是，Accenture 同期亦與 OpenAI(Frontier Alliances) 及 Anthropic 建立多年合作，採「多押注」而非獨家策略。財務條款與合約期間均未公開。\n\n> **名詞解釋**\n> 主權 AI(Sovereign AI) ：資料與模型運算保留在特定地理區域或受特定司法管轄，符合當地法規要求的 AI 部署方式。","Mistral 模型從開源社群延伸至企業合規交付，獲大型系統整合商背書其生產就緒度。然而 Mistral AI Studio 的具體整合細節（API 規格、SLA、微調流程）尚未公開，需等後續技術文件。此合作對有歐洲合規或資料主權需求的工程師具有參考價值，但在評估實際採用前應等待更多技術規格揭露。","Accenture 同時持有 OpenAI、Anthropic 與 Mistral 三方協議，形成「AI 顧問多元組合」策略以避免供應商鎖定。Mistral 藉此獲得全球最大顧問公司之一的企業銷售通路，有助打入歐洲主權 AI 市場。財務條款未公開且合作非獨家，深度有待後續訂單驗證；對歐洲企業客戶而言，此模式提供了符合在地監管要求的 AI 部署選項。","技術實力評估","市場與投資觀點",[479],{"platform":69,"user":480,"quote":481},"@faustocoppi60(Mihai Simion)","幾小時後：Mistral 崩潰了，根本無法在 AI 競賽中起跑。😝 不得不說，這個合作規模真的挺大的。這就是應該與美國人和中國人一較高下的歐洲 AI，對吧？祝好運！","Accenture 多押注策略加速確立歐洲主權 AI 市場格局，Mistral 企業通路大幅擴展，但合作實際深度尚待後續訂單驗證。",{"category":484,"source":12,"title":485,"publishDate":6,"tier1Source":486,"supplementSources":489,"coreInfo":502,"engineerView":503,"businessView":504,"viewALabel":505,"viewBLabel":506,"bench":378,"communityQuotes":507,"verdict":74,"impact":523},"discourse","OpenAI 如何競爭？四大戰略困境與應對",{"name":487,"url":488},"Benedict Evans","https://www.ben-evans.com/benedictevans/2026/2/19/how-will-openai-compete-nkg2x",[490,493,496,499],{"name":491,"url":492},"Testing ads in ChatGPT","https://openai.com/index/testing-ads-in-chatgpt/",{"name":494,"url":495},"Introducing ChatGPT Go","https://openai.com/index/introducing-chatgpt-go/",{"name":497,"url":498},"Announcing The Stargate Project","https://openai.com/index/announcing-the-stargate-project/",{"name":500,"url":501},"DeepSeek-R1 paper (arXiv)","https://arxiv.org/abs/2501.12948","#### OpenAI 的四大戰略困境\n\nBenedict Evans 在 2026 年 2 月分析指出，OpenAI 面臨四個核心挑戰：**模型層護城河薄弱**（競爭者技術可快速追上）、**日常使用黏著度不足**（ChatGPT 尚未成為高頻生活習慣）、**極端資本支出壓力**（Stargate 計畫承諾超過 4,500 億美元基礎設施投資）、以及**產品掌控力不確定**（應用層競爭激烈）。與此同時，DeepSeek-R1 的開源揭示了另一威脅——以更低成本複製強推理能力，進一步壓縮模型層的差異化空間。\n\n#### OpenAI 的應對動作\n\n面對上述壓力，OpenAI 採取多管齊下策略：\n\n- **低價方案**：推出每月 8 美元的 ChatGPT Go，覆蓋 171 個國家\n- **廣告測試**：在 Free 和 Go 方案對登入用戶開放廣告，付費方案維持無廣告\n- **垂直整合**：ChatGPT Search（全用戶開放）與 Operator 代理模式（整合進 ChatGPT）\n- **基礎設施卡位**：Stargate 計畫規劃超過 8 GW 算力、逾 4,500 億美元投資\n\n目前基本面數據仍強：週活躍用戶超過 4 億、年化營收達 100 億美元、估值 5,000 億美元。","DeepSeek-R1 的開源（671B 參數、37B 激活）直接挑戰「唯 OpenAI 最強」的假設。API 選型邏輯正在轉變：推理成本、延遲與模型可替換性比品牌更關鍵。Operator 代理框架若成熟，可能成為新的整合卡點；但 search-at-inference 仍有成本與速度代價，增量學習問題尚未解決，依賴 ChatGPT 作為知識來源仍存在資訊時效風險。","廣告引入意味 OpenAI 正式走向「免費增值＋廣告」雙軌變現，4 億不付費週活用戶成為潛在廣告庫存。Stargate 的巨額基礎設施投資構築成本護城河，但也放大財務槓桿風險。若廣告收入無法快速規模化，加上開源模型持續壓低 API 定價，OpenAI 的 5,000 億美元估值將面臨壓力測試。","實務觀點","產業結構影響",[508,511,514,517,520],{"platform":57,"user":509,"quote":510},"reducesuffering(Hacker News)","你沒有考慮到二階後設系統。ASI 不只是一個 LLM 在對話中回覆你，而是資料中心裡數百萬個 LLM，同時與數百萬人互動。",{"platform":57,"user":512,"quote":513},"barrkel(Hacker News)","搜尋引擎比推理成本更高、速度也更慢。增量學習不發生災難性遺忘的問題仍未解決。我最近用 ChatGPT 安裝 Gerrit 和 jujutsu 時非常沮喪，它一直給我過時的資訊，我不得不一再叫它去搜尋。",{"platform":57,"user":515,"quote":516},"adventured(Hacker News)","OpenAI 坐擁一個價值超過千億美元的廣告收入商機等著實現。那 95% 不付費的用戶即將開始付出一些代價。",{"platform":57,"user":518,"quote":519},"amelius(Hacker News)","當神經元數量達到一定程度後，AI 不會變得明顯更聰明，只會更博學（也更昂貴）。對大多數用戶而言，知識部分可以外包給搜尋引擎來降低成本。",{"platform":57,"user":521,"quote":522},"kbelder(Hacker News)","他們需要做某種共享對話功能——能夠開始一個對話串後邀請其他 ChatGPT 用戶加入。這能增加網路效應和轉換成本。","OpenAI 廣告化與低價分層策略正重塑 AI 產品競爭格局，開發者與企業均需重新評估 API 供應商選型與長期成本結構。",{"category":131,"source":9,"title":525,"publishDate":6,"tier1Source":526,"supplementSources":528,"coreInfo":534,"engineerView":535,"businessView":536,"viewALabel":440,"viewBLabel":441,"bench":537,"communityQuotes":538,"verdict":460,"impact":554},"Qwen3.5 122B 三張 3090 本地部署，MoE 架構讓大模型跑進消費級硬體",{"name":135,"url":527},"https://www.reddit.com/r/LocalLLaMA/comments/1rf2ulo/qwen35_122b_in_72gb_vram_3x3090_is_the_best_model/",[529,532],{"name":530,"url":531},"Qwen3.5-122B-A10B Model Card (Hugging Face)","https://huggingface.co/Qwen/Qwen3.5-122B-A10B",{"name":533,"url":140},"Qwen3.5 官方公告 (Alibaba Cloud)","#### 122B 總參數、10B 啟動：MoE 讓大模型進入消費級\n\nAlibaba Cloud 推出 Qwen3.5 中型系列，旗艦為 Qwen3.5-122B-A10B——122B 總參數中每次推論僅啟動 10B，共設 256 個專家 (8 routed + 1 shared) ，原生支援 262k tokens 上下文，最高可擴展至約 100 萬 tokens。\n\n> **名詞解釋**\n> MoE(Mixture of Experts) ：模型包含多個「專家」子網路，每次推論只啟動其中少數幾個，使超大模型能以較少記憶體和算力運行。\n\n#### 實測：72GB VRAM 三張 3090 就夠了\n\n社群用 3 張 RTX 3090（共 72GB VRAM）成功部署 Q3_K 量化版，達到約 25 tok/s、可跑 120k 上下文。模型預設開啟思考模式，連簡單指令也會展開推理鏈；社群建議調整採樣參數（temperature 0.6、top-k 20、top-p 0.8）來緩解過度思考。","72GB VRAM（3x RTX 3090 或單張 RTX 5090）可部署 Q3/Q4 量化版，vLLM 與 SGLang 均有官方範例。目前 4-bit Unsloth 量化版疑有 bug，建議先改用官方 GGUF 或 Q4_K_XL。思考模式適合複雜任務，但對簡單指令須在呼叫時手動關閉，否則首 token 延遲會大幅增加。","Qwen3.5-122B 以免費開放權重提供接近閉源旗艦的效能，讓中小型 AI 產品有了低成本私有部署選項，201 種語言支援也有利多語系場景。需注意預設思考模式會推高延遲與推論成本，且 Alibaba 出品涉及地緣政治背景，企業採購前合規評估不可省略。","#### 社群實測推論速度\n\n- Q3_K（3x RTX 3090，72GB VRAM）：~25 tok/s，最大上下文約 120k\n- Q4_K_XL（RTX 5090 + Ryzen 9 9950X3D，128GB DDR5）：34–36 tok/s，最大上下文 256k\n- Q8_K_XL（同規格）：16–18 tok/s，最大上下文 256k",[539,542,545,548,551],{"platform":135,"user":540,"quote":541},"u/mossy_troll_84（Reddit 用戶）","我用 Qwen3.5-122B-A10B-UD-Q4_K_XL 可以跑到 34–36 tok/sec，Q8_K_XL 則是 16–18 tok/sec，最大上下文均 256K。配置：Ryzen 9 9950X3D + RTX 5090 + 128GB DDR5 5600，系統為 Cachy OS Linux。",{"platform":135,"user":543,"quote":544},"u/cershrna（Reddit 用戶）","這個模型不錯，但這整個系列都很喜歡過度思考，就連「Hi」這種簡單提示詞也會想很久。",{"platform":135,"user":546,"quote":547},"u/redditrasberry（Reddit 用戶）","洗車測試並不像大家說的那麼有意義。它是把模型丟進訓練集裡出現頻率很高的場景，利用模型傾向重複那些範例邏輯的偏差來設陷阱。測試推理能否克服這種偏差是有價值的，但說它「證明」模型很笨，實在是言過其實了。",{"platform":135,"user":549,"quote":550},"u/NoahFect（Reddit 用戶）","其他討論串有人說 4-bit Unsloth 量化版有些問題，所以可能還有進步空間。目前這個模型已經很令人印象深刻，尤其是在一連串雷聲大雨點小的發布之後。",{"platform":69,"user":552,"quote":553},"@UnslothAI（Unsloth AI，開源 LLM 量化團隊）","現在可以運行新的 Qwen3.5 中型模型了！Qwen3.5 35B-A3B（MoE，僅需 24GB RAM）、Qwen3.5 27B（dense，18GB）、Qwen3.5 122B-A10B（MoE，70GB）。這些多模態混合推理 LLM 是同尺寸中表現最佳的，GGUF 量化版均已提供下載。","首個能在三張消費級 GPU(72GB VRAM) 流暢部署的 100B+ 開源 MoE 模型，大幅降低高效能本地推論門檻，量化生態正快速跟進中。",{"category":131,"source":11,"title":556,"publishDate":6,"tier1Source":557,"supplementSources":559,"coreInfo":568,"engineerView":569,"businessView":570,"viewALabel":440,"viewBLabel":441,"bench":378,"communityQuotes":571,"verdict":460,"impact":587},"Google Translate 新增 AI 情境輔助：Alternatives、Understand、Ask 三功能上線",{"name":212,"url":558},"https://blog.google/products-and-platforms/products/translate/translation-context-ai-update/",[560,564],{"name":561,"url":562,"detail":563},"Android Authority","https://www.androidauthority.com/google-translate-alternative-phrases-3644783/","功能細節報導",{"name":565,"url":566,"detail":567},"Google Blog（Gemini 翻譯升級）","https://blog.google/products-and-platforms/products/search/gemini-capabilities-translation-upgrades/","2025 年 12 月 Gemini 整合背景","#### AI 驅動的三大情境功能\n\nGoogle Translate 於 2026 年 2 月 27 日推出 Gemini 加持的情境輔助功能，專攻慣用語、口語等字面翻譯常失準的場景。三項功能各有分工：\n\n- **Alternatives**：提供多種翻譯候選詞，並附上各用語適合的時機與語境說明\n- **Understand**：生成語氣與語境解釋（例如正式與非正式語體的差異）\n- **Ask**：允許追問特定情境、國家或方言的具體用法\n\n#### 推出範圍與背景\n\n目前已在美國與印度的 Android／iOS 先行上線，網頁版即將跟進。技術基礎來自 Gemini 的多語言能力；2025 年 12 月的更新同步帶來耳機實況語音對語音翻譯測試版，支援 70 種以上語言。","Gemini 整合讓 Google Translate 從單純字串對映進化為具備語境推理的翻譯系統。**Ask** 功能本質上是以翻譯為入口的對話式 AI 介面——值得關注的是 Google 如何將 Gemini 多輪對話能力嵌入既有產品流程，以及未來是否開放 API 讓第三方存取這些情境功能。","Google Translate 每月處理約 1 兆次翻譯，此次升級強化跨語言溝通準確度，對跨境電商、本地化團隊與多語言客服具直接效益。Gemini 整合鞏固了 Google 在消費者翻譯市場的護城河，同時向 DeepL、ChatGPT 等競爭者施壓。",[572,575,578,581,584],{"platform":69,"user":573,"quote":574},"@sundarpichai(Google CEO)","每個月，人們透過 Google 進行約 1 兆次翻譯。今天，我們在 Google 翻譯 app 中推出全新 AI 驅動的即時翻譯體驗，以及協助練習新語言的測試版功能。現已在 iOS 和 Android 上線。",{"platform":329,"user":576,"quote":577},"extesy（HN 用戶）","Google 翻譯現在使用 Gemini，可以在進階 (AI) 模式和傳統模式之間切換。",{"platform":69,"user":579,"quote":580},"@MarioNawfal（科技評論員）","GOOGLE 翻譯因 AI 與語言課程全面升級。Google 翻譯新增了 110 種語言，目前支援超過 243 種語言，覆蓋逾 6 億額外使用者。App 現有兩種模式：快速模式適合即時查詢，進階模式則提供更聰明、具情境感知的 AI 翻譯。",{"platform":329,"user":582,"quote":583},"bogdan（HN 用戶）","Google 翻譯的品質遠不及 AI 翻譯工具。",{"platform":329,"user":585,"quote":586},"WhereIsTheTruth（HN 用戶）","並非所有人都以英語為母語——大多數人過去依賴 Google 翻譯，現在則轉向 AI 工具。只要是用來表達自己的想法而非用於垃圾訊息或機器人行為，這並沒有什麼問題。","Gemini 情境功能讓 Google Translate 升級為語境顧問，以免費方式衝擊 DeepL 等付費翻譯服務的差異化優勢。",{"category":131,"source":11,"title":589,"publishDate":6,"tier1Source":590,"supplementSources":592,"coreInfo":601,"engineerView":602,"businessView":603,"viewALabel":440,"viewBLabel":441,"bench":604,"communityQuotes":605,"verdict":460,"impact":621},"Nano Banana 2：以 Flash 速度達旗艦畫質的圖像生成模型",{"name":212,"url":591},"https://blog.google/innovation-and-ai/technology/developers-tools/build-with-nano-banana-2/",[593,596,599],{"name":594,"url":595},"Gemini 3.1 Flash Image Preview 文件","https://ai.google.dev/gemini-api/docs/models/gemini-3.1-flash-image-preview",{"name":597,"url":598},"Gemini 開發者 API 定價","https://ai.google.dev/gemini-api/docs/pricing",{"name":294,"url":600},"https://techcrunch.com/2026/02/26/google-launches-nano-banana-2-model-with-faster-image-generation/","#### 模型規格與能力\n\nGoogle 發布 Nano Banana 2（模型 ID：`gemini-3.1-flash-image-preview`），定位為「Flash 等級速度搭配旗艦畫質」的圖像生成暨編輯模型。支援文字與圖片／PDF 混合輸入，輸出同時涵蓋圖像與文字，上下文視窗為 131,072 輸入 token、32,768 輸出 token。\n\n新功能包括：\n\n- 輸出解析度四檔：0.5K、1K、2K、4K\n- 新增極端長寬比：1：4、4：1、1：8、8：1\n- 改善主體一致性、長寬比控制與多語言文字渲染\n\nPreview 版**不支援**：函式呼叫、快取、Live API、URL context、程式碼執行。\n\n#### 溯源機制\n\n內建雙重溯源：SynthID 浮水印（Gemini 內已驗證逾 2,000 萬次）與 C2PA 內容憑證，符合廣告平台的合規需求。\n\n> **名詞解釋**\n> C2PA(Coalition for Content Provenance and Authenticity) ：業界標準，將創作工具與修改紀錄嵌入圖像 metadata，讓任何人可驗證圖像來源。","呼叫方式與既有 Gemini 多模態 API 相同，新增 `responseModalities: [\"IMAGE\", \"TEXT\"]` 即可啟用圖像輸出。Preview 限制明確：函式呼叫與快取尚不支援，但 Batch API 可用，適合高量非同步任務。定價按 token 計費——1K 圖像約 $0.067，比 Nano Banana Pro 便宜約 50%，高頻生成場景 CP 值顯著。","Nano Banana 2 在 Artificial Analysis Image Arena 文字生圖評測奪得第一，定價僅為 Pro 版一半。部署範圍已涵蓋 Google Ads、Flow、Workspace 及 141 個國家的 Gemini Search／Lens，廣告主與媒體製作方可直接在現有 Google 服務中使用，毋須額外整合。Preview 限制（無函式呼叫）須納入產品路線圖評估。","#### 效能與定價基準\n\n- Artificial Analysis Image Arena 文字生圖：第 1 名 (2026-02-26)\n- Nano Banana 2(1K) ：$0.067 / 張\n- Nano Banana 2(4K) ：$0.151 / 張\n- Nano Banana Pro(1K/2K) ：$0.134 / 張（NB2 約為 Pro 的 50%）\n- 原版 Nano Banana（最高 1K）：$0.039 / 張",[606,609,612,615,618],{"platform":69,"user":607,"quote":608},"@artificialanlys（AI 評測分析服務）","Google 的 Nano Banana 2(Gemini 3.1 Flash Image Preview) 在 Artificial Analysis Image Arena 文字生圖排行奪得第一，定價僅為 Nano Banana Pro 的一半！Nano Banana 2 是 @GoogleDeepMind 最新的 Flash 等級圖像模型，接替初代 Nano Banana。",{"platform":69,"user":610,"quote":611},"@levelsio（Photo AI 及 Nomad List 創辦人）","✨ Nano Banana 2 現已上線 📸 Photo AI。這是圖像模型的真正突破，因為它終於實現了高度相似性——也就是 Google 所說的主體一致性。對我來說，這意味著生成的照片會真的像你或你訓練的模型，而不只是「有點像」。",{"platform":57,"user":613,"quote":614},"shostack（HN 用戶）","定價變化很有趣。我想知道他們是否會在某個時間點下架較便宜的舊模型以提升利潤。原版 Nano Banana：每張 $0.039；Nano Banana 2(1K) ：$0.067、4K：$0.151；Nano Banana Pro(1K/2K) ：$0.134。以最常見的 1K 解析度而言，NB2 約為舊版的 72%……",{"platform":448,"user":616,"quote":617},"u/THE--GRINCH（Reddit r/singularity 用戶，89 upvotes）","越來越接近「圖像生成已被攻克」的那一天了。",{"platform":448,"user":619,"quote":620},"u/bentendo93（Reddit r/singularity 用戶，70 upvotes）","哇，我用它測試之前效果很差的任務（幫我的房子做裝修規劃 lol），效果超好。好到讓我現在就想砸錢裝修了。","已可直接透過 Gemini API 呼叫，以 Pro 一半的價格拿下評測第一，適合圖像生成、廣告創意及電商產品圖等高量場景立即採用。",{"category":16,"source":12,"title":623,"publishDate":6,"tier1Source":624,"supplementSources":627,"coreInfo":634,"engineerView":635,"businessView":636,"viewALabel":637,"viewBLabel":638,"bench":639,"communityQuotes":640,"verdict":74,"impact":641},"OpenAI × PNNL 合作推出 DraftNEPABench，聯邦環評文書起草時間縮短 15%",{"name":625,"url":626},"OpenAI","https://openai.com/index/pacific-northwest-national-laboratory/",[628,631],{"name":629,"url":630},"PNNL PermitAI 新聞稿","https://www.pnnl.gov/news-media/permitai-ushers-new-era-faster-better-federal-permitting",{"name":632,"url":633},"pnnl/PermitAI GitHub","https://github.com/pnnl/PermitAI","#### OpenAI × PNNL：用 AI 加速聯邦環評文書\n\nOpenAI 與美國能源部下屬的太平洋西北國家實驗室 (PNNL) 宣布合作，發布 DraftNEPABench——首個專為 NEPA 文件起草設計的評測基準。評測涵蓋 18 個聯邦機構的文件段落，由 19 位領域專家對 102 項任務以 1–5 分制評分（結構、清晰度、準確性、引用）。\n\n> **名詞解釋**\n> NEPA（美國國家環境政策法）要求聯邦機構在批准重大建設或能源專案前，必須完成環境影響評估文件，程序複雜且動輒耗費數年。\n\n#### 技術架構與初步成果\n\n合作採用 Codex CLI 編碼代理工作流程，搭配推理模型（含 GPT-5）進行長文件合成與結構化起草，每個子章節可節省 1–5 小時，整體起草時間估計縮短約 15%。PNNL 的 PermitAI 計畫另包含 MAPLE 評測框架，支援 Azure OpenAI、AWS Bedrock、Google Vertex AI 及本地 HuggingFace 模型，資料庫已擴展至約 12 萬份文件。","MAPLE 框架已開源 (`pnnl/PermitAI`) ，支援 no-context、PDF、RAG、gold-context 四種評測模式，可接入主流雲端 LLM 服務。若需整合 NEPA 自動起草流程，可從 `evaluation` 模組切入，以 NEPAQuAD 問答集（1,590 題）驗收模型效果。需注意最長文件近 900 頁（逾 60 萬 tokens），對 context window 與推理成本有顯著壓力。","NEPA 審查是能源、基礎設施、礦業專案的主要許可瓶頸，配合白宮「21 世紀許可技術更新」行政令，聯邦 AI 採購需求正在成形。15% 起草時間縮短雖屬初步，但 OpenAI 正式切入政府合規工作流是重要訊號——對需與聯邦機構互動的企業或法律顧問，追蹤 PermitAI 生態系成熟度是值得的戰略佈局。","合規實作影響","企業風險與成本","#### DraftNEPABench 評測數據\n\n- 任務數：102 項（來自 18 個聯邦機構文件段落）\n- 評分維度：結構、清晰度、準確性、引用（1–5 分制）\n- 評測專家：19 位領域專家\n- 每子章節節省：1–5 小時\n- 整體起草時間縮短：約 15%\n- NEPA-Bench 條目：逾 10,000 條\n- NEPATEC 2.0 資料庫：約 120,000 份文件（60+ 機構）",[],"NEPA 環評文書自動起草進入基準測試階段，為聯邦機構 AI 採購提供量化依據，能源與基礎設施業者的許可流程長期將受惠。",{"category":131,"source":11,"title":643,"publishDate":6,"tier1Source":644,"supplementSources":646,"coreInfo":655,"engineerView":656,"businessView":657,"viewALabel":440,"viewBLabel":441,"bench":658,"communityQuotes":659,"verdict":672,"impact":673},"更智慧的 Android：Galaxy S26 首搭 Gemini 代理任務與裝置端詐騙偵測",{"name":212,"url":645},"https://blog.google/products-and-platforms/platforms/android/samsung-unpacked-2026/",[647,651],{"name":648,"url":649,"detail":650},"Google Security Blog","https://security.googleblog.com/2026/02/strengthening-android-lead-in-scam-protection.html","裝置端詐騙偵測技術細節",{"name":652,"url":653,"detail":654},"Samsung Newsroom","https://news.samsung.com/global/galaxy-unpacked-2026-highlights-from-galaxy-unpacked-the-beginning-of-truly-agentic-ai","Galaxy Unpacked 2026 發布摘要","#### Gemini 代理流程：有監督的多步驟任務\n\nGalaxy S26 系列首發 Gemini 任務處理功能，目前以 Beta 形式在 Gemini 應用程式推出，初期支援美國與韓國，適用類別為餐飲外送、超市購物與叫車服務。長按電源鍵呼叫 Gemini，即可口頭下達如「幫我重新訂上次的餐點」或「叫一台車回家」，Gemini 會自動跨應用程式完成多步驟操作。\n\n> **白話比喻**\n> 就像交代助理同時訂午餐和叫車，助理自行完成所有步驟，你只需在旁確認。\n\n設計強調**可監督性**：任務進度可透過通知欄即時追蹤，用戶隨時可中斷或停止，手機在執行期間仍可正常使用。\n\n#### 裝置端詐騙偵測與硬體升級\n\nS26 詐騙電話偵測由裝置端 Gemini 驅動，通話內容不上傳雲端，預設關閉，並排除聯絡人名單中的號碼，偵測到可疑話術時發出音訊與震動警示。硬體方面，S26 Ultra NPU 效能較前代提升最多 39%、CPU 提升 19%，為本地端 AI 推論提供更強算力基礎。Circle to Search 則新增多物件辨識與虛擬試穿功能。","Gemini 代理流程採「有監督的自動化」架構，透過通知欄公開任務狀態並允許隨時中斷——這是在安全性與便利性之間的刻意取捨。詐騙偵測完全在裝置端處理 (on-device inference) ，隱私邊界由硬體層把關，NPU 升級直接影響本地推論延遲。\n\n目前 Beta 版透過標準 Android Intent 整合三類應用，開發者短期無需修改現有 App。但隨著生態擴展，若要獲得最佳整合效果，開發者需主動適配 Gemini 任務流程的 API 介面。","三星與 Google 深化整合，在 Apple Siri 升級持續延誤之際搶佔「實用 AI 手機」定位，讓手機從查詢工具升級為代理執行者，對訂餐、叫車等高頻場景的用戶黏著度有直接貢獻。\n\n主要風險在於代理功能的失敗率——多步驟任務若中途失敗或誤操作，信任感將快速瓦解。Beta 階段限縮在結構化場景是合理的風險控管，後續擴展速度將決定競爭優勢能否持續。","#### 硬體效能提升（S26 Ultra vs. 前代）\n\n- NPU：提升最多 39%\n- CPU：提升最多 19%",[660,663,666,669],{"platform":448,"user":661,"quote":662},"u/Ilm03(Reddit 79 upvotes)","在手機裡預載 3 個 LLM 服務感覺有點過頭，但好吧……",{"platform":448,"user":664,"quote":665},"u/Embarrassed-Nose2526(Reddit 42 upvotes)","三星手機上的臃腫軟體已經夠多了，根本不需要再跑 3 個不同的 LLM。難怪 iPhone 這麼受歡迎，軟體更精簡的 Google Pixel 也因此成為成長最快的 Android 品牌。",{"platform":448,"user":667,"quote":668},"u/reefine(Reddit 38 upvotes)","Perplexity 現在還有存在感嗎",{"platform":69,"user":670,"quote":671},"@yabhishekhd(X)","Samsung Galaxy S26 系列完整規格外洩——螢幕、晶片、相機、電池、尺寸、定價全都有（來源：WinFuture）。Galaxy S26：6.3 吋 Dynamic AMOLED 2X、2340×1080(FHD+) 、120Hz、搭載 Android 16。","觀望","Gemini 代理任務仍處 Beta 且僅限少數應用類別，需觀察生態擴展後是否真正改變 Android 手機的日常使用模式。",{"category":131,"source":11,"title":675,"publishDate":6,"tier1Source":676,"supplementSources":678,"coreInfo":687,"engineerView":688,"businessView":689,"viewALabel":440,"viewBLabel":441,"bench":378,"communityQuotes":690,"verdict":460,"impact":697},"Circle to Search 升級：Gemini 3 驅動多目標平行視覺搜尋",{"name":212,"url":677},"https://blog.google/products-and-platforms/products/search/circle-to-search-february-2026/",[679,683],{"name":680,"url":681,"detail":682},"9to5Google","https://9to5google.com/2026/02/25/circle-to-search-gemini-3/","Gemini 3 技術細節與底部對話 UI 變更報導",{"name":684,"url":685,"detail":686},"Dataconomy","https://dataconomy.com/2026/02/26/gemini-3-powered-circle-to-search-debuts-on-galaxy-s26-and-pixel-10/","Galaxy S26 首發覆蓋後續報導","#### 多目標平行搜尋升級\n\nCircle to Search 在 2026 年 2 月迎來重大升級，搭載 Gemini 3，具備代理規劃 (agentic planning) 、推理與工具呼叫能力。新功能核心在於視覺展開 (visual fan-out) ：系統自動識別圖片中的多個重要區域，分別裁切後同時發出多條搜尋，再將結果交叉比對合成單一回覆。\n\n> **名詞解釋**\n> Visual fan-out（視覺展開）：將一張圖片拆解為多個感興趣區域，對每個區域平行執行獨立搜尋，最後彙整為統整結果。\n\n此架構延伸自 Google 在 2025 年 AI Mode 引入的查詢展開 (query fan-out) 技術——同時對多個子主題和資料來源發出並行子搜尋。\n\n#### 虛擬試穿與隱私設計\n\n更新同步新增購物「虛擬試穿」入口，支援區域含澳洲、加拿大、印度、日本、英國、美國。Google 聲明試穿照片僅在功能範圍內處理，不用於模型訓練，亦不儲存任何生物特徵資料。升級首發於 Samsung Galaxy S26 系列和 Pixel 10，計畫擴展至更多 Android 裝置；目前 Circle to Search 已在逾 5.8 億台 Android 裝置上使用。","Gemini 3 的代理規劃能力讓 Circle to Search 從「單點查詢」演進為「平行多目標推理」。視覺展開在端上切圖、分流後並行發送子搜尋，由 Gemini 交叉推理合成回覆——這套架構與 AI Mode 的 query fan-out 共用技術基礎。對 Android 開發者而言，值得關注的是 Google 如何將 agentic 推理能力下放到裝置端搜尋場景，以及未來 Gemini API 是否開放類似的 fan-out 工具呼叫介面。","Circle to Search 已覆蓋逾 5.8 億台 Android 裝置，搭載虛擬試穿後直接打通搜尋→購物轉換漏斗，對競品（如 Pinterest、Amazon 視覺搜尋）形成壓制。Samsung Galaxy S26 與 Pixel 10 的首發優勢將 Gemini 3 與旗艦硬體深度綁定，強化 Google Android 生態差異化。品牌廣告主需留意：消費者可能直接在搜尋結果中完成試穿比價，繞過品牌官網的購物流程。",[691,694],{"platform":69,"user":692,"quote":693},"@androidcentral(Android Central tech publication)","Circle to Search 剛滿兩週年，但它比以往更好用。如果你只把 Circle to Search 當成 Google Lens 的替代品來用，你真的虧大了。",{"platform":69,"user":695,"quote":696},"@MishaalRahman(Android journalist and researcher)","據報導，Google 計劃下個月將 Circle to Search 擴展至更多 Android 手機，終結其對 Pixel 和 Samsung 手機的獨家限制。","Gemini 3 驅動的視覺平行搜尋正式落地，搜尋→購物漏斗縮短，5.8 億 Android 用戶為潛在受眾。",{"category":274,"source":9,"title":699,"publishDate":6,"tier1Source":700,"supplementSources":702,"coreInfo":711,"engineerView":712,"businessView":713,"viewALabel":714,"viewBLabel":715,"bench":378,"communityQuotes":716,"verdict":460,"impact":732},"Qwen3.5-27B 本地推理令社群驚艷：廉價開源模型已可建構 3D 遊戲原型",{"name":135,"url":701},"https://www.reddit.com/r/LocalLLaMA/comments/1refvmr/qwen_3_27b_is_impressive/",[703,707],{"name":704,"url":705,"detail":706},"Qwen3 官方部落格","https://qwenlm.github.io/blog/qwen3/","Qwen3 系列架構與訓練細節",{"name":708,"url":709,"detail":710},"Qwen3.5-27B Model Card(Hugging Face)","https://huggingface.co/Qwen/Qwen3.5-27B","技術規格與授權資訊","#### 社群熱議：廉價本地模型完成複雜任務\n\nReddit r/LocalLLaMA 熱帖中，用戶 -dysangel- 展示以 Qwen3.5-27B 量化版 (unsloth Qwen 3.5 27B UD Q4_K_XL) 在 OpenWebUI artifacts 視窗中，透過迭代提示建構類 GTA 3D 原型，全程無人工組裝、無外部框架介入，引發社群對「廉價本地模型已足以完成真實任務」的廣泛討論。\n\n> **名詞解釋**\n> Q4_K_XL 是 GGUF 量化格式之一，以 4-bit 精度壓縮模型權重，讓大型模型可在消費級顯卡上運行，以少量精度換取顯著記憶體節省。\n\n#### Qwen3.5-27B 技術規格\n\nQwen3.5-27B 採 27B 參數、64 層架構，混合 `Gated DeltaNet + Gated Attention` 機制，上下文長度 262,144 tokens（可擴展至 1,010,000），以 Apache-2.0 授權開源。Qwen3 系列支援思考與非思考雙模式切換，訓練規模約 36T tokens，涵蓋 119 種語言，支援 vLLM、SGLang 及 OpenAI 相容介面部署。","Qwen3.5-27B Q4 量化版可直接在本地透過 OpenWebUI 使用，無需額外工程搭建。混合 `Gated DeltaNet` 架構帶來比純 Transformer 更長的有效上下文，262K tokens 原生支援對複雜多輪程式碼生成直接有利。Apache-2.0 授權允許商業部署；建議先用 ollama 或 llama.cpp 跑 Q4_K_XL GGUF 驗證效果，確認後再遷移至 vLLM 或 SGLang 做生產批次服務。","此次展示說明開源本地推理已達可用門檻，無需雲端 API 即可完成複雜創作任務。社群提及 ASIC 硬體可進一步壓低推理成本，若此路線成熟，雲端 API 定價護城河將顯著縮小。對企業而言，資料隱私與成本控制可同時被本地部署路徑滿足，但硬體採購與維運成本仍是導入評估的關鍵變數。","開發者視角（整合與部署）","生態影響",[717,720,723,726,729],{"platform":135,"user":718,"quote":719},"u/UnbeliebteMeinung(Reddit r/LocalLLaMA)","能看到我們可以用廉價模型完成真實可用的東西，真的很高興。這對未來是個好兆頭。結合這些 ASIC LLM 晶片，本地快速且強大的推理的未來是可能的⋯⋯感謝老天大型提供商不會形成壟斷，這改變了我們未來的一切。",{"platform":135,"user":721,"quote":722},"u/ciaguyforeal(Reddit r/LocalLLaMA)","這是在某個框架裡執行，還是它只是在寫程式碼然後需要手動組裝？",{"platform":57,"user":724,"quote":725},"laramie_co（HN 用戶）","我個人每月在 Claude API 上花約 1,200 美元（用於寫程式、寫作、分析）——換算每年 14,400 美元。即使我降到每月 20 美元方案，每次查詢都在告訴 Anthropic 我在做什麼。我想要 Claude 等級的推理能力而不依賴雲端，雖然大型模型還做不到，但本地端能做到的已出乎意料地好。",{"platform":57,"user":727,"quote":728},"ColonelPhantom（HN 用戶）","不只是 Qwen，我們最近也有 GLM-4.7-Flash，同樣在 30B-A3 左右的範圍。在我看來，30B 左右的優質開源模型競爭並不缺乏——不只是 Qwen3.5-35B 和 GLM-4.7-Flash，還有 Qwen3(-Coder)-30B 或 Granite 4 Small。",{"platform":57,"user":730,"quote":731},"jmorgan（HN 用戶）","對於本地模型，我一直在用 GLM-4.7-Flash 和新的 LFM2 24B 模型進行測試。我很期待也嘗試今天發布的新 Qwen3.5 模型。","本地 27B 開源模型已可完成複雜程式碼生成任務，Apache-2.0 授權加速企業自建推理基礎設施，降低對雲端 API 的長期依賴。","#### 社群熱議排行\n\n今日討論熱度最高的五個主題，依社群互動量排序：\n\n- **Google API 金鑰安全危機**（HN 高互動）：Truffle Security 揭露近 3,000 個網站因 Gemini 整合而暴露 `AIza` 前綴 API 金鑰，連 Google 自身也中招。@_JohnHammond(X) 快速摘要「Google API 金鑰過去不被視為機密，所以它們散落在整個網路上——但現在它們成了 Gemini 的一扇敞開的大門」，引爆 HN 多條討論串。\n- **Qwen3.5 本地部署實測熱潮**（Reddit r/LocalLLaMA 大量跑分回報）：122B MoE 模型在三張消費級 GPU（約 72GB VRAM）可流暢運行，u/mossy_troll_84 公布 Q4 量化版在 RTX 5090 環境可達 34–36 tok/sec，重新定義本地高效能推論門檻。\n- **Nano Banana 2 奪下圖像評測榜首**（Reddit r/singularity，u/THE--GRINCH 82 upvotes）：以 Pro 一半定價登頂 Artificial Analysis Image Arena，u/THE--GRINCH 直言「圖像生成問題愈來愈接近被解決了」，u/bentendo93(70 upvotes) 以裝潢規劃實測背書。\n- **anthropics/skills 技能生態**（HN + X 雙平台熱議）：Agent Skills 開放標準在數小時內催生 macOS 管理工具 Skill Studio，@AndrewYNg 公開背書 DeepLearning.AI 合作課程，引發工具作者與開發者廣泛討論。\n- **OpenAI Codex + Figma MCP 整合**（HN 活躍討論）：@parhamb(X) 分享三步驟設定教學並附言「親測有效」，推文迅速傳播為當日最多人收藏的技術帖之一。\n\n#### 技術爭議與分歧\n\n本日最明顯的社群分歧在 **benchmark 可信度** 與 **API 金鑰安全責任歸屬** 兩條戰線上激烈交鋒。\n\n在 benchmark 爭議上，u/metigue(Reddit r/LocalLLaMA) 直指問題核心：「在 Terminal Bench 2 和 Sanity Harness 上，同一個模型換框架可以看到超過 50% 的分數波動，而開源模型對糟糕的 agentic 框架特別敏感」——這讓 Qwen3.5 旗艦版的「崩落」究竟是模型問題還是框架問題，完全無法定論。另一側，u/UmpireBorn3719(Reddit r/LocalLLaMA) 質疑 gpt-oss-20b（1405 分）壓過 Qwen3.5 旗艦（1328 分）的結果是否可信，雙方對「誰才是最強開源程式模型」毫無共識。\n\n在安全責任歸屬上，gowld(HN) 冷嘲「也許是有經驗的資安審查人員都被裁員了」；SoftTalker(HN) 則持截然不同的立場：「這只是公用事業模式——如果有人接上你戶外的水龍頭偷水，你還是得付錢」。兩種立場折射出對科技公司安全設計責任的根本分歧：一派認為設計缺陷應由平台負責，另一派認為這是使用者自身的風險管理課題。\n\n#### 實戰經驗（最高價值）\n\n- u/mossy_troll_84(Reddit r/LocalLLaMA) ：在 Ryzen 9 9950X3D + RTX 5090 + 128GB DDR5 5600 環境下，Qwen3.5-122B-A10B-UD-Q4_K_XL 實測 34–36 tok/sec；Q8_K_XL 為 16–18 tok/sec，最大上下文均 256K，首次公布消費級旗艦硬體的具體跑分基準。\n- u/bentendo93（Reddit r/singularity，70 upvotes）：以 Nano Banana 2 測試室內裝潢規劃，「效果超好，好到讓我現在就想砸錢裝修了」——驗證主體一致性在高需求視覺場景的商業轉化潛力。\n- laramie_co(HN) ：自曝每月在 Claude API 花費約 1,200 美元（年計 14,400 美元），正評估本地推論替代方案：「即使降到月付 20 美元方案，每次查詢都在告訴 Anthropic 我在做什麼」——揭示隱私驅動的本地化遷移趨勢，而非純粹成本考量。\n- @parhamb(X) ：親測 Codex + Figma MCP 整合，確認修改 `~/.codex/config.toml` 加入 MCP 伺服器設定後可直接在 Codex CLI 呼叫 Figma 資產，為社群提供可直接複製的設定模板。\n\n#### 未解問題與社群預期\n\n社群目前懸而未決的關鍵問題集中在四個方向：\n\n**安全責任邊界**：neop1x(HN) 指出 Google 現有的 API 金鑰限制方案「每位管理員都必須對每個專案重複執行，顯然只是個權宜之計」——社群等待 Google 正式撤回「API 金鑰非機密」聲明，並在金鑰啟用新服務時引入顯式確認機制，目前官方無回應。\n\n**技能路徑標準化**：westurner(HN) 點出 `.claude/skills/` 與 `.agents/skills/` 雙路徑並存的問題，直言「如果規格能指定通用的家目錄相對路徑，對整個生態會更好」，agentskills.io 尚未給出明確答覆。\n\n**消費級 AI 功能膨脹**：Galaxy S26 預載三個 LLM 服務引發強烈反彈，u/Ilm03（Reddit，79 upvotes）質疑「在手機裡預載 3 個 LLM 服務感覺有點過頭」，u/Embarrassed-Nose2526（Reddit，42 upvotes）更指出 iPhone 與 Pixel 正因軟體精簡而獲益——對「AI 功能堆砌 vs. 精簡體驗」的取捨分歧預計將在 S26 正式發布後激化。\n\n**本地模型的長期競爭力**：ColonelPhantom(HN) 觀察到 30B 左右的優質開源模型競爭白熱化——不只是 Qwen3.5，還有 GLM-4.7-Flash、Granite 4 Small 等。社群真正的問題是：當本地 27B 模型已可生成可互動的 3D 遊戲原型，雲端 API 的差異化護城河還剩多少？",[735,737,739,741,743,745,747,749,750,752,753,755,757],{"type":77,"text":736},"登入 Google AI Studio，檢視現有 API 金鑰的安全狀態面板，對每個金鑰設定 API 範圍限制（僅允許必要服務）與應用程式限制（綁定來源 IP 或 HTTP referrer），確認是否出現外洩警告通知。",{"type":77,"text":738},"用 Qwen3.5-27B 在自己的 repo 上跑 5–10 個 issue，並用兩個不同 agentic 框架（如 SWE-agent 和 OpenHands）比較分數差異，確認框架影響程度後再做模型選型決策。",{"type":77,"text":740},"在現有專案建立 `.claude/skills/` 資料夾，從 anthropics/skills 倉庫複製 frontend-design 或 git-commit 技能，觀察 Claude Code 在相關任務中的行為變化，感受零提示詞重複的體驗差異。",{"type":77,"text":742},"透過 Gemini API 呼叫 Nano Banana 2(gemini-2.0-flash-exp-image-generation) ，以廣告創意、電商產品圖或室內設計等場景測試主體一致性，並與舊版本比較生成品質與成本差異。",{"type":77,"text":744},"修改 `~/.codex/config.toml` 加入 Figma MCP 設定（`url = \"http://127.0.0.1:3845/mcp\"`），取一個現有 UI 組件試試從 Figma 設計稿生成程式碼，評估在你的設計系統中的元件還原度。",{"type":80,"text":746},"在 CI/CD 管線整合 TruffleHog，掃描所有 `AIza` 前綴字串（Google API 金鑰常見前綴），偵測到金鑰時自動阻擋 PR 合併，並定期稽核 GCP Console 的 Credentials 頁面。",{"type":80,"text":748},"設計一組 10–20 個「內部 benchmark」任務，覆蓋你實際工作流中的難度分布，建立可重複驗測的 agentic 評估流水線，不依賴單一外部 benchmark 做模型選型決策。",{"type":80,"text":415},{"type":80,"text":751},"若 Figma→程式碼元件還原度達到 80% 以上，考慮在 PR 流程中加入 Figma MCP 步驟，讓設計稿改動自動觸發對應程式碼建議，縮短設計→開發的同步週期。",{"type":83,"text":84},{"type":83,"text":754},"追蹤 agentskills.io 規格更新，關注 `.claude/skills/` 與 `.agents/skills/` 路徑標準是否收斂，以及 Cursor、Windsurf 等主流 AI IDE 是否陸續宣布支援，作為企業大規模導入的決策時機訊號。",{"type":83,"text":756},"追蹤 APEX 排行榜更新、GLM-4.7 全尺寸版本的社群確認，以及 OpenAI SWE-bench Pro 的採用情況——這三件事決定了下一輪開源程式模型選型的基準線。",{"type":83,"text":758},"追蹤 OpenAI 廣告化策略的具體推進（廣告時機、形式與免費層綁定方式），以及低價分層方案是否進一步壓縮 API 供應商的定價空間，重新評估長期 API 成本結構。","今天的 AI 社群正在三條平行戰線上同時移動。Google API 金鑰危機提醒我們，過去「設計如此」的隱性安全假設在 AI 服務疊加後可能瞬間失效——任何歷史上被標記為「非機密」的憑證，在整合新能力後都值得重新審視。Qwen3.5 在消費級硬體上的實測數據，讓「雲端 vs. 本地」的成本與隱私算式開始真正有解：當 laramie_co 等開發者每年花 14,000 美元在雲端 API、同時擔心資料去向，而本地 27B 模型已能生成可互動的 3D 原型，這不再只是技術討論，而是實際的採購決策。而 Skills 生態在數小時內自發湧現管理工具，則暗示著 AI 工具協作的下一個核心基礎設施正在悄悄成形——不是由平台主導，而是由社群先跑出來。三件事的共同指向：AI 的競爭優勢正從「誰的模型最強」，快速移向「誰能最快把能力整合進現有工作流，同時管好安全與成本」。",{"prev":115,"next":761},"2026-02-28",{"data":763,"body":764,"excerpt":-1,"toc":774},{"title":378,"description":40},{"type":765,"children":766},"root",[767],{"type":768,"tag":769,"props":770,"children":771},"element","p",{},[772],{"type":773,"value":40},"text",{"title":378,"searchDepth":775,"depth":775,"links":776},2,[],{"data":778,"body":779,"excerpt":-1,"toc":785},{"title":378,"description":44},{"type":765,"children":780},[781],{"type":768,"tag":769,"props":782,"children":783},{},[784],{"type":773,"value":44},{"title":378,"searchDepth":775,"depth":775,"links":786},[],{"data":788,"body":789,"excerpt":-1,"toc":795},{"title":378,"description":47},{"type":765,"children":790},[791],{"type":768,"tag":769,"props":792,"children":793},{},[794],{"type":773,"value":47},{"title":378,"searchDepth":775,"depth":775,"links":796},[],{"data":798,"body":799,"excerpt":-1,"toc":805},{"title":378,"description":50},{"type":765,"children":800},[801],{"type":768,"tag":769,"props":802,"children":803},{},[804],{"type":773,"value":50},{"title":378,"searchDepth":775,"depth":775,"links":806},[],{"data":808,"body":810,"excerpt":-1,"toc":858},{"title":378,"description":809},"Google 多年來在 Firebase 等平台文件中明確告知開發者：API 金鑰不是機密，可以放入前端程式碼、公開 Git 儲存庫，甚至 Common Crawl 可索引的網頁中。這個「公開即安全」的前提，讓無數開發者在無意間將金鑰曝光於公共網路。Truffle Security 的研究揭露，這個延續多年的安全假設，在 Gemini 服務上線後已悄然失效。",{"type":765,"children":811},[812,816,823,828,834,839],{"type":768,"tag":769,"props":813,"children":814},{},[815],{"type":773,"value":809},{"type":768,"tag":817,"props":818,"children":820},"h4",{"id":819},"前因-1文件明文說非機密的歷史",[821],{"type":773,"value":822},"前因 1：文件明文說「非機密」的歷史",{"type":768,"tag":769,"props":824,"children":825},{},[826],{"type":773,"value":827},"Firebase 的安全檢查清單至今（2026-01-21 更新版本）仍寫明 Firebase API 金鑰不是機密，Maps JavaScript API 文件（2026-02-26 更新）同樣展示前端直接嵌入金鑰的做法，並僅以「未限制的金鑰可能遭濫用」輕描淡寫帶過風險。這套文件策略使開發者長期低估金鑰管理的必要性，形成系統性的安全認知缺口。",{"type":768,"tag":817,"props":829,"children":831},{"id":830},"前因-2gemini-上線帶來特權提升路徑",[832],{"type":773,"value":833},"前因 2：Gemini 上線帶來「特權提升」路徑",{"type":768,"tag":769,"props":835,"children":836},{},[837],{"type":773,"value":838},"2025 年起，Google 陸續在各 GCP 專案中推出 Gemini 與 Generative Language API。問題的核心在於：一個已存在的 GCP 專案 API 金鑰，一旦有人——或自動化流程——在同一專案內啟用了生成式語言 API，該金鑰便可立即用於呼叫 Gemini 端點，無需重新核發、無需額外授權。Truffle Security 將此定義為「單服務特權提升」 (Single-Service Privilege Escalation) ，Google 在 2026-01-13 接受了這個分類。",{"type":768,"tag":840,"props":841,"children":842},"blockquote",{},[843],{"type":768,"tag":769,"props":844,"children":845},{},[846,852,856],{"type":768,"tag":847,"props":848,"children":849},"strong",{},[850],{"type":773,"value":851},"名詞解釋",{"type":768,"tag":853,"props":854,"children":855},"br",{},[],{"type":773,"value":857},"\nSingle-Service Privilege Escalation（單服務特權提升）：指原本僅具低風險存取權限的憑證，因同一系統的新服務被啟用，導致其實際可存取範圍大幅擴張，而憑證持有人毫不知情。",{"title":378,"searchDepth":775,"depth":775,"links":859},[],{"data":861,"body":862,"excerpt":-1,"toc":923},{"title":378,"description":378},{"type":765,"children":863},[864,869,883,888,893,913,918],{"type":768,"tag":817,"props":865,"children":867},{"id":866},"核心條款",[868],{"type":773,"value":866},{"type":768,"tag":769,"props":870,"children":871},{},[872,874,881],{"type":773,"value":873},"Google 的應對措施分為兩層。第一層為事後封鎖：針對在 Common Crawl 等公開資料集中被偵測到的外洩金鑰，Google 已主動阻止其存取 Gemini 端點，受影響的金鑰呼叫時會收到錯誤訊息：",{"type":768,"tag":875,"props":876,"children":878},"code",{"className":877},[],[879],{"type":773,"value":880},"Your API key was reported as leaked. Please use another API key.",{"type":773,"value":882}," 第二層為預防性設計建議：Google 建議開發者改用 AI Studio 核發的金鑰，這類金鑰預設僅限 Google AI Studio 與 Gemini 使用範圍，降低跨服務特權提升的風險。",{"type":768,"tag":817,"props":884,"children":886},{"id":885},"適用範圍",[887],{"type":773,"value":885},{"type":768,"tag":769,"props":889,"children":890},{},[891],{"type":773,"value":892},"所有持有 GCP 專案 API 金鑰的開發者均受影響，尤其是：",{"type":768,"tag":894,"props":895,"children":896},"ul",{},[897,903,908],{"type":768,"tag":898,"props":899,"children":900},"li",{},[901],{"type":773,"value":902},"曾在公開 Git 儲存庫、前端程式碼或可索引網頁中嵌入金鑰的開發者",{"type":768,"tag":898,"props":904,"children":905},{},[906],{"type":773,"value":907},"使用 Firebase、Maps JavaScript API 等歷史上文件明示「金鑰非機密」的服務的開發者",{"type":768,"tag":898,"props":909,"children":910},{},[911],{"type":773,"value":912},"其 GCP 專案中已啟用或未來將啟用 Generative Language API 的帳戶",{"type":768,"tag":817,"props":914,"children":916},{"id":915},"執法機制",[917],{"type":773,"value":915},{"type":768,"tag":769,"props":919,"children":920},{},[921],{"type":773,"value":922},"目前 Google 的執法機制為被動偵測：僅對已知外洩（如 Common Crawl 資料集）的金鑰採取封鎖行動。未被偵測到的外洩金鑰仍可正常使用，產生的帳單風險由金鑰持有者自行承擔。Google 的帳單申訴流程可處理部分情況，但審核結果因案而異，並非保證退款。",{"title":378,"searchDepth":775,"depth":775,"links":924},[],{"data":926,"body":928,"excerpt":-1,"toc":957},{"title":378,"description":927},"開發者需要完成以下技術改造：",{"type":765,"children":929},[930,934],{"type":768,"tag":769,"props":931,"children":932},{},[933],{"type":773,"value":927},{"type":768,"tag":894,"props":935,"children":936},{},[937,942,947,952],{"type":768,"tag":898,"props":938,"children":939},{},[940],{"type":773,"value":941},"稽核現有 GCP 專案的 API 金鑰清單，確認哪些金鑰所屬專案已啟用 Generative Language API",{"type":768,"tag":898,"props":943,"children":944},{},[945],{"type":773,"value":946},"為所有 API 金鑰設定 API 限制（僅允許必要的服務）與應用程式限制（綁定來源 IP 或 HTTP referrer）",{"type":768,"tag":898,"props":948,"children":949},{},[950],{"type":773,"value":951},"將前端直接使用的 API 金鑰遷移至伺服器端代理或短效憑證 (ephemeral tokens)",{"type":768,"tag":898,"props":953,"children":954},{},[955],{"type":773,"value":956},"輪替 (rotate) 所有曾公開出現過的舊有金鑰",{"title":378,"searchDepth":775,"depth":775,"links":958},[],{"data":960,"body":962,"excerpt":-1,"toc":986},{"title":378,"description":961},"對於小型開發者或個人專案，金鑰審計通常可在半天內完成。對於擁有大量 GCP 專案的企業，則需要：",{"type":765,"children":963},[964,968],{"type":768,"tag":769,"props":965,"children":966},{},[967],{"type":773,"value":961},{"type":768,"tag":894,"props":969,"children":970},{},[971,976,981],{"type":768,"tag":898,"props":972,"children":973},{},[974],{"type":773,"value":975},"人力：資安工程師盤點所有專案金鑰（視規模需 1-5 人天）",{"type":768,"tag":898,"props":977,"children":978},{},[979],{"type":773,"value":980},"工具：TruffleHog 等開源工具可掃描程式碼儲存庫（免費，但需整合進 CI/CD 管線）",{"type":768,"tag":898,"props":982,"children":983},{},[984],{"type":773,"value":985},"時間：金鑰輪替與應用程式重新部署的耗時視服務數量而定",{"title":378,"searchDepth":775,"depth":775,"links":987},[],{"data":989,"body":991,"excerpt":-1,"toc":1029},{"title":378,"description":990},"最低限度的合規步驟：",{"type":765,"children":992},[993,997],{"type":768,"tag":769,"props":994,"children":995},{},[996],{"type":773,"value":990},{"type":768,"tag":998,"props":999,"children":1000},"ol",{},[1001,1006,1011,1024],{"type":768,"tag":898,"props":1002,"children":1003},{},[1004],{"type":773,"value":1005},"登入 Google AI Studio，檢視金鑰狀態警告面板",{"type":768,"tag":898,"props":1007,"children":1008},{},[1009],{"type":773,"value":1010},"前往 GCP Console → APIs & Services → Credentials，對每個金鑰加上 API 限制",{"type":768,"tag":898,"props":1012,"children":1013},{},[1014,1016,1022],{"type":773,"value":1015},"搜尋程式碼儲存庫中所有 ",{"type":768,"tag":875,"props":1017,"children":1019},{"className":1018},[],[1020],{"type":773,"value":1021},"AIza",{"type":773,"value":1023}," 開頭字串（Google API 金鑰的常見前綴）",{"type":768,"tag":898,"props":1025,"children":1026},{},[1027],{"type":773,"value":1028},"若發現曾公開曝光的金鑰，立即建立新金鑰並停用舊有金鑰",{"title":378,"searchDepth":775,"depth":775,"links":1030},[],{"data":1032,"body":1033,"excerpt":-1,"toc":1096},{"title":378,"description":378},{"type":765,"children":1034},[1035,1040,1045,1063,1068,1086,1091],{"type":768,"tag":817,"props":1036,"children":1038},{"id":1037},"直接影響者",[1039],{"type":773,"value":1037},{"type":768,"tag":769,"props":1041,"children":1042},{},[1043],{"type":773,"value":1044},"首當其衝的是：",{"type":768,"tag":894,"props":1046,"children":1047},{},[1048,1053,1058],{"type":768,"tag":898,"props":1049,"children":1050},{},[1051],{"type":773,"value":1052},"使用 Firebase 並已在前端嵌入 API 金鑰的 Web 開發者（Firebase 文件長期宣稱金鑰非機密）",{"type":768,"tag":898,"props":1054,"children":1055},{},[1056],{"type":773,"value":1057},"在 Common Crawl 可索引網頁中出現金鑰的網站所有人（已有 2,863 個確認受影響）",{"type":768,"tag":898,"props":1059,"children":1060},{},[1061],{"type":773,"value":1062},"使用 Maps JavaScript API 的開發者，相關文件至今仍示範前端嵌入方式",{"type":768,"tag":817,"props":1064,"children":1066},{"id":1065},"間接波及者",[1067],{"type":773,"value":1065},{"type":768,"tag":894,"props":1069,"children":1070},{},[1071,1076,1081],{"type":768,"tag":898,"props":1072,"children":1073},{},[1074],{"type":773,"value":1075},"GCP 服務商與受管服務提供商 (MSP) ：需協助客戶稽核並修補金鑰配置",{"type":768,"tag":898,"props":1077,"children":1078},{},[1079],{"type":773,"value":1080},"使用 Google Cloud 金鑰管理的 SaaS 供應商：若客戶的 GCP 專案啟用了 Gemini，其金鑰風險等級已悄然提升",{"type":768,"tag":898,"props":1082,"children":1083},{},[1084],{"type":773,"value":1085},"企業資安合規部門：需重新評估組織內 Google 憑證的分類標準與存取控制政策",{"type":768,"tag":817,"props":1087,"children":1089},{"id":1088},"成本轉嫁效應",[1090],{"type":773,"value":1088},{"type":768,"tag":769,"props":1092,"children":1093},{},[1094],{"type":773,"value":1095},"攻擊者可利用外洩金鑰呼叫 Gemini API，產生的 LLM 推理費用直接計入金鑰所有者的 GCP 帳單。若未設定配額上限，受害者可能在短時間內累積大量費用。Google 的帳單申訴流程可處理部分情況，但審核結果因案而異，並非保證退款，最終費用風險仍由終端開發者承擔。",{"title":378,"searchDepth":775,"depth":775,"links":1097},[],{"data":1099,"body":1100,"excerpt":-1,"toc":1106},{"title":378,"description":100},{"type":765,"children":1101},[1102],{"type":768,"tag":769,"props":1103,"children":1104},{},[1105],{"type":773,"value":100},{"title":378,"searchDepth":775,"depth":775,"links":1107},[],{"data":1109,"body":1110,"excerpt":-1,"toc":1116},{"title":378,"description":104},{"type":765,"children":1111},[1112],{"type":768,"tag":769,"props":1113,"children":1114},{},[1115],{"type":773,"value":104},{"title":378,"searchDepth":775,"depth":775,"links":1117},[],{"data":1119,"body":1120,"excerpt":-1,"toc":1126},{"title":378,"description":107},{"type":765,"children":1121},[1122],{"type":768,"tag":769,"props":1123,"children":1124},{},[1125],{"type":773,"value":107},{"title":378,"searchDepth":775,"depth":775,"links":1127},[],{"data":1129,"body":1130,"excerpt":-1,"toc":1136},{"title":378,"description":110},{"type":765,"children":1131},[1132],{"type":768,"tag":769,"props":1133,"children":1134},{},[1135],{"type":773,"value":110},{"title":378,"searchDepth":775,"depth":775,"links":1137},[],{"data":1139,"body":1140,"excerpt":-1,"toc":1146},{"title":378,"description":113},{"type":765,"children":1141},[1142],{"type":768,"tag":769,"props":1143,"children":1144},{},[1145],{"type":773,"value":113},{"title":378,"searchDepth":775,"depth":775,"links":1147},[],{"data":1149,"body":1150,"excerpt":-1,"toc":1156},{"title":378,"description":116},{"type":765,"children":1151},[1152],{"type":768,"tag":769,"props":1153,"children":1154},{},[1155],{"type":773,"value":116},{"title":378,"searchDepth":775,"depth":775,"links":1157},[],{"data":1159,"body":1160,"excerpt":-1,"toc":1166},{"title":378,"description":120},{"type":765,"children":1161},[1162],{"type":768,"tag":769,"props":1163,"children":1164},{},[1165],{"type":773,"value":120},{"title":378,"searchDepth":775,"depth":775,"links":1167},[],{"data":1169,"body":1170,"excerpt":-1,"toc":1176},{"title":378,"description":124},{"type":765,"children":1171},[1172],{"type":768,"tag":769,"props":1173,"children":1174},{},[1175],{"type":773,"value":124},{"title":378,"searchDepth":775,"depth":775,"links":1177},[],{"data":1179,"body":1180,"excerpt":-1,"toc":1186},{"title":378,"description":129},{"type":765,"children":1181},[1182],{"type":768,"tag":769,"props":1183,"children":1184},{},[1185],{"type":773,"value":129},{"title":378,"searchDepth":775,"depth":775,"links":1187},[],{"data":1189,"body":1190,"excerpt":-1,"toc":1196},{"title":378,"description":53},{"type":765,"children":1191},[1192],{"type":768,"tag":769,"props":1193,"children":1194},{},[1195],{"type":773,"value":53},{"title":378,"searchDepth":775,"depth":775,"links":1197},[],{"data":1199,"body":1200,"excerpt":-1,"toc":1206},{"title":378,"description":54},{"type":765,"children":1201},[1202],{"type":768,"tag":769,"props":1203,"children":1204},{},[1205],{"type":773,"value":54},{"title":378,"searchDepth":775,"depth":775,"links":1207},[],{"data":1209,"body":1210,"excerpt":-1,"toc":1216},{"title":378,"description":155},{"type":765,"children":1211},[1212],{"type":768,"tag":769,"props":1213,"children":1214},{},[1215],{"type":773,"value":155},{"title":378,"searchDepth":775,"depth":775,"links":1217},[],{"data":1219,"body":1220,"excerpt":-1,"toc":1226},{"title":378,"description":159},{"type":765,"children":1221},[1222],{"type":768,"tag":769,"props":1223,"children":1224},{},[1225],{"type":773,"value":159},{"title":378,"searchDepth":775,"depth":775,"links":1227},[],{"data":1229,"body":1230,"excerpt":-1,"toc":1236},{"title":378,"description":162},{"type":765,"children":1231},[1232],{"type":768,"tag":769,"props":1233,"children":1234},{},[1235],{"type":773,"value":162},{"title":378,"searchDepth":775,"depth":775,"links":1237},[],{"data":1239,"body":1240,"excerpt":-1,"toc":1246},{"title":378,"description":165},{"type":765,"children":1241},[1242],{"type":768,"tag":769,"props":1243,"children":1244},{},[1245],{"type":773,"value":165},{"title":378,"searchDepth":775,"depth":775,"links":1247},[],{"data":1249,"body":1251,"excerpt":-1,"toc":1304},{"title":378,"description":1250},"程式碼代理 (coding agent) 的能力評估在 2026 年陷入一場信任危機。一方面，各大廠商爭相在 SWE-bench Verified 上刷新紀錄，Qwen3.5-397B 官方宣稱達到 76.4%；另一方面，OpenAI 在 2026-02-23 正式宣告 SWE-bench Verified 已被污染，不再能衡量前沿模型的真實程式能力。社群因此迫切需要更可信的獨立評測管道，而 Reddit 社群分享的 APEX benchmark 結果，正是在這個背景下引爆討論。",{"type":765,"children":1252},[1253,1257,1263,1268,1283,1289,1294,1299],{"type":768,"tag":769,"props":1254,"children":1255},{},[1256],{"type":773,"value":1250},{"type":768,"tag":817,"props":1258,"children":1260},{"id":1259},"痛點-1標準-benchmark-已被訓練資料污染",[1261],{"type":773,"value":1262},"痛點 1：標準 benchmark 已被訓練資料污染",{"type":768,"tag":769,"props":1264,"children":1265},{},[1266],{"type":773,"value":1267},"SWE-bench Verified 長期以來是程式碼代理的黃金標準，但隨著前沿模型規模擴大、訓練資料範圍擴展，測試集題目越來越容易被「見過」。OpenAI 的公告直接指出這一問題並建議改用 SWE-bench Pro。這意味著模型在 SWE-bench 上的高分，部分可能來自「記住答案」而非真正的推理與修復能力，使得官方數字對開發者的參考價值大打折扣。",{"type":768,"tag":840,"props":1269,"children":1270},{},[1271],{"type":768,"tag":769,"props":1272,"children":1273},{},[1274,1278,1281],{"type":768,"tag":847,"props":1275,"children":1276},{},[1277],{"type":773,"value":851},{"type":768,"tag":853,"props":1279,"children":1280},{},[],{"type":773,"value":1282},"\nSWE-bench Verified 是由 Princeton NLP 建立的程式碼修復 benchmark，要求模型根據 GitHub issue 自動提交正確的程式碼修復 patch；Verified 版本由人工驗證確保題目的可解性與品質。",{"type":768,"tag":817,"props":1284,"children":1286},{"id":1285},"痛點-2模型規模與任務難度之間的非線性落差",[1287],{"type":773,"value":1288},"痛點 2：模型規模與任務難度之間的非線性落差",{"type":768,"tag":769,"props":1290,"children":1291},{},[1292],{"type":773,"value":1293},"直覺上，更大的模型應該在更難的任務上表現更好。但 APEX 測試數據顯示，Qwen3.5-397B 在 hard/expert 難度取得約 1550 分，卻在 master 難度大幅滑落至 1194 分——而 Qwen3.5-27B 在同場景維持 1384 分，GPT-OSS-20B 更達到 1405 分。「更多參數 = 更強能力」的假設在高難度程式任務上並不成立，暗示旗艦模型的能力天花板可能與訓練資料分佈或架構選擇有關。",{"type":768,"tag":817,"props":1295,"children":1297},{"id":1296},"舊解法",[1298],{"type":773,"value":1296},{"type":768,"tag":769,"props":1300,"children":1301},{},[1302],{"type":773,"value":1303},"過去開發者通常依賴官方 benchmark 分數（SWE-bench Verified、HumanEval、MBPP）做模型選型決策。這些數字生產容易、易於比較，但多在單一函式修復或合成測試集上測量，未必反映面對複雜依賴關係的完整 repo 時的真實 agentic 表現。",{"title":378,"searchDepth":775,"depth":775,"links":1305},[],{"data":1307,"body":1309,"excerpt":-1,"toc":1315},{"title":378,"description":1308},"Qwen3.5-397B 在標準 benchmark 上的亮眼數字，為何到了 APEX 真實 repo 測試就顯著下滑？理解這個問題需要拆解三個機制：測試方法的差異、模型架構的特性，以及框架對 agentic 任務的隱性影響。",{"type":765,"children":1310},[1311],{"type":768,"tag":769,"props":1312,"children":1313},{},[1314],{"type":773,"value":1308},{"title":378,"searchDepth":775,"depth":775,"links":1316},[],{"data":1318,"body":1320,"excerpt":-1,"toc":1341},{"title":378,"description":1319},"APEX 從 GitHub 蒐集 70 個真實 repo 的程式任務，讓模型在 agentic tool-use 設定下執行——可呼叫 shell、搜尋程式碼、讀寫檔案，模擬真實工程師的工作流程。評分採用 pairwise ELO 制度，從正確性、完整性、品質與效率四個維度評估，截至測試時排行榜收錄 51 個模型、累積 3,431 次執行。這與合成測試集的「給一個函式、改一行程式碼」有本質差異。",{"type":765,"children":1321},[1322,1326],{"type":768,"tag":769,"props":1323,"children":1324},{},[1325],{"type":773,"value":1319},{"type":768,"tag":840,"props":1327,"children":1328},{},[1329],{"type":768,"tag":769,"props":1330,"children":1331},{},[1332,1336,1339],{"type":768,"tag":847,"props":1333,"children":1334},{},[1335],{"type":773,"value":851},{"type":768,"tag":853,"props":1337,"children":1338},{},[],{"type":773,"value":1340},"\nELO 制度源自西洋棋排名系統，用來計算玩家（或模型）的相對實力分數；pairwise ELO 讓每對模型在同一任務上互相比較，獲勝方得分、落敗方扣分，最終形成連續分數排行榜，能處理模型數量不等、執行次數不一的情況。",{"title":378,"searchDepth":775,"depth":775,"links":1342},[],{"data":1344,"body":1346,"excerpt":-1,"toc":1367},{"title":378,"description":1345},"Qwen3.5-397B-A17B 採用 Gated DeltaNet 加上稀疏 MoE 的混合架構，總參數 397B 但每次推理僅啟動 17B 活躍參數。官方宣傳的 SWE-bench Verified 76.4% 令人印象深刻，但在 APEX 的 master 難度任務上分數僅 1194——低於 Qwen3.5-27B 的 1384，更遠低於 GLM-4.7 量化版的 1572。可能的解釋是：master 難度任務需要更深度的跨檔案推理與狀態追蹤，而稀疏啟動架構在這類需要全域一致性的任務上存在固有局限。",{"type":765,"children":1347},[1348,1352],{"type":768,"tag":769,"props":1349,"children":1350},{},[1351],{"type":773,"value":1345},{"type":768,"tag":840,"props":1353,"children":1354},{},[1355],{"type":768,"tag":769,"props":1356,"children":1357},{},[1358,1362,1365],{"type":768,"tag":847,"props":1359,"children":1360},{},[1361],{"type":773,"value":851},{"type":768,"tag":853,"props":1363,"children":1364},{},[],{"type":773,"value":1366},"\nMoE（Mixture of Experts，混合專家架構）是一種神經網路設計，模型由多個「專家」子網路組成，每次推理只激活其中少數幾個，使超大參數模型能以較低計算成本運作，但可能在需要跨專家協調的複雜任務上表現不穩定。",{"title":378,"searchDepth":775,"depth":775,"links":1368},[],{"data":1370,"body":1372,"excerpt":-1,"toc":1394},{"title":378,"description":1371},"Reddit 社群評論指出一個關鍵問題：agentic 框架的設計會大幅影響模型的 benchmark 分數，在 Terminal Bench 2 和 Sanity Harness 上，同一模型換框架可以出現超過 50% 的分數波動。開源模型對「糟糕」的框架尤其敏感，因為它們的 instruction following 和工具呼叫格式比商業 API 更不穩定。APEX 目前使用自訂框架，尚未與 SWE-agent、OpenHands、Agentless 等主流框架交叉驗證，因此 Qwen3.5-397B 的低分有多少來自模型本身、多少來自框架，仍無定論。",{"type":765,"children":1373},[1374,1378],{"type":768,"tag":769,"props":1375,"children":1376},{},[1377],{"type":773,"value":1371},{"type":768,"tag":840,"props":1379,"children":1380},{},[1381],{"type":768,"tag":769,"props":1382,"children":1383},{},[1384,1389,1392],{"type":768,"tag":847,"props":1385,"children":1386},{},[1387],{"type":773,"value":1388},"白話比喻",{"type":768,"tag":853,"props":1390,"children":1391},{},[],{"type":773,"value":1393},"\n就像一位頂尖廚師被迫使用劣質廚具——廚師的技術沒有改變，但出餐品質大打折扣。agentic 框架就是那套廚具，選得好不好直接決定模型能發揮多少真實能力。",{"title":378,"searchDepth":775,"depth":775,"links":1395},[],{"data":1397,"body":1398,"excerpt":-1,"toc":1523},{"title":378,"description":378},{"type":765,"children":1399},[1400,1405,1428,1433,1456,1461,1466,1471,1489,1494,1512,1518],{"type":768,"tag":817,"props":1401,"children":1403},{"id":1402},"競爭版圖",[1404],{"type":773,"value":1402},{"type":768,"tag":894,"props":1406,"children":1407},{},[1408,1418],{"type":768,"tag":898,"props":1409,"children":1410},{},[1411,1416],{"type":768,"tag":847,"props":1412,"children":1413},{},[1414],{"type":773,"value":1415},"直接競品",{"type":773,"value":1417},"：GLM-4.7（量化版 APEX 1572 暫居第一，但版本未確認）、GPT-OSS-20B(1405) 、Codex 5.3（接近 GPT-5.2）",{"type":768,"tag":898,"props":1419,"children":1420},{},[1421,1426],{"type":768,"tag":847,"props":1422,"children":1423},{},[1424],{"type":773,"value":1425},"間接競品",{"type":773,"value":1427},"：Anthropic Claude Sonnet（API 服務）、Google Gemini 系列、Meta Llama 系列的程式碼代理能力",{"type":768,"tag":817,"props":1429,"children":1431},{"id":1430},"護城河類型",[1432],{"type":773,"value":1430},{"type":768,"tag":894,"props":1434,"children":1435},{},[1436,1446],{"type":768,"tag":898,"props":1437,"children":1438},{},[1439,1444],{"type":768,"tag":847,"props":1440,"children":1441},{},[1442],{"type":773,"value":1443},"工程護城河",{"type":773,"value":1445},"：Qwen3.5 的混合 Gated DeltaNet + 稀疏 MoE 架構提供 262,144 token 的原生上下文，對多檔案 agentic 任務有結構性優勢；Qwen3-Coder-Next 的訓練配方已複用於 Qwen3.5，技術路徑具延續性",{"type":768,"tag":898,"props":1447,"children":1448},{},[1449,1454],{"type":768,"tag":847,"props":1450,"children":1451},{},[1452],{"type":773,"value":1453},"生態護城河",{"type":773,"value":1455},"：開源授權使社群遷移門檻低；Alibaba Cloud 提供商業部署路徑，對亞太企業有採購便利性",{"type":768,"tag":817,"props":1457,"children":1459},{"id":1458},"定價策略",[1460],{"type":773,"value":1458},{"type":768,"tag":769,"props":1462,"children":1463},{},[1464],{"type":773,"value":1465},"Qwen3.5 系列以開源授權發布，本地部署無 API 費用。商業場景可透過阿里雲 API 調用，具體定價尚未在本次測試報告中揭露。競爭對手 GLM-4.7 的定價策略亦未公開，現階段成本比較有限。",{"type":768,"tag":817,"props":1467,"children":1469},{"id":1468},"企業導入阻力",[1470],{"type":773,"value":1468},{"type":768,"tag":894,"props":1472,"children":1473},{},[1474,1479,1484],{"type":768,"tag":898,"props":1475,"children":1476},{},[1477],{"type":773,"value":1478},"397B 全尺寸模型的硬體門檻高（需多 GPU 節點），多數中小型企業無法本地部署，必須依賴 API",{"type":768,"tag":898,"props":1480,"children":1481},{},[1482],{"type":773,"value":1483},"benchmark 結果的不確定性（框架敏感、排行榜遷移中）使企業難以建立信心，採購決策難以加速",{"type":768,"tag":898,"props":1485,"children":1486},{},[1487],{"type":773,"value":1488},"競爭格局快速變化（GLM-4.7、GPT-OSS-20B 均有競爭力），採購週期與模型迭代速度不匹配",{"type":768,"tag":817,"props":1490,"children":1492},{"id":1491},"第二序影響",[1493],{"type":773,"value":1491},{"type":768,"tag":894,"props":1495,"children":1496},{},[1497,1502,1507],{"type":768,"tag":898,"props":1498,"children":1499},{},[1500],{"type":773,"value":1501},"若 APEX 排行榜更新後 Qwen3.5-397B 數字改善，可能觸發社群重新評估，帶動採用率回升",{"type":768,"tag":898,"props":1503,"children":1504},{},[1505],{"type":773,"value":1506},"GLM-4.7 若確認以全尺寸版本奪冠，將使智譜 AI 聲量大幅提升，可能吸引企業採購評估",{"type":768,"tag":898,"props":1508,"children":1509},{},[1510],{"type":773,"value":1511},"SWE-bench Verified 被廢棄的趨勢加速後，缺乏公認替代標準將使模型選型更依賴內部測試，增加企業研究成本",{"type":768,"tag":817,"props":1513,"children":1515},{"id":1514},"判決先觀望benchmark-數字尚在重算框架敏感性未解",[1516],{"type":773,"value":1517},"判決：先觀望（benchmark 數字尚在重算，框架敏感性未解）",{"type":768,"tag":769,"props":1519,"children":1520},{},[1521],{"type":773,"value":1522},"Qwen3.5-397B 的官方 benchmark 與社群獨立測試之間存在顯著落差。APEX 排行榜正在遷移重算，框架敏感性問題尚未有交叉驗證，現階段不宜以旗艦規模做部署決策。若有本地部署需求，27B 版本在 master 難度表現更穩定且硬體門檻低；建議等待排行榜更新與多框架交叉驗證結果出爐後再做評估。",{"title":378,"searchDepth":775,"depth":775,"links":1524},[],{"data":1526,"body":1527,"excerpt":-1,"toc":1688},{"title":378,"description":378},{"type":765,"children":1528},[1529,1535,1641,1646,1669,1675],{"type":768,"tag":817,"props":1530,"children":1532},{"id":1531},"apex-elo-分數master-難度reddit-引用快照",[1533],{"type":773,"value":1534},"APEX ELO 分數（master 難度，Reddit 引用快照）",{"type":768,"tag":1536,"props":1537,"children":1538},"table",{},[1539,1558],{"type":768,"tag":1540,"props":1541,"children":1542},"thead",{},[1543],{"type":768,"tag":1544,"props":1545,"children":1546},"tr",{},[1547,1553],{"type":768,"tag":1548,"props":1549,"children":1550},"th",{},[1551],{"type":773,"value":1552},"模型",{"type":768,"tag":1548,"props":1554,"children":1555},{},[1556],{"type":773,"value":1557},"APEX ELO(master)",{"type":768,"tag":1559,"props":1560,"children":1561},"tbody",{},[1562,1576,1589,1602,1615,1628],{"type":768,"tag":1544,"props":1563,"children":1564},{},[1565,1571],{"type":768,"tag":1566,"props":1567,"children":1568},"td",{},[1569],{"type":773,"value":1570},"GLM-4.7 量化版",{"type":768,"tag":1566,"props":1572,"children":1573},{},[1574],{"type":773,"value":1575},"1572",{"type":768,"tag":1544,"props":1577,"children":1578},{},[1579,1584],{"type":768,"tag":1566,"props":1580,"children":1581},{},[1582],{"type":773,"value":1583},"GPT-OSS-20B",{"type":768,"tag":1566,"props":1585,"children":1586},{},[1587],{"type":773,"value":1588},"1405",{"type":768,"tag":1544,"props":1590,"children":1591},{},[1592,1597],{"type":768,"tag":1566,"props":1593,"children":1594},{},[1595],{"type":773,"value":1596},"Qwen3.5-27B",{"type":768,"tag":1566,"props":1598,"children":1599},{},[1600],{"type":773,"value":1601},"1384",{"type":768,"tag":1544,"props":1603,"children":1604},{},[1605,1610],{"type":768,"tag":1566,"props":1606,"children":1607},{},[1608],{"type":773,"value":1609},"Qwen3-Coder-Next",{"type":768,"tag":1566,"props":1611,"children":1612},{},[1613],{"type":773,"value":1614},"1328",{"type":768,"tag":1544,"props":1616,"children":1617},{},[1618,1623],{"type":768,"tag":1566,"props":1619,"children":1620},{},[1621],{"type":773,"value":1622},"Qwen3.5-35B MoE",{"type":768,"tag":1566,"props":1624,"children":1625},{},[1626],{"type":773,"value":1627},"1256",{"type":768,"tag":1544,"props":1629,"children":1630},{},[1631,1636],{"type":768,"tag":1566,"props":1632,"children":1633},{},[1634],{"type":773,"value":1635},"Qwen3.5-397B-A17B",{"type":768,"tag":1566,"props":1637,"children":1638},{},[1639],{"type":773,"value":1640},"1194",{"type":768,"tag":817,"props":1642,"children":1644},{"id":1643},"重要注意事項",[1645],{"type":773,"value":1643},{"type":768,"tag":894,"props":1647,"children":1648},{},[1649,1654,1659,1664],{"type":768,"tag":898,"props":1650,"children":1651},{},[1652],{"type":773,"value":1653},"以上數字來自 Reddit 貼文引用的 APEX 排行榜快照，2026-02-27 資料正在遷移重算，最終數字可能有所調整",{"type":768,"tag":898,"props":1655,"children":1656},{},[1657],{"type":773,"value":1658},"GLM-4.7 的具體版本（GLM-4.7-Flash 小模型 vs. Unsloth 版 100GB+ 全尺寸）尚未經社群確認",{"type":768,"tag":898,"props":1660,"children":1661},{},[1662],{"type":773,"value":1663},"Codex 5.3 分數「接近 GPT-5.2」，但貼文未提供具體 ELO 數字",{"type":768,"tag":898,"props":1665,"children":1666},{},[1667],{"type":773,"value":1668},"Qwen3.5-397B 在 hard/expert 難度約 1550 分，master 難度大幅下滑約 356 分",{"type":768,"tag":817,"props":1670,"children":1672},{"id":1671},"官方-benchmarkqwen35-397b供對照",[1673],{"type":773,"value":1674},"官方 benchmark（Qwen3.5-397B，供對照）",{"type":768,"tag":894,"props":1676,"children":1677},{},[1678,1683],{"type":768,"tag":898,"props":1679,"children":1680},{},[1681],{"type":773,"value":1682},"SWE-bench Verified：76.4%（已知存在污染問題）",{"type":768,"tag":898,"props":1684,"children":1685},{},[1686],{"type":773,"value":1687},"Terminal Bench 2：52.5%",{"title":378,"searchDepth":775,"depth":775,"links":1689},[],{"data":1691,"body":1692,"excerpt":-1,"toc":1709},{"title":378,"description":378},{"type":765,"children":1693},[1694],{"type":768,"tag":894,"props":1695,"children":1696},{},[1697,1701,1705],{"type":768,"tag":898,"props":1698,"children":1699},{},[1700],{"type":773,"value":171},{"type":768,"tag":898,"props":1702,"children":1703},{},[1704],{"type":773,"value":172},{"type":768,"tag":898,"props":1706,"children":1707},{},[1708],{"type":773,"value":173},{"title":378,"searchDepth":775,"depth":775,"links":1710},[],{"data":1712,"body":1713,"excerpt":-1,"toc":1730},{"title":378,"description":378},{"type":765,"children":1714},[1715],{"type":768,"tag":894,"props":1716,"children":1717},{},[1718,1722,1726],{"type":768,"tag":898,"props":1719,"children":1720},{},[1721],{"type":773,"value":175},{"type":768,"tag":898,"props":1723,"children":1724},{},[1725],{"type":773,"value":176},{"type":768,"tag":898,"props":1727,"children":1728},{},[1729],{"type":773,"value":177},{"title":378,"searchDepth":775,"depth":775,"links":1731},[],{"data":1733,"body":1734,"excerpt":-1,"toc":1740},{"title":378,"description":181},{"type":765,"children":1735},[1736],{"type":768,"tag":769,"props":1737,"children":1738},{},[1739],{"type":773,"value":181},{"title":378,"searchDepth":775,"depth":775,"links":1741},[],{"data":1743,"body":1744,"excerpt":-1,"toc":1750},{"title":378,"description":182},{"type":765,"children":1745},[1746],{"type":768,"tag":769,"props":1747,"children":1748},{},[1749],{"type":773,"value":182},{"title":378,"searchDepth":775,"depth":775,"links":1751},[],{"data":1753,"body":1754,"excerpt":-1,"toc":1760},{"title":378,"description":228},{"type":765,"children":1755},[1756],{"type":768,"tag":769,"props":1757,"children":1758},{},[1759],{"type":773,"value":228},{"title":378,"searchDepth":775,"depth":775,"links":1761},[],{"data":1763,"body":1764,"excerpt":-1,"toc":1770},{"title":378,"description":231},{"type":765,"children":1765},[1766],{"type":768,"tag":769,"props":1767,"children":1768},{},[1769],{"type":773,"value":231},{"title":378,"searchDepth":775,"depth":775,"links":1771},[],{"data":1773,"body":1774,"excerpt":-1,"toc":1780},{"title":378,"description":233},{"type":765,"children":1775},[1776],{"type":768,"tag":769,"props":1777,"children":1778},{},[1779],{"type":773,"value":233},{"title":378,"searchDepth":775,"depth":775,"links":1781},[],{"data":1783,"body":1784,"excerpt":-1,"toc":1790},{"title":378,"description":235},{"type":765,"children":1785},[1786],{"type":768,"tag":769,"props":1787,"children":1788},{},[1789],{"type":773,"value":235},{"title":378,"searchDepth":775,"depth":775,"links":1791},[],{"data":1793,"body":1795,"excerpt":-1,"toc":1823},{"title":378,"description":1794},"麻州 (Massachusetts) 長期以來是美國科技人才的重要基地，哈佛、MIT 等頂尖學府坐落於此，但隨著 AI 浪潮席捲全球就業市場，州政府開始面臨如何確保非技術背景居民不被時代淘汰的壓力。",{"type":765,"children":1796},[1797,1801,1807,1812,1818],{"type":768,"tag":769,"props":1798,"children":1799},{},[1800],{"type":773,"value":1794},{"type":768,"tag":817,"props":1802,"children":1804},{"id":1803},"前因-1ai-技能缺口威脅中低收入勞工",[1805],{"type":773,"value":1806},"前因 1：AI 技能缺口威脅中低收入勞工",{"type":768,"tag":769,"props":1808,"children":1809},{},[1810],{"type":773,"value":1811},"隨著生成式 AI 工具在職場中快速普及，雇主對具備基礎 AI 素養的員工需求急速上升。麻州製造業、零售、行政支援等傳統職類正面臨自動化衝擊，這些領域的從業者往往缺乏自行投資再訓練的資源。傳統職訓計畫的資金多集中在特定行業或高學歷族群，一般居民難以受惠。",{"type":768,"tag":817,"props":1813,"children":1815},{"id":1814},"前因-2google-已在麻州累積深厚基礎",[1816],{"type":773,"value":1817},"前因 2：Google 已在麻州累積深厚基礎",{"type":768,"tag":769,"props":1819,"children":1820},{},[1821],{"type":773,"value":1822},"Google 的 Grow with Google 計畫自 2017 年起在全美各州推動數位技能培訓，據報已有超過 25 萬名麻州居民完成數位技能課程。全球超過 100 萬人取得 Google Career Certificate，其中逾 70% 在 6 個月內獲得正面職涯影響。這個既有基礎讓麻州政府得以在現有機制上快速擴展，而非從零開始建立培訓體系。",{"title":378,"searchDepth":775,"depth":775,"links":1824},[],{"data":1826,"body":1828,"excerpt":-1,"toc":1894},{"title":378,"description":1827},"此次公告的核心是麻州政府透過 MassTech 旗下的麻州 AI 樞紐 (Massachusetts AI Hub) ，與 Google 合作提供無需額外費用的 AI 相關課程。",{"type":765,"children":1829},[1830,1834,1838,1843,1858,1862,1867,1871,1876],{"type":768,"tag":769,"props":1831,"children":1832},{},[1833],{"type":773,"value":1827},{"type":768,"tag":817,"props":1835,"children":1836},{"id":866},[1837],{"type":773,"value":866},{"type":768,"tag":769,"props":1839,"children":1840},{},[1841],{"type":773,"value":1842},"主要提供課程包括 Google AI Professional Certificate、Google AI Essentials、Google Agile Essentials，以及 Data Analytics、IT Support、Project Management 等職涯發展證書。其中 AI Professional Certificate 包含 20 餘項實作活動，並附贈 3 個月免費 Google AI Pro 存取權限。課程全為自進度線上形式，完成後可取得 Google 官方認證。",{"type":768,"tag":840,"props":1844,"children":1845},{},[1846],{"type":768,"tag":769,"props":1847,"children":1848},{},[1849,1853,1856],{"type":768,"tag":847,"props":1850,"children":1851},{},[1852],{"type":773,"value":851},{"type":768,"tag":853,"props":1854,"children":1855},{},[],{"type":773,"value":1857},"\nGoogle AI Professional Certificate：Google 官方推出的 AI 實務技能認證課程，涵蓋機器學習基礎、AI 工具應用與實作專案，面向非學術背景的職場人士設計。",{"type":768,"tag":817,"props":1859,"children":1860},{"id":885},[1861],{"type":773,"value":885},{"type":768,"tag":769,"props":1863,"children":1864},{},[1865],{"type":773,"value":1866},"所有麻州居民均可申請，無學歷、職業或年齡限制。免費存取期間至 2027 年 12 月 31 日止，涵蓋學生、在職員工及小型企業主。",{"type":768,"tag":817,"props":1868,"children":1869},{"id":915},[1870],{"type":773,"value":915},{"type":768,"tag":769,"props":1872,"children":1873},{},[1874],{"type":773,"value":1875},"本計畫屬志願性質的公共服務計畫，無罰則機制。執行機構為麻州 AI 樞紐（MassTech 旗下部門），申請流程如下：",{"type":768,"tag":998,"props":1877,"children":1878},{},[1879,1884,1889],{"type":768,"tag":898,"props":1880,"children":1881},{},[1882],{"type":773,"value":1883},"前往 MA AI Hub 網站填寫意願表單",{"type":768,"tag":898,"props":1885,"children":1886},{},[1887],{"type":773,"value":1888},"自行開始自進度線上課程",{"type":768,"tag":898,"props":1890,"children":1891},{},[1892],{"type":773,"value":1893},"完成課程後取得 Google 認證",{"title":378,"searchDepth":775,"depth":775,"links":1895},[],{"data":1897,"body":1898,"excerpt":-1,"toc":1904},{"title":378,"description":240},{"type":765,"children":1899},[1900],{"type":768,"tag":769,"props":1901,"children":1902},{},[1903],{"type":773,"value":240},{"title":378,"searchDepth":775,"depth":775,"links":1905},[],{"data":1907,"body":1908,"excerpt":-1,"toc":1914},{"title":378,"description":242},{"type":765,"children":1909},[1910],{"type":768,"tag":769,"props":1911,"children":1912},{},[1913],{"type":773,"value":242},{"title":378,"searchDepth":775,"depth":775,"links":1915},[],{"data":1917,"body":1918,"excerpt":-1,"toc":1938},{"title":378,"description":378},{"type":765,"children":1919},[1920],{"type":768,"tag":894,"props":1921,"children":1922},{},[1923,1928,1933],{"type":768,"tag":898,"props":1924,"children":1925},{},[1926],{"type":773,"value":1927},"前往 aihub.masstech.org/google-certificates 填寫意願表單",{"type":768,"tag":898,"props":1929,"children":1930},{},[1931],{"type":773,"value":1932},"根據自身程度選擇入門課程（推薦先從 AI Essentials 開始）",{"type":768,"tag":898,"props":1934,"children":1935},{},[1936],{"type":773,"value":1937},"依自進度完成課程並申請 Google 認證",{"title":378,"searchDepth":775,"depth":775,"links":1939},[],{"data":1941,"body":1942,"excerpt":-1,"toc":1999},{"title":378,"description":378},{"type":765,"children":1943},[1944,1948,1981,1985,1990,1994],{"type":768,"tag":817,"props":1945,"children":1946},{"id":1037},[1947],{"type":773,"value":1037},{"type":768,"tag":894,"props":1949,"children":1950},{},[1951,1961,1971],{"type":768,"tag":898,"props":1952,"children":1953},{},[1954,1959],{"type":768,"tag":847,"props":1955,"children":1956},{},[1957],{"type":773,"value":1958},"麻州居民",{"type":773,"value":1960},"：尤其是中低收入、非技術背景的勞工，可免費獲得具市場認可的 AI 技能認證",{"type":768,"tag":898,"props":1962,"children":1963},{},[1964,1969],{"type":768,"tag":847,"props":1965,"children":1966},{},[1967],{"type":773,"value":1968},"在地職訓機構",{"type":773,"value":1970},"：社區大學與職業培訓學校可能面臨部分生源轉移，原有的付費數位技能課程市場受到衝擊",{"type":768,"tag":898,"props":1972,"children":1973},{},[1974,1979],{"type":768,"tag":847,"props":1975,"children":1976},{},[1977],{"type":773,"value":1978},"在地 AI 培訓新創",{"type":773,"value":1980},"：原以麻州市場為主的付費課程提供者需重新評估定價策略，面對政府補貼帶來的免費競爭",{"type":768,"tag":817,"props":1982,"children":1983},{"id":1065},[1984],{"type":773,"value":1065},{"type":768,"tag":769,"props":1986,"children":1987},{},[1988],{"type":773,"value":1989},"麻州雇主可更容易招募到具備 Google 認證基礎 AI 素養的員工，降低內部培訓成本。其他州政府（尤其是科技產業集中的加州、紐約、德州）可能效仿此模式，推動類似的州政府與科技巨頭培訓合作計畫。",{"type":768,"tag":817,"props":1991,"children":1992},{"id":1088},[1993],{"type":773,"value":1088},{"type":768,"tag":769,"props":1995,"children":1996},{},[1997],{"type":773,"value":1998},"短期內課程費用由 Google 與州政府共同補貼，居民無需自付。然而長期而言，若大量居民取得 AI 相關認證後進入就業市場，相關技能的薪資溢價可能逐漸收窄，對已持有相關證書的從業者形成供給側壓力。",{"title":378,"searchDepth":775,"depth":775,"links":2000},[],{"data":2002,"body":2003,"excerpt":-1,"toc":2009},{"title":378,"description":248},{"type":765,"children":2004},[2005],{"type":768,"tag":769,"props":2006,"children":2007},{},[2008],{"type":773,"value":248},{"title":378,"searchDepth":775,"depth":775,"links":2010},[],{"data":2012,"body":2013,"excerpt":-1,"toc":2019},{"title":378,"description":251},{"type":765,"children":2014},[2015],{"type":768,"tag":769,"props":2016,"children":2017},{},[2018],{"type":773,"value":251},{"title":378,"searchDepth":775,"depth":775,"links":2020},[],{"data":2022,"body":2023,"excerpt":-1,"toc":2029},{"title":378,"description":254},{"type":765,"children":2024},[2025],{"type":768,"tag":769,"props":2026,"children":2027},{},[2028],{"type":773,"value":254},{"title":378,"searchDepth":775,"depth":775,"links":2030},[],{"data":2032,"body":2033,"excerpt":-1,"toc":2039},{"title":378,"description":257},{"type":765,"children":2034},[2035],{"type":768,"tag":769,"props":2036,"children":2037},{},[2038],{"type":773,"value":257},{"title":378,"searchDepth":775,"depth":775,"links":2040},[],{"data":2042,"body":2043,"excerpt":-1,"toc":2049},{"title":378,"description":260},{"type":765,"children":2044},[2045],{"type":768,"tag":769,"props":2046,"children":2047},{},[2048],{"type":773,"value":260},{"title":378,"searchDepth":775,"depth":775,"links":2050},[],{"data":2052,"body":2053,"excerpt":-1,"toc":2059},{"title":378,"description":262},{"type":765,"children":2054},[2055],{"type":768,"tag":769,"props":2056,"children":2057},{},[2058],{"type":773,"value":262},{"title":378,"searchDepth":775,"depth":775,"links":2060},[],{"data":2062,"body":2063,"excerpt":-1,"toc":2069},{"title":378,"description":263},{"type":765,"children":2064},[2065],{"type":768,"tag":769,"props":2066,"children":2067},{},[2068],{"type":773,"value":263},{"title":378,"searchDepth":775,"depth":775,"links":2070},[],{"data":2072,"body":2073,"excerpt":-1,"toc":2079},{"title":378,"description":302},{"type":765,"children":2074},[2075],{"type":768,"tag":769,"props":2076,"children":2077},{},[2078],{"type":773,"value":302},{"title":378,"searchDepth":775,"depth":775,"links":2080},[],{"data":2082,"body":2083,"excerpt":-1,"toc":2089},{"title":378,"description":305},{"type":765,"children":2084},[2085],{"type":768,"tag":769,"props":2086,"children":2087},{},[2088],{"type":773,"value":305},{"title":378,"searchDepth":775,"depth":775,"links":2090},[],{"data":2092,"body":2093,"excerpt":-1,"toc":2099},{"title":378,"description":307},{"type":765,"children":2094},[2095],{"type":768,"tag":769,"props":2096,"children":2097},{},[2098],{"type":773,"value":307},{"title":378,"searchDepth":775,"depth":775,"links":2100},[],{"data":2102,"body":2103,"excerpt":-1,"toc":2109},{"title":378,"description":309},{"type":765,"children":2104},[2105],{"type":768,"tag":769,"props":2106,"children":2107},{},[2108],{"type":773,"value":309},{"title":378,"searchDepth":775,"depth":775,"links":2110},[],{"data":2112,"body":2114,"excerpt":-1,"toc":2153},{"title":378,"description":2113},"OpenAI Codex 與 Figma 的整合，代表設計與工程之間長達十年的協作裂縫，正試圖以 AI 為橋梁縫合。Codex 產品負責人 Alexander Embiricos 明確表示，這個工作流「不預設你是設計師還是工程師」，而是讓兩種角色都能從自己熟悉的工具出發，無縫進入對方的領域。",{"type":765,"children":2115},[2116,2120,2126,2131,2137,2142,2148],{"type":768,"tag":769,"props":2117,"children":2118},{},[2119],{"type":773,"value":2113},{"type":768,"tag":817,"props":2121,"children":2123},{"id":2122},"痛點-1設計稿與程式碼之間的永恆鴻溝",[2124],{"type":773,"value":2125},"痛點 1：設計稿與程式碼之間的永恆鴻溝",{"type":768,"tag":769,"props":2127,"children":2128},{},[2129],{"type":773,"value":2130},"傳統工作流中，Figma 是設計師的主場，程式碼編輯器是工程師的戰場。兩者之間的資訊傳遞仰賴截圖、Slack 訊息、以及充滿誤解的口頭描述。設計稿改一個色票，工程師需要重新比對手動更新；工程師加了一個響應斷點，設計師完全不知情。這種「設計→標注→開發→回設計」的單向循環，消耗了大量跨職能溝通成本，在快速迭代的產品環境中格外致命。",{"type":768,"tag":817,"props":2132,"children":2134},{"id":2133},"痛點-2現有-ai-工具仍是各守一方的單向助手",[2135],{"type":773,"value":2136},"痛點 2：現有 AI 工具仍是各守一方的單向助手",{"type":768,"tag":769,"props":2138,"children":2139},{},[2140],{"type":773,"value":2141},"GitHub Copilot、Cursor 等 AI 程式碼工具擅長從文字描述生成程式碼，但無法理解或輸出 Figma 原生格式；Figma AI（如 Make）可生成設計稿草稿，但缺乏與真實程式碼庫的雙向同步能力。開發者仍需在兩套工具之間手動搬運設計意圖，AI 只解決了各自領域的局部問題，橋接點依然是人工。",{"type":768,"tag":817,"props":2143,"children":2145},{"id":2144},"舊解法第三方插件轉碼工具的侷限",[2146],{"type":773,"value":2147},"舊解法：第三方插件轉碼工具的侷限",{"type":768,"tag":769,"props":2149,"children":2150},{},[2151],{"type":773,"value":2152},"Locofy、Anima、Builder.io 等工具試圖解決 Figma→程式碼的轉換問題，但方向仍是單向的，且轉換品質參差不齊，無法處理複雜的互動邏輯與狀態管理，最終仍需大量人工修正才能進入生產環境。",{"title":378,"searchDepth":775,"depth":775,"links":2154},[],{"data":2156,"body":2158,"excerpt":-1,"toc":2164},{"title":378,"description":2157},"Figma MCP Server 是這次整合的核心基礎設施，讓 Codex 能以標準化協議讀寫 Figma 設計資源，實現真正的雙向工作流，而非過去工具鏈中的單向輸出。",{"type":765,"children":2159},[2160],{"type":768,"tag":769,"props":2161,"children":2162},{},[2163],{"type":773,"value":2157},{"title":378,"searchDepth":775,"depth":775,"links":2165},[],{"data":2167,"body":2169,"excerpt":-1,"toc":2220},{"title":378,"description":2168},"Figma MCP Server 提供兩種接入模式：遠端模式透過 https://mcp.figma.com/mcp 以 OAuth 認證連接 Figma 雲端服務；本地模式透過 http://127.0.0.1:3845/mcp 接入 Figma 桌面應用程式。遠端模式適合 CI/CD 環境或無頭伺服器場景；本地模式則能存取未發布的設計稿草稿與本地資源，適合開發階段的快速迭代。",{"type":765,"children":2170},[2171,2205],{"type":768,"tag":769,"props":2172,"children":2173},{},[2174,2176,2181,2183,2189,2191,2196,2197,2203],{"type":773,"value":2175},"Figma MCP Server 提供兩種接入模式：",{"type":768,"tag":847,"props":2177,"children":2178},{},[2179],{"type":773,"value":2180},"遠端模式",{"type":773,"value":2182},"透過 ",{"type":768,"tag":875,"props":2184,"children":2186},{"className":2185},[],[2187],{"type":773,"value":2188},"https://mcp.figma.com/mcp",{"type":773,"value":2190}," 以 OAuth 認證連接 Figma 雲端服務；",{"type":768,"tag":847,"props":2192,"children":2193},{},[2194],{"type":773,"value":2195},"本地模式",{"type":773,"value":2182},{"type":768,"tag":875,"props":2198,"children":2200},{"className":2199},[],[2201],{"type":773,"value":2202},"http://127.0.0.1:3845/mcp",{"type":773,"value":2204}," 接入 Figma 桌面應用程式。遠端模式適合 CI/CD 環境或無頭伺服器場景；本地模式則能存取未發布的設計稿草稿與本地資源，適合開發階段的快速迭代。",{"type":768,"tag":840,"props":2206,"children":2207},{},[2208],{"type":768,"tag":769,"props":2209,"children":2210},{},[2211,2215,2218],{"type":768,"tag":847,"props":2212,"children":2213},{},[2214],{"type":773,"value":851},{"type":768,"tag":853,"props":2216,"children":2217},{},[],{"type":773,"value":2219},"\nMCP(Model Context Protocol) 是 Anthropic 提出的開放標準，讓 AI 模型透過統一介面呼叫外部工具與資料來源，功能上類似 AI 應用的 REST API 規範，讓不同 AI 客戶端（Codex、Gemini CLI 等）都能用相同方式接入同一個工具服務。",{"title":378,"searchDepth":775,"depth":775,"links":2221},[],{"data":2223,"body":2225,"excerpt":-1,"toc":2246},{"title":378,"description":2224},"整合支援兩個方向的轉換：Figma → Code 方向允許 Codex 讀取 Figma Design、Make、FigJam 的設計脈絡（元件樣式、層級結構、尺寸標注），直接生成對應前端程式碼；Code → Figma 方向讓開發者可以從現有 UI 程式碼或描述生成可編輯的 Figma 設計檔案，反向輸出設計稿供設計師繼續迭代。後者是本次整合最具突破性的部分，過去幾乎所有工具都只走單向。",{"type":765,"children":2226},[2227],{"type":768,"tag":769,"props":2228,"children":2229},{},[2230,2232,2237,2239,2244],{"type":773,"value":2231},"整合支援兩個方向的轉換：",{"type":768,"tag":847,"props":2233,"children":2234},{},[2235],{"type":773,"value":2236},"Figma → Code",{"type":773,"value":2238}," 方向允許 Codex 讀取 Figma Design、Make、FigJam 的設計脈絡（元件樣式、層級結構、尺寸標注），直接生成對應前端程式碼；",{"type":768,"tag":847,"props":2240,"children":2241},{},[2242],{"type":773,"value":2243},"Code → Figma",{"type":773,"value":2245}," 方向讓開發者可以從現有 UI 程式碼或描述生成可編輯的 Figma 設計檔案，反向輸出設計稿供設計師繼續迭代。後者是本次整合最具突破性的部分，過去幾乎所有工具都只走單向。",{"title":378,"searchDepth":775,"depth":775,"links":2247},[],{"data":2249,"body":2251,"excerpt":-1,"toc":2272},{"title":378,"description":2250},"Figma 對 MCP 工具呼叫設有方案分級限制：Enterprise 方案每日 600 次、Org／Pro 開發席位每日 200 次、Starter／檢視者／協作者每月僅 6 次。超出配額後請求將被拒絕，不會自動升級計費。此設計將「AI 功能」直接綁定付費席位，意味著個人免費用戶幾乎無法在日常工作中建立穩定的工作流。",{"type":765,"children":2252},[2253,2257],{"type":768,"tag":769,"props":2254,"children":2255},{},[2256],{"type":773,"value":2250},{"type":768,"tag":840,"props":2258,"children":2259},{},[2260],{"type":768,"tag":769,"props":2261,"children":2262},{},[2263,2267,2270],{"type":768,"tag":847,"props":2264,"children":2265},{},[2266],{"type":773,"value":1388},{"type":768,"tag":853,"props":2268,"children":2269},{},[],{"type":773,"value":2271},"\n這就像在設計師的 Figma 和工程師的程式碼編輯器之間裝了一條雙向傳送帶：以前只能從設計→程式碼單向走，現在可以把寫好的程式碼「逆送」回設計稿，讓設計師繼續在熟悉的工具裡修改——前提是你付了夠多的月費。",{"title":378,"searchDepth":775,"depth":775,"links":2273},[],{"data":2275,"body":2276,"excerpt":-1,"toc":2383},{"title":378,"description":378},{"type":765,"children":2277},[2278,2282,2303,2307,2329,2333,2338,2342,2355,2359,2372,2378],{"type":768,"tag":817,"props":2279,"children":2280},{"id":1402},[2281],{"type":773,"value":1402},{"type":768,"tag":894,"props":2283,"children":2284},{},[2285,2294],{"type":768,"tag":898,"props":2286,"children":2287},{},[2288,2292],{"type":768,"tag":847,"props":2289,"children":2290},{},[2291],{"type":773,"value":1415},{"type":773,"value":2293},"：GitHub Copilot Workspace（微軟生態，缺乏 Figma 原生整合）、Cursor IDE（有視覺設計稿讀取功能但非雙向）、Vercel v0（文字→UI，無 Figma 可編輯稿輸出）",{"type":768,"tag":898,"props":2295,"children":2296},{},[2297,2301],{"type":768,"tag":847,"props":2298,"children":2299},{},[2300],{"type":773,"value":1425},{"type":773,"value":2302},"：Locofy、Anima 等 Figma 插件轉碼工具；Builder.io 的視覺→程式碼平台；Gemini CLI（同樣支援 Figma MCP，競爭同一工作流入口）",{"type":768,"tag":817,"props":2304,"children":2305},{"id":1430},[2306],{"type":773,"value":1430},{"type":768,"tag":894,"props":2308,"children":2309},{},[2310,2319],{"type":768,"tag":898,"props":2311,"children":2312},{},[2313,2317],{"type":768,"tag":847,"props":2314,"children":2315},{},[2316],{"type":773,"value":1453},{"type":773,"value":2318},"：Figma 擁有設計師社群的高黏著度，OpenAI Codex 控制了 AI 程式碼生成入口；雙方生態的交叉授權形成競品難以單獨複製的組合優勢",{"type":768,"tag":898,"props":2320,"children":2321},{},[2322,2327],{"type":768,"tag":847,"props":2323,"children":2324},{},[2325],{"type":773,"value":2326},"資料護城河",{"type":773,"value":2328},"：Codex 100 萬週活用戶的實際使用數據，可持續訓練設計↔程式碼雙向轉換模型的精確度，形成飛輪效應",{"type":768,"tag":817,"props":2330,"children":2331},{"id":1458},[2332],{"type":773,"value":1458},{"type":768,"tag":769,"props":2334,"children":2335},{},[2336],{"type":773,"value":2337},"Figma MCP 以方案分級限制工具呼叫次數，將 AI 功能綁定高階付費席位，形成向上銷售機制。OpenAI Codex 另按 API token 計費。兩層計費疊加，對企業用戶而言成本仍屬可控，但對個人開發者或 Starter 用戶形成明顯進入門檻，降低了有機傳播的速度。",{"type":768,"tag":817,"props":2339,"children":2340},{"id":1468},[2341],{"type":773,"value":1468},{"type":768,"tag":894,"props":2343,"children":2344},{},[2345,2350],{"type":768,"tag":898,"props":2346,"children":2347},{},[2348],{"type":773,"value":2349},"需同時持有 Figma 企業方案與 OpenAI API 授權，IT 採購決策鏈較長，評估周期可能達 3-6 個月",{"type":768,"tag":898,"props":2351,"children":2352},{},[2353],{"type":773,"value":2354},"設計稿透過遠端 MCP 傳遞涉及資料主權疑慮，金融、醫療等高合規產業需額外進行資安審查",{"type":768,"tag":817,"props":2356,"children":2357},{"id":1491},[2358],{"type":773,"value":1491},{"type":768,"tag":894,"props":2360,"children":2361},{},[2362,2367],{"type":768,"tag":898,"props":2363,"children":2364},{},[2365],{"type":773,"value":2366},"Figma 插件生態（Locofy、Anima 等）的商業模式受到威脅，MCP 原生整合可能逐步取代付費插件的市場空間",{"type":768,"tag":898,"props":2368,"children":2369},{},[2370],{"type":773,"value":2371},"設計師與前端工程師的職責邊界將進一步模糊，「能寫 code 的設計師」或「理解設計系統的全端工程師」需求上升",{"type":768,"tag":817,"props":2373,"children":2375},{"id":2374},"判決生態卡位戰成功設計程式碼雙入口已被兩強壟斷",[2376],{"type":773,"value":2377},"判決：生態卡位戰成功（設計×程式碼雙入口已被兩強壟斷）",{"type":768,"tag":769,"props":2379,"children":2380},{},[2381],{"type":773,"value":2382},"OpenAI 與 Figma 此舉不是在創造新市場，而是在 AI 工作流中搶占設計→程式碼這個高頻接觸點。對 Figma 而言，MCP 整合鞏固了其作為「設計稿唯一事實來源」的地位，並透過配額機制將 AI 功能變現；對 OpenAI 而言，Codex 的應用場景從純程式碼延伸至設計迭代，進一步拉高用戶黏著度。短期內這仍是新鮮整合，但雙向傳送帶一旦被開發者工作流採用，切換成本將大幅提高，護城河效應會隨時間持續加深。",{"title":378,"searchDepth":775,"depth":775,"links":2384},[],{"data":2386,"body":2387,"excerpt":-1,"toc":2399},{"title":378,"description":378},{"type":765,"children":2388},[2389,2394],{"type":768,"tag":817,"props":2390,"children":2392},{"id":2391},"用量成長數據",[2393],{"type":773,"value":2391},{"type":768,"tag":769,"props":2395,"children":2396},{},[2397],{"type":773,"value":2398},"OpenAI 報告 Codex 目前擁有超過 100 萬週活躍用戶，自 2026 年初以來使用量成長超過 400%，顯示 Codex CLI 的採用率正在加速。然而本次 Figma 整合剛於 2026-02-26 發布，目前尚無公開的設計↔程式碼轉換精確度、往返一致性或元件還原度的基準測試數據，實際效果需待社群進行獨立評測後才有更清晰的參考依據。",{"title":378,"searchDepth":775,"depth":775,"links":2400},[],{"data":2402,"body":2403,"excerpt":-1,"toc":2424},{"title":378,"description":378},{"type":765,"children":2404},[2405],{"type":768,"tag":894,"props":2406,"children":2407},{},[2408,2412,2416,2420],{"type":768,"tag":898,"props":2409,"children":2410},{},[2411],{"type":773,"value":315},{"type":768,"tag":898,"props":2413,"children":2414},{},[2415],{"type":773,"value":316},{"type":768,"tag":898,"props":2417,"children":2418},{},[2419],{"type":773,"value":317},{"type":768,"tag":898,"props":2421,"children":2422},{},[2423],{"type":773,"value":318},{"title":378,"searchDepth":775,"depth":775,"links":2425},[],{"data":2427,"body":2428,"excerpt":-1,"toc":2441},{"title":378,"description":378},{"type":765,"children":2429},[2430],{"type":768,"tag":894,"props":2431,"children":2432},{},[2433,2437],{"type":768,"tag":898,"props":2434,"children":2435},{},[2436],{"type":773,"value":320},{"type":768,"tag":898,"props":2438,"children":2439},{},[2440],{"type":773,"value":321},{"title":378,"searchDepth":775,"depth":775,"links":2442},[],{"data":2444,"body":2445,"excerpt":-1,"toc":2451},{"title":378,"description":325},{"type":765,"children":2446},[2447],{"type":768,"tag":769,"props":2448,"children":2449},{},[2450],{"type":773,"value":325},{"title":378,"searchDepth":775,"depth":775,"links":2452},[],{"data":2454,"body":2455,"excerpt":-1,"toc":2461},{"title":378,"description":326},{"type":765,"children":2456},[2457],{"type":768,"tag":769,"props":2458,"children":2459},{},[2460],{"type":773,"value":326},{"title":378,"searchDepth":775,"depth":775,"links":2462},[],{"data":2464,"body":2465,"excerpt":-1,"toc":2471},{"title":378,"description":366},{"type":765,"children":2466},[2467],{"type":768,"tag":769,"props":2468,"children":2469},{},[2470],{"type":773,"value":366},{"title":378,"searchDepth":775,"depth":775,"links":2472},[],{"data":2474,"body":2475,"excerpt":-1,"toc":2481},{"title":378,"description":370},{"type":765,"children":2476},[2477],{"type":768,"tag":769,"props":2478,"children":2479},{},[2480],{"type":773,"value":370},{"title":378,"searchDepth":775,"depth":775,"links":2482},[],{"data":2484,"body":2485,"excerpt":-1,"toc":2491},{"title":378,"description":373},{"type":765,"children":2486},[2487],{"type":768,"tag":769,"props":2488,"children":2489},{},[2490],{"type":773,"value":373},{"title":378,"searchDepth":775,"depth":775,"links":2492},[],{"data":2494,"body":2495,"excerpt":-1,"toc":2501},{"title":378,"description":375},{"type":765,"children":2496},[2497],{"type":768,"tag":769,"props":2498,"children":2499},{},[2500],{"type":773,"value":375},{"title":378,"searchDepth":775,"depth":775,"links":2502},[],{"data":2504,"body":2506,"excerpt":-1,"toc":2545},{"title":378,"description":2505},"AI Agent 的能力上限，長期被「如何讓它理解我們的工作方式」卡住。提示詞可以寫，系統指令可以調，但這些知識散落在各工具的設定頁，換一個 AI 平台就要重來一遍，企業的最佳實踐也難以模組化傳承給整個團隊。",{"type":765,"children":2507},[2508,2512,2518,2523,2529,2534,2540],{"type":768,"tag":769,"props":2509,"children":2510},{},[2511],{"type":773,"value":2505},{"type":768,"tag":817,"props":2513,"children":2515},{"id":2514},"痛點-1ai-工具的情境知識格式各自為政",[2516],{"type":773,"value":2517},"痛點 1：AI 工具的情境知識格式各自為政",{"type":768,"tag":769,"props":2519,"children":2520},{},[2521],{"type":773,"value":2522},"Claude 有 CLAUDE.md，Cursor 有 .cursorrules，GitHub Copilot 有 copilot-instructions.md——每個平台都要求開發者用不同格式複製一次領域知識。跨工具複用幾乎不可能，企業投入大量工程時間做的 AI 調整，切換工具後全部歸零，形成嚴重的知識重複建設問題。",{"type":768,"tag":817,"props":2524,"children":2526},{"id":2525},"痛點-2團隊-ai-最佳實踐難以結構化共享",[2527],{"type":773,"value":2528},"痛點 2：團隊 AI 最佳實踐難以結構化共享",{"type":768,"tag":769,"props":2530,"children":2531},{},[2532],{"type":773,"value":2533},"即便在同一工具內，個人積累的「有效提示詞」也無法輕易分享給整個團隊。新成員往往需要數週才能摸索出讓 Agent 在特定技術棧上表現良好的指令模式。缺乏標準化格式，讓組織內的 AI 使用知識無法形成可複用的制度資本，資深工程師的隱性經驗也難以傳承。",{"type":768,"tag":817,"props":2535,"children":2537},{"id":2536},"舊解法claudemd-全域設定",[2538],{"type":773,"value":2539},"舊解法：CLAUDE.md 全域設定",{"type":768,"tag":769,"props":2541,"children":2542},{},[2543],{"type":773,"value":2544},"過去 Anthropic 提供 CLAUDE.md 讓開發者在專案根目錄放置指令，這確實有效，但本質是平坦的單一檔案，難以按功能模組化，不支援附帶腳本、參考資料或二進位資產的複合結構，更無法跨 AI 工具互通，是解決了個人工作流卻未解決生態孤島的方案。",{"title":378,"searchDepth":775,"depth":775,"links":2546},[],{"data":2548,"body":2550,"excerpt":-1,"toc":2571},{"title":378,"description":2549},"Agent Skills 規格的核心設計哲學是「漸進式揭露 (progressive disclosure) 」——AI 先讀取輕量的 metadata，確認技能與當前任務相關後才載入完整指令，最後在需要時才拉取外部資源，有效避免浪費寶貴的 context window。",{"type":765,"children":2551},[2552,2556],{"type":768,"tag":769,"props":2553,"children":2554},{},[2555],{"type":773,"value":2549},{"type":768,"tag":840,"props":2557,"children":2558},{},[2559],{"type":768,"tag":769,"props":2560,"children":2561},{},[2562,2566,2569],{"type":768,"tag":847,"props":2563,"children":2564},{},[2565],{"type":773,"value":851},{"type":768,"tag":853,"props":2567,"children":2568},{},[],{"type":773,"value":2570},"\nprogressive disclosure（漸進式揭露）：一種 UX 與系統設計原則，指資訊按需分層提供，使用者（或 AI）只在需要時才接觸下一層細節，以減少認知負荷或計算成本。",{"title":378,"searchDepth":775,"depth":775,"links":2572},[],{"data":2574,"body":2576,"excerpt":-1,"toc":2630},{"title":378,"description":2575},"每個技能是一個資料夾，根目錄必須有 SKILL.md。YAML frontmatter 定義兩個必要欄位：name 和 description，讓 AI 能快速判斷是否啟用此技能。其餘欄位如 license、compatibility、metadata 和實驗性的 allowed-tools 均為選填，讓技能作者在不破壞基本規格相容性的前提下擴充附加功能。",{"type":765,"children":2577},[2578],{"type":768,"tag":769,"props":2579,"children":2580},{},[2581,2583,2589,2591,2597,2599,2605,2607,2613,2614,2620,2622,2628],{"type":773,"value":2582},"每個技能是一個資料夾，根目錄必須有 SKILL.md。YAML frontmatter 定義兩個必要欄位：",{"type":768,"tag":875,"props":2584,"children":2586},{"className":2585},[],[2587],{"type":773,"value":2588},"name",{"type":773,"value":2590}," 和 ",{"type":768,"tag":875,"props":2592,"children":2594},{"className":2593},[],[2595],{"type":773,"value":2596},"description",{"type":773,"value":2598},"，讓 AI 能快速判斷是否啟用此技能。其餘欄位如 ",{"type":768,"tag":875,"props":2600,"children":2602},{"className":2601},[],[2603],{"type":773,"value":2604},"license",{"type":773,"value":2606},"、",{"type":768,"tag":875,"props":2608,"children":2610},{"className":2609},[],[2611],{"type":773,"value":2612},"compatibility",{"type":773,"value":2606},{"type":768,"tag":875,"props":2615,"children":2617},{"className":2616},[],[2618],{"type":773,"value":2619},"metadata",{"type":773,"value":2621}," 和實驗性的 ",{"type":768,"tag":875,"props":2623,"children":2625},{"className":2624},[],[2626],{"type":773,"value":2627},"allowed-tools",{"type":773,"value":2629}," 均為選填，讓技能作者在不破壞基本規格相容性的前提下擴充附加功能。",{"title":378,"searchDepth":775,"depth":775,"links":2631},[],{"data":2633,"body":2635,"excerpt":-1,"toc":2682},{"title":378,"description":2634},"技能資料夾除 SKILL.md 外，可包含三類選填子目錄：",{"type":765,"children":2636},[2637,2641,2677],{"type":768,"tag":769,"props":2638,"children":2639},{},[2640],{"type":773,"value":2634},{"type":768,"tag":894,"props":2642,"children":2643},{},[2644,2655,2666],{"type":768,"tag":898,"props":2645,"children":2646},{},[2647,2653],{"type":768,"tag":875,"props":2648,"children":2650},{"className":2649},[],[2651],{"type":773,"value":2652},"scripts/",{"type":773,"value":2654},"：可執行的自動化腳本",{"type":768,"tag":898,"props":2656,"children":2657},{},[2658,2664],{"type":768,"tag":875,"props":2659,"children":2661},{"className":2660},[],[2662],{"type":773,"value":2663},"references/",{"type":773,"value":2665},"：技能執行時可查閱的靜態文件",{"type":768,"tag":898,"props":2667,"children":2668},{},[2669,2675],{"type":768,"tag":875,"props":2670,"children":2672},{"className":2671},[],[2673],{"type":773,"value":2674},"assets/",{"type":773,"value":2676},"：圖片、範本等二進位資源",{"type":768,"tag":769,"props":2678,"children":2679},{},[2680],{"type":773,"value":2681},"這使得「前端設計技能」可以附帶完整的設計規範文件，「部署技能」可以附帶 CI/CD 腳本範本，技能從純指令升級為自包含的工作流程套件。",{"title":378,"searchDepth":775,"depth":775,"links":2683},[],{"data":2685,"body":2687,"excerpt":-1,"toc":2741},{"title":378,"description":2686},"2025-12-18 Anthropic 將規格發布為開放標準 (agentskills.io) ，同日 GitHub Copilot 宣布相容 .claude/skills 目錄。規格層面，技能路徑尚有社群討論 (.claude/skills/ vs .agents/skills/) ，但跨平台相容的方向已明確確立：同一套技能資料夾可被多個 AI 工具載入，無需重複維護。",{"type":765,"children":2688},[2689,2718],{"type":768,"tag":769,"props":2690,"children":2691},{},[2692,2694,2700,2702,2708,2710,2716],{"type":773,"value":2693},"2025-12-18 Anthropic 將規格發布為開放標準 (agentskills.io) ，同日 GitHub Copilot 宣布相容 ",{"type":768,"tag":875,"props":2695,"children":2697},{"className":2696},[],[2698],{"type":773,"value":2699},".claude/skills",{"type":773,"value":2701}," 目錄。規格層面，技能路徑尚有社群討論 (",{"type":768,"tag":875,"props":2703,"children":2705},{"className":2704},[],[2706],{"type":773,"value":2707},".claude/skills/",{"type":773,"value":2709}," vs ",{"type":768,"tag":875,"props":2711,"children":2713},{"className":2712},[],[2714],{"type":773,"value":2715},".agents/skills/",{"type":773,"value":2717},") ，但跨平台相容的方向已明確確立：同一套技能資料夾可被多個 AI 工具載入，無需重複維護。",{"type":768,"tag":840,"props":2719,"children":2720},{},[2721],{"type":768,"tag":769,"props":2722,"children":2723},{},[2724,2728,2731,2733,2739],{"type":768,"tag":847,"props":2725,"children":2726},{},[2727],{"type":773,"value":1388},{"type":768,"tag":853,"props":2729,"children":2730},{},[],{"type":773,"value":2732},"\n把 Agent Skills 想成 npm 套件，但裝的不是程式碼而是「工作方式」。寫一次 ",{"type":768,"tag":875,"props":2734,"children":2736},{"className":2735},[],[2737],{"type":773,"value":2738},"SKILL.md",{"type":773,"value":2740}," 就像發布一個 package，任何支援此規格的 AI 工具都能 \"install\" 這套領域知識，一次撰寫，多處生效。",{"title":378,"searchDepth":775,"depth":775,"links":2742},[],{"data":2744,"body":2745,"excerpt":-1,"toc":2856},{"title":378,"description":378},{"type":765,"children":2746},[2747,2751,2772,2776,2797,2801,2806,2810,2828,2832,2845,2851],{"type":768,"tag":817,"props":2748,"children":2749},{"id":1402},[2750],{"type":773,"value":1402},{"type":768,"tag":894,"props":2752,"children":2753},{},[2754,2763],{"type":768,"tag":898,"props":2755,"children":2756},{},[2757,2761],{"type":768,"tag":847,"props":2758,"children":2759},{},[2760],{"type":773,"value":1415},{"type":773,"value":2762},"：Cursor 的 .cursorrules 系統、各家 AI IDE 的私有自訂指令機制（目前均為平台綁定格式）",{"type":768,"tag":898,"props":2764,"children":2765},{},[2766,2770],{"type":768,"tag":847,"props":2767,"children":2768},{},[2769],{"type":773,"value":1425},{"type":773,"value":2771},"：LangChain 的 prompt templates、Dust.tt 的知識庫配置、企業級 RAG 系統（如 Glean）提供的情境知識注入方案",{"type":768,"tag":817,"props":2773,"children":2774},{"id":1430},[2775],{"type":773,"value":1430},{"type":768,"tag":894,"props":2777,"children":2778},{},[2779,2788],{"type":768,"tag":898,"props":2780,"children":2781},{},[2782,2786],{"type":768,"tag":847,"props":2783,"children":2784},{},[2785],{"type":773,"value":1453},{"type":773,"value":2787},"：anthropics/skills 倉庫作為官方技能目錄，社群貢獻的技能累積量形成先發優勢；Andrew Ng 等 AI 教育者為此規格開設課程，大幅提升標準採用率與認可度",{"type":768,"tag":898,"props":2789,"children":2790},{},[2791,2795],{"type":768,"tag":847,"props":2792,"children":2793},{},[2794],{"type":773,"value":1443},{"type":773,"value":2796},"：progressive disclosure 的 context 效率設計，使技能格式在長任務中比平坦 CLAUDE.md 更具成本優勢；GitHub Copilot 相容性則打破了「技能綁定 Claude」的採用疑慮",{"type":768,"tag":817,"props":2798,"children":2799},{"id":1458},[2800],{"type":773,"value":1458},{"type":768,"tag":769,"props":2802,"children":2803},{},[2804],{"type":773,"value":2805},"規格本身開放免費，anthropics/skills 倉庫中大多數技能採 Apache-2.0 授權可商業使用。文件技能（docx/pdf/pptx/xlsx 處理）採 source-available 而非完全開源，暗示 Anthropic 保留部分商業化空間。企業建立私有技能目錄的技術成本極低（純資料夾結構），但維護情境知識品質所需的人力成本不可低估。",{"type":768,"tag":817,"props":2807,"children":2808},{"id":1468},[2809],{"type":773,"value":1468},{"type":768,"tag":894,"props":2811,"children":2812},{},[2813,2818,2823],{"type":768,"tag":898,"props":2814,"children":2815},{},[2816],{"type":773,"value":2817},"技能路徑標準尚未完全定案，企業可能顧慮未來規格收斂後的遷移成本",{"type":768,"tag":898,"props":2819,"children":2820},{},[2821],{"type":773,"value":2822},"缺乏類似 npm audit 的技能安全審查機制，企業安全團隊可能要求全面審查社群來源技能的指令內容",{"type":768,"tag":898,"props":2824,"children":2825},{},[2826],{"type":773,"value":2827},"與現有知識管理系統（Confluence、Notion）的雙向同步路徑尚未成熟，知識更新需要手動維護兩套來源",{"type":768,"tag":817,"props":2829,"children":2830},{"id":1491},[2831],{"type":773,"value":1491},{"type":768,"tag":894,"props":2833,"children":2834},{},[2835,2840],{"type":768,"tag":898,"props":2836,"children":2837},{},[2838],{"type":773,"value":2839},"若 Agent Skills 成為業界標準，AI 工具廠商將被迫宣布支援此規格，否則面臨生態孤立風險，這反過來持續強化 Anthropic 的生態話語權",{"type":768,"tag":898,"props":2841,"children":2842},{},[2843],{"type":773,"value":2844},"垂直領域技能市集 (Skill Marketplace) 的商業模式可期——類似 VSCode Extension Marketplace，法律合規、金融分析、特定框架等付費技能套件將逐步出現",{"type":768,"tag":817,"props":2846,"children":2848},{"id":2847},"判決值得現在跟進低成本卡位高槓桿的生態先機",[2849],{"type":773,"value":2850},"判決：值得現在跟進（低成本卡位、高槓桿的生態先機）",{"type":768,"tag":769,"props":2852,"children":2853},{},[2854],{"type":773,"value":2855},"Agent Skills 的採用成本極低（一個 Markdown 檔案），而標準一旦確立，後進者的整合成本將顯著上升。現在跟進等同於以最小代價參與一個即將成為業界基礎設施的規格制定期，同時積累的技能資產在跨工具互通成熟後將直接轉化為生產力紅利。",{"title":378,"searchDepth":775,"depth":775,"links":2857},[],{"data":2859,"body":2860,"excerpt":-1,"toc":2881},{"title":378,"description":378},{"type":765,"children":2861},[2862],{"type":768,"tag":894,"props":2863,"children":2864},{},[2865,2869,2873,2877],{"type":768,"tag":898,"props":2866,"children":2867},{},[2868],{"type":773,"value":381},{"type":768,"tag":898,"props":2870,"children":2871},{},[2872],{"type":773,"value":382},{"type":768,"tag":898,"props":2874,"children":2875},{},[2876],{"type":773,"value":383},{"type":768,"tag":898,"props":2878,"children":2879},{},[2880],{"type":773,"value":384},{"title":378,"searchDepth":775,"depth":775,"links":2882},[],{"data":2884,"body":2885,"excerpt":-1,"toc":2898},{"title":378,"description":378},{"type":765,"children":2886},[2887],{"type":768,"tag":894,"props":2888,"children":2889},{},[2890,2894],{"type":768,"tag":898,"props":2891,"children":2892},{},[2893],{"type":773,"value":386},{"type":768,"tag":898,"props":2895,"children":2896},{},[2897],{"type":773,"value":387},{"title":378,"searchDepth":775,"depth":775,"links":2899},[],{"data":2901,"body":2902,"excerpt":-1,"toc":2908},{"title":378,"description":391},{"type":765,"children":2903},[2904],{"type":768,"tag":769,"props":2905,"children":2906},{},[2907],{"type":773,"value":391},{"title":378,"searchDepth":775,"depth":775,"links":2909},[],{"data":2911,"body":2912,"excerpt":-1,"toc":2918},{"title":378,"description":392},{"type":765,"children":2913},[2914],{"type":768,"tag":769,"props":2915,"children":2916},{},[2917],{"type":773,"value":392},{"title":378,"searchDepth":775,"depth":775,"links":2919},[],{"data":2921,"body":2922,"excerpt":-1,"toc":2928},{"title":378,"description":393},{"type":765,"children":2923},[2924],{"type":768,"tag":769,"props":2925,"children":2926},{},[2927],{"type":773,"value":393},{"title":378,"searchDepth":775,"depth":775,"links":2929},[],{"data":2931,"body":2932,"excerpt":-1,"toc":3002},{"title":378,"description":378},{"type":765,"children":2933},[2934,2940,2953,2976,2991,2997],{"type":768,"tag":817,"props":2935,"children":2937},{"id":2936},"核心升級以-flash-速度達到-pro-品質",[2938],{"type":773,"value":2939},"核心升級：以 Flash 速度達到 Pro 品質",{"type":768,"tag":769,"props":2941,"children":2942},{},[2943,2945,2951],{"type":773,"value":2944},"Google 於 2026 年 2 月 26 日發布 Nano Banana 2（API 識別碼：",{"type":768,"tag":875,"props":2946,"children":2948},{"className":2947},[],[2949],{"type":773,"value":2950},"gemini-3.1-flash-image-preview",{"type":773,"value":2952},"），定位為「Flash 速度、Pro 品質」的圖像生成模型，已同步在 Gemini 應用程式、Google Search、AI Studio／API、Vertex AI 及 Google Ads 全面推出。主要能力包括：",{"type":768,"tag":894,"props":2954,"children":2955},{},[2956,2961,2966,2971],{"type":768,"tag":898,"props":2957,"children":2958},{},[2959],{"type":773,"value":2960},"即時網路搜尋與圖片搜尋接地，生成內容可反映最新世界知識",{"type":768,"tag":898,"props":2962,"children":2963},{},[2964],{"type":773,"value":2965},"精確文字渲染與多語翻譯",{"type":768,"tag":898,"props":2967,"children":2968},{},[2969],{"type":773,"value":2970},"最多支援 5 個角色、14 個物件的主體一致性",{"type":768,"tag":898,"props":2972,"children":2973},{},[2974],{"type":773,"value":2975},"輸出解析度從 512px 至 4K，適合量產場景",{"type":768,"tag":840,"props":2977,"children":2978},{},[2979],{"type":768,"tag":769,"props":2980,"children":2981},{},[2982,2986,2989],{"type":768,"tag":847,"props":2983,"children":2984},{},[2985],{"type":773,"value":851},{"type":768,"tag":853,"props":2987,"children":2988},{},[],{"type":773,"value":2990},"\nGrounding（接地）：讓模型在生成時查詢外部真實資料（如 Google 搜尋），而非僅依賴訓練時的靜態知識。",{"type":768,"tag":817,"props":2992,"children":2994},{"id":2993},"溯源機制synthid-與-c2pa",[2995],{"type":773,"value":2996},"溯源機制：SynthID 與 C2PA",{"type":768,"tag":769,"props":2998,"children":2999},{},[3000],{"type":773,"value":3001},"所有生成圖像均內嵌 SynthID 不可見浮水印，Google 表示自 2025 年 11 月以來已被驗證逾 2,000 萬次；C2PA 內容憑證功能也即將登陸 Gemini 應用程式。已知限制包含小字渲染不穩定、角色一致性在長工作流中可能漂移，以及偶發性逾時問題。",{"title":378,"searchDepth":775,"depth":775,"links":3003},[],{"data":3005,"body":3007,"excerpt":-1,"toc":3025},{"title":378,"description":3006},"模型支援多模態輸入，context window 達 100 萬 token，可接受最多 14 張參考圖像進行多圖工作流。目前仍為 preview 狀態，建議在生產環境加入重試機制與輸出品質驗證邏輯。SynthID 浮水印可透過 google-deepmind/synthid-text 驗證；C2PA 介接尚未上線，溯源暫以 SynthID API 為主。",{"type":765,"children":3008},[3009],{"type":768,"tag":769,"props":3010,"children":3011},{},[3012,3014,3023],{"type":773,"value":3013},"模型支援多模態輸入，context window 達 100 萬 token，可接受最多 14 張參考圖像進行多圖工作流。目前仍為 preview 狀態，建議在生產環境加入重試機制與輸出品質驗證邏輯。SynthID 浮水印可透過 ",{"type":768,"tag":3015,"props":3016,"children":3020},"a",{"href":3017,"rel":3018},"https://github.com/google-deepmind/synthid-text",[3019],"nofollow",[3021],{"type":773,"value":3022},"google-deepmind/synthid-text",{"type":773,"value":3024}," 驗證；C2PA 介接尚未上線，溯源暫以 SynthID API 為主。",{"title":378,"searchDepth":775,"depth":775,"links":3026},[],{"data":3028,"body":3029,"excerpt":-1,"toc":3035},{"title":378,"description":439},{"type":765,"children":3030},[3031],{"type":768,"tag":769,"props":3032,"children":3033},{},[3034],{"type":773,"value":439},{"title":378,"searchDepth":775,"depth":775,"links":3036},[],{"data":3038,"body":3039,"excerpt":-1,"toc":3071},{"title":378,"description":378},{"type":765,"children":3040},[3041,3046],{"type":768,"tag":817,"props":3042,"children":3044},{"id":3043},"效能基準",[3045],{"type":773,"value":3043},{"type":768,"tag":894,"props":3047,"children":3048},{},[3049,3054,3059],{"type":768,"tag":898,"props":3050,"children":3051},{},[3052],{"type":773,"value":3053},"GenAI-Bench Overall Preference：1079.0 ± 7.0（含 Thinking、文字搜尋、圖片搜尋三項增強變體）",{"type":768,"tag":898,"props":3055,"children":3056},{},[3057],{"type":773,"value":3058},"GenAI-Bench Visual Quality：1140.0 ± 6.0",{"type":768,"tag":898,"props":3060,"children":3061},{},[3062,3064,3069],{"type":773,"value":3063},"Artificial Analysis Image Arena 文字生圖排名：",{"type":768,"tag":847,"props":3065,"children":3066},{},[3067],{"type":773,"value":3068},"第 1 名",{"type":773,"value":3070},"（定價約為 Nano Banana Pro 的一半）",{"title":378,"searchDepth":775,"depth":775,"links":3072},[],{"data":3074,"body":3075,"excerpt":-1,"toc":3114},{"title":378,"description":378},{"type":765,"children":3076},[3077,3083,3088,3094,3099],{"type":768,"tag":817,"props":3078,"children":3080},{"id":3079},"合作重點主權-ai-的企業交付",[3081],{"type":773,"value":3082},"合作重點：主權 AI 的企業交付",{"type":768,"tag":769,"props":3084,"children":3085},{},[3086],{"type":773,"value":3087},"Accenture 與 Mistral AI 於 2026 年 2 月 26 日宣布多年策略合作，目標是在歐洲及全球為企業大規模部署進階 AI 解決方案。雙方將聯合開發企業 AI 方案，Accenture 亦成為 Mistral 客戶並在內部導入 Mistral AI Studio。",{"type":768,"tag":817,"props":3089,"children":3091},{"id":3090},"架構多押注策略下的主控優先",[3092],{"type":773,"value":3093},"架構：多押注策略下的主控優先",{"type":768,"tag":769,"props":3095,"children":3096},{},[3097],{"type":773,"value":3098},"合作特別強調「主權 AI」定位，針對歐洲資料在地化與監管需求提供安全、大規模的合規部署。交付模型結合 Mistral 的模型能力與 Accenture 的企業架構、治理及規模化專長，並含客戶培訓認證、微調與運維支援。值得注意的是，Accenture 同期亦與 OpenAI(Frontier Alliances) 及 Anthropic 建立多年合作，採「多押注」而非獨家策略。財務條款與合約期間均未公開。",{"type":768,"tag":840,"props":3100,"children":3101},{},[3102],{"type":768,"tag":769,"props":3103,"children":3104},{},[3105,3109,3112],{"type":768,"tag":847,"props":3106,"children":3107},{},[3108],{"type":773,"value":851},{"type":768,"tag":853,"props":3110,"children":3111},{},[],{"type":773,"value":3113},"\n主權 AI(Sovereign AI) ：資料與模型運算保留在特定地理區域或受特定司法管轄，符合當地法規要求的 AI 部署方式。",{"title":378,"searchDepth":775,"depth":775,"links":3115},[],{"data":3117,"body":3118,"excerpt":-1,"toc":3124},{"title":378,"description":474},{"type":765,"children":3119},[3120],{"type":768,"tag":769,"props":3121,"children":3122},{},[3123],{"type":773,"value":474},{"title":378,"searchDepth":775,"depth":775,"links":3125},[],{"data":3127,"body":3128,"excerpt":-1,"toc":3134},{"title":378,"description":475},{"type":765,"children":3129},[3130],{"type":768,"tag":769,"props":3131,"children":3132},{},[3133],{"type":773,"value":475},{"title":378,"searchDepth":775,"depth":775,"links":3135},[],{"data":3137,"body":3138,"excerpt":-1,"toc":3238},{"title":378,"description":378},{"type":765,"children":3139},[3140,3146,3179,3185,3190,3233],{"type":768,"tag":817,"props":3141,"children":3143},{"id":3142},"openai-的四大戰略困境",[3144],{"type":773,"value":3145},"OpenAI 的四大戰略困境",{"type":768,"tag":769,"props":3147,"children":3148},{},[3149,3151,3156,3158,3163,3165,3170,3172,3177],{"type":773,"value":3150},"Benedict Evans 在 2026 年 2 月分析指出，OpenAI 面臨四個核心挑戰：",{"type":768,"tag":847,"props":3152,"children":3153},{},[3154],{"type":773,"value":3155},"模型層護城河薄弱",{"type":773,"value":3157},"（競爭者技術可快速追上）、",{"type":768,"tag":847,"props":3159,"children":3160},{},[3161],{"type":773,"value":3162},"日常使用黏著度不足",{"type":773,"value":3164},"（ChatGPT 尚未成為高頻生活習慣）、",{"type":768,"tag":847,"props":3166,"children":3167},{},[3168],{"type":773,"value":3169},"極端資本支出壓力",{"type":773,"value":3171},"（Stargate 計畫承諾超過 4,500 億美元基礎設施投資）、以及",{"type":768,"tag":847,"props":3173,"children":3174},{},[3175],{"type":773,"value":3176},"產品掌控力不確定",{"type":773,"value":3178},"（應用層競爭激烈）。與此同時，DeepSeek-R1 的開源揭示了另一威脅——以更低成本複製強推理能力，進一步壓縮模型層的差異化空間。",{"type":768,"tag":817,"props":3180,"children":3182},{"id":3181},"openai-的應對動作",[3183],{"type":773,"value":3184},"OpenAI 的應對動作",{"type":768,"tag":769,"props":3186,"children":3187},{},[3188],{"type":773,"value":3189},"面對上述壓力，OpenAI 採取多管齊下策略：",{"type":768,"tag":894,"props":3191,"children":3192},{},[3193,3203,3213,3223],{"type":768,"tag":898,"props":3194,"children":3195},{},[3196,3201],{"type":768,"tag":847,"props":3197,"children":3198},{},[3199],{"type":773,"value":3200},"低價方案",{"type":773,"value":3202},"：推出每月 8 美元的 ChatGPT Go，覆蓋 171 個國家",{"type":768,"tag":898,"props":3204,"children":3205},{},[3206,3211],{"type":768,"tag":847,"props":3207,"children":3208},{},[3209],{"type":773,"value":3210},"廣告測試",{"type":773,"value":3212},"：在 Free 和 Go 方案對登入用戶開放廣告，付費方案維持無廣告",{"type":768,"tag":898,"props":3214,"children":3215},{},[3216,3221],{"type":768,"tag":847,"props":3217,"children":3218},{},[3219],{"type":773,"value":3220},"垂直整合",{"type":773,"value":3222},"：ChatGPT Search（全用戶開放）與 Operator 代理模式（整合進 ChatGPT）",{"type":768,"tag":898,"props":3224,"children":3225},{},[3226,3231],{"type":768,"tag":847,"props":3227,"children":3228},{},[3229],{"type":773,"value":3230},"基礎設施卡位",{"type":773,"value":3232},"：Stargate 計畫規劃超過 8 GW 算力、逾 4,500 億美元投資",{"type":768,"tag":769,"props":3234,"children":3235},{},[3236],{"type":773,"value":3237},"目前基本面數據仍強：週活躍用戶超過 4 億、年化營收達 100 億美元、估值 5,000 億美元。",{"title":378,"searchDepth":775,"depth":775,"links":3239},[],{"data":3241,"body":3242,"excerpt":-1,"toc":3248},{"title":378,"description":503},{"type":765,"children":3243},[3244],{"type":768,"tag":769,"props":3245,"children":3246},{},[3247],{"type":773,"value":503},{"title":378,"searchDepth":775,"depth":775,"links":3249},[],{"data":3251,"body":3252,"excerpt":-1,"toc":3258},{"title":378,"description":504},{"type":765,"children":3253},[3254],{"type":768,"tag":769,"props":3255,"children":3256},{},[3257],{"type":773,"value":504},{"title":378,"searchDepth":775,"depth":775,"links":3259},[],{"data":3261,"body":3262,"excerpt":-1,"toc":3301},{"title":378,"description":378},{"type":765,"children":3263},[3264,3270,3275,3290,3296],{"type":768,"tag":817,"props":3265,"children":3267},{"id":3266},"_122b-總參數10b-啟動moe-讓大模型進入消費級",[3268],{"type":773,"value":3269},"122B 總參數、10B 啟動：MoE 讓大模型進入消費級",{"type":768,"tag":769,"props":3271,"children":3272},{},[3273],{"type":773,"value":3274},"Alibaba Cloud 推出 Qwen3.5 中型系列，旗艦為 Qwen3.5-122B-A10B——122B 總參數中每次推論僅啟動 10B，共設 256 個專家 (8 routed + 1 shared) ，原生支援 262k tokens 上下文，最高可擴展至約 100 萬 tokens。",{"type":768,"tag":840,"props":3276,"children":3277},{},[3278],{"type":768,"tag":769,"props":3279,"children":3280},{},[3281,3285,3288],{"type":768,"tag":847,"props":3282,"children":3283},{},[3284],{"type":773,"value":851},{"type":768,"tag":853,"props":3286,"children":3287},{},[],{"type":773,"value":3289},"\nMoE(Mixture of Experts) ：模型包含多個「專家」子網路，每次推論只啟動其中少數幾個，使超大模型能以較少記憶體和算力運行。",{"type":768,"tag":817,"props":3291,"children":3293},{"id":3292},"實測72gb-vram-三張-3090-就夠了",[3294],{"type":773,"value":3295},"實測：72GB VRAM 三張 3090 就夠了",{"type":768,"tag":769,"props":3297,"children":3298},{},[3299],{"type":773,"value":3300},"社群用 3 張 RTX 3090（共 72GB VRAM）成功部署 Q3_K 量化版，達到約 25 tok/s、可跑 120k 上下文。模型預設開啟思考模式，連簡單指令也會展開推理鏈；社群建議調整採樣參數（temperature 0.6、top-k 20、top-p 0.8）來緩解過度思考。",{"title":378,"searchDepth":775,"depth":775,"links":3302},[],{"data":3304,"body":3305,"excerpt":-1,"toc":3311},{"title":378,"description":535},{"type":765,"children":3306},[3307],{"type":768,"tag":769,"props":3308,"children":3309},{},[3310],{"type":773,"value":535},{"title":378,"searchDepth":775,"depth":775,"links":3312},[],{"data":3314,"body":3315,"excerpt":-1,"toc":3321},{"title":378,"description":536},{"type":765,"children":3316},[3317],{"type":768,"tag":769,"props":3318,"children":3319},{},[3320],{"type":773,"value":536},{"title":378,"searchDepth":775,"depth":775,"links":3322},[],{"data":3324,"body":3325,"excerpt":-1,"toc":3350},{"title":378,"description":378},{"type":765,"children":3326},[3327,3332],{"type":768,"tag":817,"props":3328,"children":3330},{"id":3329},"社群實測推論速度",[3331],{"type":773,"value":3329},{"type":768,"tag":894,"props":3333,"children":3334},{},[3335,3340,3345],{"type":768,"tag":898,"props":3336,"children":3337},{},[3338],{"type":773,"value":3339},"Q3_K（3x RTX 3090，72GB VRAM）：~25 tok/s，最大上下文約 120k",{"type":768,"tag":898,"props":3341,"children":3342},{},[3343],{"type":773,"value":3344},"Q4_K_XL（RTX 5090 + Ryzen 9 9950X3D，128GB DDR5）：34–36 tok/s，最大上下文 256k",{"type":768,"tag":898,"props":3346,"children":3347},{},[3348],{"type":773,"value":3349},"Q8_K_XL（同規格）：16–18 tok/s，最大上下文 256k",{"title":378,"searchDepth":775,"depth":775,"links":3351},[],{"data":3353,"body":3354,"excerpt":-1,"toc":3410},{"title":378,"description":378},{"type":765,"children":3355},[3356,3362,3367,3400,3405],{"type":768,"tag":817,"props":3357,"children":3359},{"id":3358},"ai-驅動的三大情境功能",[3360],{"type":773,"value":3361},"AI 驅動的三大情境功能",{"type":768,"tag":769,"props":3363,"children":3364},{},[3365],{"type":773,"value":3366},"Google Translate 於 2026 年 2 月 27 日推出 Gemini 加持的情境輔助功能，專攻慣用語、口語等字面翻譯常失準的場景。三項功能各有分工：",{"type":768,"tag":894,"props":3368,"children":3369},{},[3370,3380,3390],{"type":768,"tag":898,"props":3371,"children":3372},{},[3373,3378],{"type":768,"tag":847,"props":3374,"children":3375},{},[3376],{"type":773,"value":3377},"Alternatives",{"type":773,"value":3379},"：提供多種翻譯候選詞，並附上各用語適合的時機與語境說明",{"type":768,"tag":898,"props":3381,"children":3382},{},[3383,3388],{"type":768,"tag":847,"props":3384,"children":3385},{},[3386],{"type":773,"value":3387},"Understand",{"type":773,"value":3389},"：生成語氣與語境解釋（例如正式與非正式語體的差異）",{"type":768,"tag":898,"props":3391,"children":3392},{},[3393,3398],{"type":768,"tag":847,"props":3394,"children":3395},{},[3396],{"type":773,"value":3397},"Ask",{"type":773,"value":3399},"：允許追問特定情境、國家或方言的具體用法",{"type":768,"tag":817,"props":3401,"children":3403},{"id":3402},"推出範圍與背景",[3404],{"type":773,"value":3402},{"type":768,"tag":769,"props":3406,"children":3407},{},[3408],{"type":773,"value":3409},"目前已在美國與印度的 Android／iOS 先行上線，網頁版即將跟進。技術基礎來自 Gemini 的多語言能力；2025 年 12 月的更新同步帶來耳機實況語音對語音翻譯測試版，支援 70 種以上語言。",{"title":378,"searchDepth":775,"depth":775,"links":3411},[],{"data":3413,"body":3415,"excerpt":-1,"toc":3428},{"title":378,"description":3414},"Gemini 整合讓 Google Translate 從單純字串對映進化為具備語境推理的翻譯系統。Ask 功能本質上是以翻譯為入口的對話式 AI 介面——值得關注的是 Google 如何將 Gemini 多輪對話能力嵌入既有產品流程，以及未來是否開放 API 讓第三方存取這些情境功能。",{"type":765,"children":3416},[3417],{"type":768,"tag":769,"props":3418,"children":3419},{},[3420,3422,3426],{"type":773,"value":3421},"Gemini 整合讓 Google Translate 從單純字串對映進化為具備語境推理的翻譯系統。",{"type":768,"tag":847,"props":3423,"children":3424},{},[3425],{"type":773,"value":3397},{"type":773,"value":3427}," 功能本質上是以翻譯為入口的對話式 AI 介面——值得關注的是 Google 如何將 Gemini 多輪對話能力嵌入既有產品流程，以及未來是否開放 API 讓第三方存取這些情境功能。",{"title":378,"searchDepth":775,"depth":775,"links":3429},[],{"data":3431,"body":3432,"excerpt":-1,"toc":3438},{"title":378,"description":570},{"type":765,"children":3433},[3434],{"type":768,"tag":769,"props":3435,"children":3436},{},[3437],{"type":773,"value":570},{"title":378,"searchDepth":775,"depth":775,"links":3439},[],{"data":3441,"body":3442,"excerpt":-1,"toc":3521},{"title":378,"description":378},{"type":765,"children":3443},[3444,3449,3461,3466,3484,3496,3501,3506],{"type":768,"tag":817,"props":3445,"children":3447},{"id":3446},"模型規格與能力",[3448],{"type":773,"value":3446},{"type":768,"tag":769,"props":3450,"children":3451},{},[3452,3454,3459],{"type":773,"value":3453},"Google 發布 Nano Banana 2（模型 ID：",{"type":768,"tag":875,"props":3455,"children":3457},{"className":3456},[],[3458],{"type":773,"value":2950},{"type":773,"value":3460},"），定位為「Flash 等級速度搭配旗艦畫質」的圖像生成暨編輯模型。支援文字與圖片／PDF 混合輸入，輸出同時涵蓋圖像與文字，上下文視窗為 131,072 輸入 token、32,768 輸出 token。",{"type":768,"tag":769,"props":3462,"children":3463},{},[3464],{"type":773,"value":3465},"新功能包括：",{"type":768,"tag":894,"props":3467,"children":3468},{},[3469,3474,3479],{"type":768,"tag":898,"props":3470,"children":3471},{},[3472],{"type":773,"value":3473},"輸出解析度四檔：0.5K、1K、2K、4K",{"type":768,"tag":898,"props":3475,"children":3476},{},[3477],{"type":773,"value":3478},"新增極端長寬比：1：4、4：1、1：8、8：1",{"type":768,"tag":898,"props":3480,"children":3481},{},[3482],{"type":773,"value":3483},"改善主體一致性、長寬比控制與多語言文字渲染",{"type":768,"tag":769,"props":3485,"children":3486},{},[3487,3489,3494],{"type":773,"value":3488},"Preview 版",{"type":768,"tag":847,"props":3490,"children":3491},{},[3492],{"type":773,"value":3493},"不支援",{"type":773,"value":3495},"：函式呼叫、快取、Live API、URL context、程式碼執行。",{"type":768,"tag":817,"props":3497,"children":3499},{"id":3498},"溯源機制",[3500],{"type":773,"value":3498},{"type":768,"tag":769,"props":3502,"children":3503},{},[3504],{"type":773,"value":3505},"內建雙重溯源：SynthID 浮水印（Gemini 內已驗證逾 2,000 萬次）與 C2PA 內容憑證，符合廣告平台的合規需求。",{"type":768,"tag":840,"props":3507,"children":3508},{},[3509],{"type":768,"tag":769,"props":3510,"children":3511},{},[3512,3516,3519],{"type":768,"tag":847,"props":3513,"children":3514},{},[3515],{"type":773,"value":851},{"type":768,"tag":853,"props":3517,"children":3518},{},[],{"type":773,"value":3520},"\nC2PA(Coalition for Content Provenance and Authenticity) ：業界標準，將創作工具與修改紀錄嵌入圖像 metadata，讓任何人可驗證圖像來源。",{"title":378,"searchDepth":775,"depth":775,"links":3522},[],{"data":3524,"body":3526,"excerpt":-1,"toc":3541},{"title":378,"description":3525},"呼叫方式與既有 Gemini 多模態 API 相同，新增 responseModalities: [\"IMAGE\", \"TEXT\"] 即可啟用圖像輸出。Preview 限制明確：函式呼叫與快取尚不支援，但 Batch API 可用，適合高量非同步任務。定價按 token 計費——1K 圖像約 $0.067，比 Nano Banana Pro 便宜約 50%，高頻生成場景 CP 值顯著。",{"type":765,"children":3527},[3528],{"type":768,"tag":769,"props":3529,"children":3530},{},[3531,3533,3539],{"type":773,"value":3532},"呼叫方式與既有 Gemini 多模態 API 相同，新增 ",{"type":768,"tag":875,"props":3534,"children":3536},{"className":3535},[],[3537],{"type":773,"value":3538},"responseModalities: [\"IMAGE\", \"TEXT\"]",{"type":773,"value":3540}," 即可啟用圖像輸出。Preview 限制明確：函式呼叫與快取尚不支援，但 Batch API 可用，適合高量非同步任務。定價按 token 計費——1K 圖像約 $0.067，比 Nano Banana Pro 便宜約 50%，高頻生成場景 CP 值顯著。",{"title":378,"searchDepth":775,"depth":775,"links":3542},[],{"data":3544,"body":3545,"excerpt":-1,"toc":3551},{"title":378,"description":603},{"type":765,"children":3546},[3547],{"type":768,"tag":769,"props":3548,"children":3549},{},[3550],{"type":773,"value":603},{"title":378,"searchDepth":775,"depth":775,"links":3552},[],{"data":3554,"body":3555,"excerpt":-1,"toc":3590},{"title":378,"description":378},{"type":765,"children":3556},[3557,3562],{"type":768,"tag":817,"props":3558,"children":3560},{"id":3559},"效能與定價基準",[3561],{"type":773,"value":3559},{"type":768,"tag":894,"props":3563,"children":3564},{},[3565,3570,3575,3580,3585],{"type":768,"tag":898,"props":3566,"children":3567},{},[3568],{"type":773,"value":3569},"Artificial Analysis Image Arena 文字生圖：第 1 名 (2026-02-26)",{"type":768,"tag":898,"props":3571,"children":3572},{},[3573],{"type":773,"value":3574},"Nano Banana 2(1K) ：$0.067 / 張",{"type":768,"tag":898,"props":3576,"children":3577},{},[3578],{"type":773,"value":3579},"Nano Banana 2(4K) ：$0.151 / 張",{"type":768,"tag":898,"props":3581,"children":3582},{},[3583],{"type":773,"value":3584},"Nano Banana Pro(1K/2K) ：$0.134 / 張（NB2 約為 Pro 的 50%）",{"type":768,"tag":898,"props":3586,"children":3587},{},[3588],{"type":773,"value":3589},"原版 Nano Banana（最高 1K）：$0.039 / 張",{"title":378,"searchDepth":775,"depth":775,"links":3591},[],{"data":3593,"body":3594,"excerpt":-1,"toc":3632},{"title":378,"description":378},{"type":765,"children":3595},[3596,3602,3607,3622,3627],{"type":768,"tag":817,"props":3597,"children":3599},{"id":3598},"openai-pnnl用-ai-加速聯邦環評文書",[3600],{"type":773,"value":3601},"OpenAI × PNNL：用 AI 加速聯邦環評文書",{"type":768,"tag":769,"props":3603,"children":3604},{},[3605],{"type":773,"value":3606},"OpenAI 與美國能源部下屬的太平洋西北國家實驗室 (PNNL) 宣布合作，發布 DraftNEPABench——首個專為 NEPA 文件起草設計的評測基準。評測涵蓋 18 個聯邦機構的文件段落，由 19 位領域專家對 102 項任務以 1–5 分制評分（結構、清晰度、準確性、引用）。",{"type":768,"tag":840,"props":3608,"children":3609},{},[3610],{"type":768,"tag":769,"props":3611,"children":3612},{},[3613,3617,3620],{"type":768,"tag":847,"props":3614,"children":3615},{},[3616],{"type":773,"value":851},{"type":768,"tag":853,"props":3618,"children":3619},{},[],{"type":773,"value":3621},"\nNEPA（美國國家環境政策法）要求聯邦機構在批准重大建設或能源專案前，必須完成環境影響評估文件，程序複雜且動輒耗費數年。",{"type":768,"tag":817,"props":3623,"children":3625},{"id":3624},"技術架構與初步成果",[3626],{"type":773,"value":3624},{"type":768,"tag":769,"props":3628,"children":3629},{},[3630],{"type":773,"value":3631},"合作採用 Codex CLI 編碼代理工作流程，搭配推理模型（含 GPT-5）進行長文件合成與結構化起草，每個子章節可節省 1–5 小時，整體起草時間估計縮短約 15%。PNNL 的 PermitAI 計畫另包含 MAPLE 評測框架，支援 Azure OpenAI、AWS Bedrock、Google Vertex AI 及本地 HuggingFace 模型，資料庫已擴展至約 12 萬份文件。",{"title":378,"searchDepth":775,"depth":775,"links":3633},[],{"data":3635,"body":3637,"excerpt":-1,"toc":3660},{"title":378,"description":3636},"MAPLE 框架已開源 (pnnl/PermitAI) ，支援 no-context、PDF、RAG、gold-context 四種評測模式，可接入主流雲端 LLM 服務。若需整合 NEPA 自動起草流程，可從 evaluation 模組切入，以 NEPAQuAD 問答集（1,590 題）驗收模型效果。需注意最長文件近 900 頁（逾 60 萬 tokens），對 context window 與推理成本有顯著壓力。",{"type":765,"children":3638},[3639],{"type":768,"tag":769,"props":3640,"children":3641},{},[3642,3644,3650,3652,3658],{"type":773,"value":3643},"MAPLE 框架已開源 (",{"type":768,"tag":875,"props":3645,"children":3647},{"className":3646},[],[3648],{"type":773,"value":3649},"pnnl/PermitAI",{"type":773,"value":3651},") ，支援 no-context、PDF、RAG、gold-context 四種評測模式，可接入主流雲端 LLM 服務。若需整合 NEPA 自動起草流程，可從 ",{"type":768,"tag":875,"props":3653,"children":3655},{"className":3654},[],[3656],{"type":773,"value":3657},"evaluation",{"type":773,"value":3659}," 模組切入，以 NEPAQuAD 問答集（1,590 題）驗收模型效果。需注意最長文件近 900 頁（逾 60 萬 tokens），對 context window 與推理成本有顯著壓力。",{"title":378,"searchDepth":775,"depth":775,"links":3661},[],{"data":3663,"body":3664,"excerpt":-1,"toc":3670},{"title":378,"description":636},{"type":765,"children":3665},[3666],{"type":768,"tag":769,"props":3667,"children":3668},{},[3669],{"type":773,"value":636},{"title":378,"searchDepth":775,"depth":775,"links":3671},[],{"data":3673,"body":3674,"excerpt":-1,"toc":3720},{"title":378,"description":378},{"type":765,"children":3675},[3676,3682],{"type":768,"tag":817,"props":3677,"children":3679},{"id":3678},"draftnepabench-評測數據",[3680],{"type":773,"value":3681},"DraftNEPABench 評測數據",{"type":768,"tag":894,"props":3683,"children":3684},{},[3685,3690,3695,3700,3705,3710,3715],{"type":768,"tag":898,"props":3686,"children":3687},{},[3688],{"type":773,"value":3689},"任務數：102 項（來自 18 個聯邦機構文件段落）",{"type":768,"tag":898,"props":3691,"children":3692},{},[3693],{"type":773,"value":3694},"評分維度：結構、清晰度、準確性、引用（1–5 分制）",{"type":768,"tag":898,"props":3696,"children":3697},{},[3698],{"type":773,"value":3699},"評測專家：19 位領域專家",{"type":768,"tag":898,"props":3701,"children":3702},{},[3703],{"type":773,"value":3704},"每子章節節省：1–5 小時",{"type":768,"tag":898,"props":3706,"children":3707},{},[3708],{"type":773,"value":3709},"整體起草時間縮短：約 15%",{"type":768,"tag":898,"props":3711,"children":3712},{},[3713],{"type":773,"value":3714},"NEPA-Bench 條目：逾 10,000 條",{"type":768,"tag":898,"props":3716,"children":3717},{},[3718],{"type":773,"value":3719},"NEPATEC 2.0 資料庫：約 120,000 份文件（60+ 機構）",{"title":378,"searchDepth":775,"depth":775,"links":3721},[],{"data":3723,"body":3724,"excerpt":-1,"toc":3774},{"title":378,"description":378},{"type":765,"children":3725},[3726,3732,3737,3752,3764,3769],{"type":768,"tag":817,"props":3727,"children":3729},{"id":3728},"gemini-代理流程有監督的多步驟任務",[3730],{"type":773,"value":3731},"Gemini 代理流程：有監督的多步驟任務",{"type":768,"tag":769,"props":3733,"children":3734},{},[3735],{"type":773,"value":3736},"Galaxy S26 系列首發 Gemini 任務處理功能，目前以 Beta 形式在 Gemini 應用程式推出，初期支援美國與韓國，適用類別為餐飲外送、超市購物與叫車服務。長按電源鍵呼叫 Gemini，即可口頭下達如「幫我重新訂上次的餐點」或「叫一台車回家」，Gemini 會自動跨應用程式完成多步驟操作。",{"type":768,"tag":840,"props":3738,"children":3739},{},[3740],{"type":768,"tag":769,"props":3741,"children":3742},{},[3743,3747,3750],{"type":768,"tag":847,"props":3744,"children":3745},{},[3746],{"type":773,"value":1388},{"type":768,"tag":853,"props":3748,"children":3749},{},[],{"type":773,"value":3751},"\n就像交代助理同時訂午餐和叫車，助理自行完成所有步驟，你只需在旁確認。",{"type":768,"tag":769,"props":3753,"children":3754},{},[3755,3757,3762],{"type":773,"value":3756},"設計強調",{"type":768,"tag":847,"props":3758,"children":3759},{},[3760],{"type":773,"value":3761},"可監督性",{"type":773,"value":3763},"：任務進度可透過通知欄即時追蹤，用戶隨時可中斷或停止，手機在執行期間仍可正常使用。",{"type":768,"tag":817,"props":3765,"children":3767},{"id":3766},"裝置端詐騙偵測與硬體升級",[3768],{"type":773,"value":3766},{"type":768,"tag":769,"props":3770,"children":3771},{},[3772],{"type":773,"value":3773},"S26 詐騙電話偵測由裝置端 Gemini 驅動，通話內容不上傳雲端，預設關閉，並排除聯絡人名單中的號碼，偵測到可疑話術時發出音訊與震動警示。硬體方面，S26 Ultra NPU 效能較前代提升最多 39%、CPU 提升 19%，為本地端 AI 推論提供更強算力基礎。Circle to Search 則新增多物件辨識與虛擬試穿功能。",{"title":378,"searchDepth":775,"depth":775,"links":3775},[],{"data":3777,"body":3779,"excerpt":-1,"toc":3790},{"title":378,"description":3778},"Gemini 代理流程採「有監督的自動化」架構，透過通知欄公開任務狀態並允許隨時中斷——這是在安全性與便利性之間的刻意取捨。詐騙偵測完全在裝置端處理 (on-device inference) ，隱私邊界由硬體層把關，NPU 升級直接影響本地推論延遲。",{"type":765,"children":3780},[3781,3785],{"type":768,"tag":769,"props":3782,"children":3783},{},[3784],{"type":773,"value":3778},{"type":768,"tag":769,"props":3786,"children":3787},{},[3788],{"type":773,"value":3789},"目前 Beta 版透過標準 Android Intent 整合三類應用，開發者短期無需修改現有 App。但隨著生態擴展，若要獲得最佳整合效果，開發者需主動適配 Gemini 任務流程的 API 介面。",{"title":378,"searchDepth":775,"depth":775,"links":3791},[],{"data":3793,"body":3795,"excerpt":-1,"toc":3806},{"title":378,"description":3794},"三星與 Google 深化整合，在 Apple Siri 升級持續延誤之際搶佔「實用 AI 手機」定位，讓手機從查詢工具升級為代理執行者，對訂餐、叫車等高頻場景的用戶黏著度有直接貢獻。",{"type":765,"children":3796},[3797,3801],{"type":768,"tag":769,"props":3798,"children":3799},{},[3800],{"type":773,"value":3794},{"type":768,"tag":769,"props":3802,"children":3803},{},[3804],{"type":773,"value":3805},"主要風險在於代理功能的失敗率——多步驟任務若中途失敗或誤操作，信任感將快速瓦解。Beta 階段限縮在結構化場景是合理的風險控管，後續擴展速度將決定競爭優勢能否持續。",{"title":378,"searchDepth":775,"depth":775,"links":3807},[],{"data":3809,"body":3810,"excerpt":-1,"toc":3831},{"title":378,"description":378},{"type":765,"children":3811},[3812,3818],{"type":768,"tag":817,"props":3813,"children":3815},{"id":3814},"硬體效能提升s26-ultra-vs-前代",[3816],{"type":773,"value":3817},"硬體效能提升（S26 Ultra vs. 前代）",{"type":768,"tag":894,"props":3819,"children":3820},{},[3821,3826],{"type":768,"tag":898,"props":3822,"children":3823},{},[3824],{"type":773,"value":3825},"NPU：提升最多 39%",{"type":768,"tag":898,"props":3827,"children":3828},{},[3829],{"type":773,"value":3830},"CPU：提升最多 19%",{"title":378,"searchDepth":775,"depth":775,"links":3832},[],{"data":3834,"body":3835,"excerpt":-1,"toc":3877},{"title":378,"description":378},{"type":765,"children":3836},[3837,3842,3847,3862,3867,3872],{"type":768,"tag":817,"props":3838,"children":3840},{"id":3839},"多目標平行搜尋升級",[3841],{"type":773,"value":3839},{"type":768,"tag":769,"props":3843,"children":3844},{},[3845],{"type":773,"value":3846},"Circle to Search 在 2026 年 2 月迎來重大升級，搭載 Gemini 3，具備代理規劃 (agentic planning) 、推理與工具呼叫能力。新功能核心在於視覺展開 (visual fan-out) ：系統自動識別圖片中的多個重要區域，分別裁切後同時發出多條搜尋，再將結果交叉比對合成單一回覆。",{"type":768,"tag":840,"props":3848,"children":3849},{},[3850],{"type":768,"tag":769,"props":3851,"children":3852},{},[3853,3857,3860],{"type":768,"tag":847,"props":3854,"children":3855},{},[3856],{"type":773,"value":851},{"type":768,"tag":853,"props":3858,"children":3859},{},[],{"type":773,"value":3861},"\nVisual fan-out（視覺展開）：將一張圖片拆解為多個感興趣區域，對每個區域平行執行獨立搜尋，最後彙整為統整結果。",{"type":768,"tag":769,"props":3863,"children":3864},{},[3865],{"type":773,"value":3866},"此架構延伸自 Google 在 2025 年 AI Mode 引入的查詢展開 (query fan-out) 技術——同時對多個子主題和資料來源發出並行子搜尋。",{"type":768,"tag":817,"props":3868,"children":3870},{"id":3869},"虛擬試穿與隱私設計",[3871],{"type":773,"value":3869},{"type":768,"tag":769,"props":3873,"children":3874},{},[3875],{"type":773,"value":3876},"更新同步新增購物「虛擬試穿」入口，支援區域含澳洲、加拿大、印度、日本、英國、美國。Google 聲明試穿照片僅在功能範圍內處理，不用於模型訓練，亦不儲存任何生物特徵資料。升級首發於 Samsung Galaxy S26 系列和 Pixel 10，計畫擴展至更多 Android 裝置；目前 Circle to Search 已在逾 5.8 億台 Android 裝置上使用。",{"title":378,"searchDepth":775,"depth":775,"links":3878},[],{"data":3880,"body":3881,"excerpt":-1,"toc":3887},{"title":378,"description":688},{"type":765,"children":3882},[3883],{"type":768,"tag":769,"props":3884,"children":3885},{},[3886],{"type":773,"value":688},{"title":378,"searchDepth":775,"depth":775,"links":3888},[],{"data":3890,"body":3891,"excerpt":-1,"toc":3897},{"title":378,"description":689},{"type":765,"children":3892},[3893],{"type":768,"tag":769,"props":3894,"children":3895},{},[3896],{"type":773,"value":689},{"title":378,"searchDepth":775,"depth":775,"links":3898},[],{"data":3900,"body":3901,"excerpt":-1,"toc":3948},{"title":378,"description":378},{"type":765,"children":3902},[3903,3909,3914,3929,3935],{"type":768,"tag":817,"props":3904,"children":3906},{"id":3905},"社群熱議廉價本地模型完成複雜任務",[3907],{"type":773,"value":3908},"社群熱議：廉價本地模型完成複雜任務",{"type":768,"tag":769,"props":3910,"children":3911},{},[3912],{"type":773,"value":3913},"Reddit r/LocalLLaMA 熱帖中，用戶 -dysangel- 展示以 Qwen3.5-27B 量化版 (unsloth Qwen 3.5 27B UD Q4_K_XL) 在 OpenWebUI artifacts 視窗中，透過迭代提示建構類 GTA 3D 原型，全程無人工組裝、無外部框架介入，引發社群對「廉價本地模型已足以完成真實任務」的廣泛討論。",{"type":768,"tag":840,"props":3915,"children":3916},{},[3917],{"type":768,"tag":769,"props":3918,"children":3919},{},[3920,3924,3927],{"type":768,"tag":847,"props":3921,"children":3922},{},[3923],{"type":773,"value":851},{"type":768,"tag":853,"props":3925,"children":3926},{},[],{"type":773,"value":3928},"\nQ4_K_XL 是 GGUF 量化格式之一，以 4-bit 精度壓縮模型權重，讓大型模型可在消費級顯卡上運行，以少量精度換取顯著記憶體節省。",{"type":768,"tag":817,"props":3930,"children":3932},{"id":3931},"qwen35-27b-技術規格",[3933],{"type":773,"value":3934},"Qwen3.5-27B 技術規格",{"type":768,"tag":769,"props":3936,"children":3937},{},[3938,3940,3946],{"type":773,"value":3939},"Qwen3.5-27B 採 27B 參數、64 層架構，混合 ",{"type":768,"tag":875,"props":3941,"children":3943},{"className":3942},[],[3944],{"type":773,"value":3945},"Gated DeltaNet + Gated Attention",{"type":773,"value":3947}," 機制，上下文長度 262,144 tokens（可擴展至 1,010,000），以 Apache-2.0 授權開源。Qwen3 系列支援思考與非思考雙模式切換，訓練規模約 36T tokens，涵蓋 119 種語言，支援 vLLM、SGLang 及 OpenAI 相容介面部署。",{"title":378,"searchDepth":775,"depth":775,"links":3949},[],{"data":3951,"body":3953,"excerpt":-1,"toc":3968},{"title":378,"description":3952},"Qwen3.5-27B Q4 量化版可直接在本地透過 OpenWebUI 使用，無需額外工程搭建。混合 Gated DeltaNet 架構帶來比純 Transformer 更長的有效上下文，262K tokens 原生支援對複雜多輪程式碼生成直接有利。Apache-2.0 授權允許商業部署；建議先用 ollama 或 llama.cpp 跑 Q4_K_XL GGUF 驗證效果，確認後再遷移至 vLLM 或 SGLang 做生產批次服務。",{"type":765,"children":3954},[3955],{"type":768,"tag":769,"props":3956,"children":3957},{},[3958,3960,3966],{"type":773,"value":3959},"Qwen3.5-27B Q4 量化版可直接在本地透過 OpenWebUI 使用，無需額外工程搭建。混合 ",{"type":768,"tag":875,"props":3961,"children":3963},{"className":3962},[],[3964],{"type":773,"value":3965},"Gated DeltaNet",{"type":773,"value":3967}," 架構帶來比純 Transformer 更長的有效上下文，262K tokens 原生支援對複雜多輪程式碼生成直接有利。Apache-2.0 授權允許商業部署；建議先用 ollama 或 llama.cpp 跑 Q4_K_XL GGUF 驗證效果，確認後再遷移至 vLLM 或 SGLang 做生產批次服務。",{"title":378,"searchDepth":775,"depth":775,"links":3969},[],{"data":3971,"body":3972,"excerpt":-1,"toc":3978},{"title":378,"description":713},{"type":765,"children":3973},[3974],{"type":768,"tag":769,"props":3975,"children":3976},{},[3977],{"type":773,"value":713},{"title":378,"searchDepth":775,"depth":775,"links":3979},[],{"data":3981,"body":3982,"excerpt":-1,"toc":4188},{"title":378,"description":378},{"type":765,"children":3983},[3984,3989,3994,4054,4059,4078,4083,4088,4094,4125,4130,4135,4145,4168,4178],{"type":768,"tag":817,"props":3985,"children":3987},{"id":3986},"社群熱議排行",[3988],{"type":773,"value":3986},{"type":768,"tag":769,"props":3990,"children":3991},{},[3992],{"type":773,"value":3993},"今日討論熱度最高的五個主題，依社群互動量排序：",{"type":768,"tag":894,"props":3995,"children":3996},{},[3997,4014,4024,4034,4044],{"type":768,"tag":898,"props":3998,"children":3999},{},[4000,4005,4007,4012],{"type":768,"tag":847,"props":4001,"children":4002},{},[4003],{"type":773,"value":4004},"Google API 金鑰安全危機",{"type":773,"value":4006},"（HN 高互動）：Truffle Security 揭露近 3,000 個網站因 Gemini 整合而暴露 ",{"type":768,"tag":875,"props":4008,"children":4010},{"className":4009},[],[4011],{"type":773,"value":1021},{"type":773,"value":4013}," 前綴 API 金鑰，連 Google 自身也中招。@_JohnHammond(X) 快速摘要「Google API 金鑰過去不被視為機密，所以它們散落在整個網路上——但現在它們成了 Gemini 的一扇敞開的大門」，引爆 HN 多條討論串。",{"type":768,"tag":898,"props":4015,"children":4016},{},[4017,4022],{"type":768,"tag":847,"props":4018,"children":4019},{},[4020],{"type":773,"value":4021},"Qwen3.5 本地部署實測熱潮",{"type":773,"value":4023},"（Reddit r/LocalLLaMA 大量跑分回報）：122B MoE 模型在三張消費級 GPU（約 72GB VRAM）可流暢運行，u/mossy_troll_84 公布 Q4 量化版在 RTX 5090 環境可達 34–36 tok/sec，重新定義本地高效能推論門檻。",{"type":768,"tag":898,"props":4025,"children":4026},{},[4027,4032],{"type":768,"tag":847,"props":4028,"children":4029},{},[4030],{"type":773,"value":4031},"Nano Banana 2 奪下圖像評測榜首",{"type":773,"value":4033},"（Reddit r/singularity，u/THE--GRINCH 82 upvotes）：以 Pro 一半定價登頂 Artificial Analysis Image Arena，u/THE--GRINCH 直言「圖像生成問題愈來愈接近被解決了」，u/bentendo93(70 upvotes) 以裝潢規劃實測背書。",{"type":768,"tag":898,"props":4035,"children":4036},{},[4037,4042],{"type":768,"tag":847,"props":4038,"children":4039},{},[4040],{"type":773,"value":4041},"anthropics/skills 技能生態",{"type":773,"value":4043},"（HN + X 雙平台熱議）：Agent Skills 開放標準在數小時內催生 macOS 管理工具 Skill Studio，@AndrewYNg 公開背書 DeepLearning.AI 合作課程，引發工具作者與開發者廣泛討論。",{"type":768,"tag":898,"props":4045,"children":4046},{},[4047,4052],{"type":768,"tag":847,"props":4048,"children":4049},{},[4050],{"type":773,"value":4051},"OpenAI Codex + Figma MCP 整合",{"type":773,"value":4053},"（HN 活躍討論）：@parhamb(X) 分享三步驟設定教學並附言「親測有效」，推文迅速傳播為當日最多人收藏的技術帖之一。",{"type":768,"tag":817,"props":4055,"children":4057},{"id":4056},"技術爭議與分歧",[4058],{"type":773,"value":4056},{"type":768,"tag":769,"props":4060,"children":4061},{},[4062,4064,4069,4071,4076],{"type":773,"value":4063},"本日最明顯的社群分歧在 ",{"type":768,"tag":847,"props":4065,"children":4066},{},[4067],{"type":773,"value":4068},"benchmark 可信度",{"type":773,"value":4070}," 與 ",{"type":768,"tag":847,"props":4072,"children":4073},{},[4074],{"type":773,"value":4075},"API 金鑰安全責任歸屬",{"type":773,"value":4077}," 兩條戰線上激烈交鋒。",{"type":768,"tag":769,"props":4079,"children":4080},{},[4081],{"type":773,"value":4082},"在 benchmark 爭議上，u/metigue(Reddit r/LocalLLaMA) 直指問題核心：「在 Terminal Bench 2 和 Sanity Harness 上，同一個模型換框架可以看到超過 50% 的分數波動，而開源模型對糟糕的 agentic 框架特別敏感」——這讓 Qwen3.5 旗艦版的「崩落」究竟是模型問題還是框架問題，完全無法定論。另一側，u/UmpireBorn3719(Reddit r/LocalLLaMA) 質疑 gpt-oss-20b（1405 分）壓過 Qwen3.5 旗艦（1328 分）的結果是否可信，雙方對「誰才是最強開源程式模型」毫無共識。",{"type":768,"tag":769,"props":4084,"children":4085},{},[4086],{"type":773,"value":4087},"在安全責任歸屬上，gowld(HN) 冷嘲「也許是有經驗的資安審查人員都被裁員了」；SoftTalker(HN) 則持截然不同的立場：「這只是公用事業模式——如果有人接上你戶外的水龍頭偷水，你還是得付錢」。兩種立場折射出對科技公司安全設計責任的根本分歧：一派認為設計缺陷應由平台負責，另一派認為這是使用者自身的風險管理課題。",{"type":768,"tag":817,"props":4089,"children":4091},{"id":4090},"實戰經驗最高價值",[4092],{"type":773,"value":4093},"實戰經驗（最高價值）",{"type":768,"tag":894,"props":4095,"children":4096},{},[4097,4102,4107,4112],{"type":768,"tag":898,"props":4098,"children":4099},{},[4100],{"type":773,"value":4101},"u/mossy_troll_84(Reddit r/LocalLLaMA) ：在 Ryzen 9 9950X3D + RTX 5090 + 128GB DDR5 5600 環境下，Qwen3.5-122B-A10B-UD-Q4_K_XL 實測 34–36 tok/sec；Q8_K_XL 為 16–18 tok/sec，最大上下文均 256K，首次公布消費級旗艦硬體的具體跑分基準。",{"type":768,"tag":898,"props":4103,"children":4104},{},[4105],{"type":773,"value":4106},"u/bentendo93（Reddit r/singularity，70 upvotes）：以 Nano Banana 2 測試室內裝潢規劃，「效果超好，好到讓我現在就想砸錢裝修了」——驗證主體一致性在高需求視覺場景的商業轉化潛力。",{"type":768,"tag":898,"props":4108,"children":4109},{},[4110],{"type":773,"value":4111},"laramie_co(HN) ：自曝每月在 Claude API 花費約 1,200 美元（年計 14,400 美元），正評估本地推論替代方案：「即使降到月付 20 美元方案，每次查詢都在告訴 Anthropic 我在做什麼」——揭示隱私驅動的本地化遷移趨勢，而非純粹成本考量。",{"type":768,"tag":898,"props":4113,"children":4114},{},[4115,4117,4123],{"type":773,"value":4116},"@parhamb(X) ：親測 Codex + Figma MCP 整合，確認修改 ",{"type":768,"tag":875,"props":4118,"children":4120},{"className":4119},[],[4121],{"type":773,"value":4122},"~/.codex/config.toml",{"type":773,"value":4124}," 加入 MCP 伺服器設定後可直接在 Codex CLI 呼叫 Figma 資產，為社群提供可直接複製的設定模板。",{"type":768,"tag":817,"props":4126,"children":4128},{"id":4127},"未解問題與社群預期",[4129],{"type":773,"value":4127},{"type":768,"tag":769,"props":4131,"children":4132},{},[4133],{"type":773,"value":4134},"社群目前懸而未決的關鍵問題集中在四個方向：",{"type":768,"tag":769,"props":4136,"children":4137},{},[4138,4143],{"type":768,"tag":847,"props":4139,"children":4140},{},[4141],{"type":773,"value":4142},"安全責任邊界",{"type":773,"value":4144},"：neop1x(HN) 指出 Google 現有的 API 金鑰限制方案「每位管理員都必須對每個專案重複執行，顯然只是個權宜之計」——社群等待 Google 正式撤回「API 金鑰非機密」聲明，並在金鑰啟用新服務時引入顯式確認機制，目前官方無回應。",{"type":768,"tag":769,"props":4146,"children":4147},{},[4148,4153,4155,4160,4161,4166],{"type":768,"tag":847,"props":4149,"children":4150},{},[4151],{"type":773,"value":4152},"技能路徑標準化",{"type":773,"value":4154},"：westurner(HN) 點出 ",{"type":768,"tag":875,"props":4156,"children":4158},{"className":4157},[],[4159],{"type":773,"value":2707},{"type":773,"value":4070},{"type":768,"tag":875,"props":4162,"children":4164},{"className":4163},[],[4165],{"type":773,"value":2715},{"type":773,"value":4167}," 雙路徑並存的問題，直言「如果規格能指定通用的家目錄相對路徑，對整個生態會更好」，agentskills.io 尚未給出明確答覆。",{"type":768,"tag":769,"props":4169,"children":4170},{},[4171,4176],{"type":768,"tag":847,"props":4172,"children":4173},{},[4174],{"type":773,"value":4175},"消費級 AI 功能膨脹",{"type":773,"value":4177},"：Galaxy S26 預載三個 LLM 服務引發強烈反彈，u/Ilm03（Reddit，79 upvotes）質疑「在手機裡預載 3 個 LLM 服務感覺有點過頭」，u/Embarrassed-Nose2526（Reddit，42 upvotes）更指出 iPhone 與 Pixel 正因軟體精簡而獲益——對「AI 功能堆砌 vs. 精簡體驗」的取捨分歧預計將在 S26 正式發布後激化。",{"type":768,"tag":769,"props":4179,"children":4180},{},[4181,4186],{"type":768,"tag":847,"props":4182,"children":4183},{},[4184],{"type":773,"value":4185},"本地模型的長期競爭力",{"type":773,"value":4187},"：ColonelPhantom(HN) 觀察到 30B 左右的優質開源模型競爭白熱化——不只是 Qwen3.5，還有 GLM-4.7-Flash、Granite 4 Small 等。社群真正的問題是：當本地 27B 模型已可生成可互動的 3D 遊戲原型，雲端 API 的差異化護城河還剩多少？",{"title":378,"searchDepth":775,"depth":775,"links":4189},[],{"data":4191,"body":4192,"excerpt":-1,"toc":4198},{"title":378,"description":759},{"type":765,"children":4193},[4194],{"type":768,"tag":769,"props":4195,"children":4196},{},[4197],{"type":773,"value":759},{"title":378,"searchDepth":775,"depth":775,"links":4199},[],{"data":4201,"body":4202,"excerpt":-1,"toc":4650},{"title":378,"description":378},{"type":765,"children":4203},[4204,4209,4227,4233,4588,4593,4598,4603,4621,4626,4644],{"type":768,"tag":817,"props":4205,"children":4207},{"id":4206},"環境需求",[4208],{"type":773,"value":4206},{"type":768,"tag":894,"props":4210,"children":4211},{},[4212,4217,4222],{"type":768,"tag":898,"props":4213,"children":4214},{},[4215],{"type":773,"value":4216},"Qwen3.5-397B-A17B：FP8 量化需要約 250GB+ VRAM，建議多 GPU 節點；全精度需求更高",{"type":768,"tag":898,"props":4218,"children":4219},{},[4220],{"type":773,"value":4221},"Qwen3.5-27B：單張 A100 80GB 可完整載入 (BF16) ；Apple M2 Ultra（192GB 統一記憶體）可本地運行",{"type":768,"tag":898,"props":4223,"children":4224},{},[4225],{"type":773,"value":4226},"agentic 框架：SWE-agent、OpenHands、Agentless 均可選用，但框架選擇是首要變數，建議先固定框架再比較模型",{"type":768,"tag":817,"props":4228,"children":4230},{"id":4229},"最小-poc",[4231],{"type":773,"value":4232},"最小 PoC",{"type":768,"tag":4234,"props":4235,"children":4239},"pre",{"className":4236,"code":4237,"language":4238,"meta":378,"style":378},"language-python shiki shiki-themes vitesse-dark","# 使用 OpenHands 快速驗測 Qwen3.5-27B（需先啟動 vLLM 端點）\nfrom openhands.controller import AgentController\nfrom openhands.llm.llm import LLM\n\nllm = LLM(\n    model=\"openai/Qwen3.5-27B\",\n    base_url=\"http://localhost:8000/v1\",\n    api_key=\"your-key\"\n)\n\ncontroller = AgentController(llm=llm)\nresult = controller.run(task=\"Fix the failing test in tests/test_parser.py\")\nprint(result)\n","python",[4240],{"type":768,"tag":875,"props":4241,"children":4242},{"__ignoreMap":378},[4243,4255,4291,4330,4339,4361,4396,4426,4453,4462,4470,4508,4565],{"type":768,"tag":4244,"props":4245,"children":4248},"span",{"class":4246,"line":4247},"line",1,[4249],{"type":768,"tag":4244,"props":4250,"children":4252},{"style":4251},"--shiki-default:#758575DD",[4253],{"type":773,"value":4254},"# 使用 OpenHands 快速驗測 Qwen3.5-27B（需先啟動 vLLM 端點）\n",{"type":768,"tag":4244,"props":4256,"children":4257},{"class":4246,"line":775},[4258,4264,4270,4276,4281,4286],{"type":768,"tag":4244,"props":4259,"children":4261},{"style":4260},"--shiki-default:#4D9375",[4262],{"type":773,"value":4263},"from",{"type":768,"tag":4244,"props":4265,"children":4267},{"style":4266},"--shiki-default:#DBD7CAEE",[4268],{"type":773,"value":4269}," openhands",{"type":768,"tag":4244,"props":4271,"children":4273},{"style":4272},"--shiki-default:#666666",[4274],{"type":773,"value":4275},".",{"type":768,"tag":4244,"props":4277,"children":4278},{"style":4266},[4279],{"type":773,"value":4280},"controller ",{"type":768,"tag":4244,"props":4282,"children":4283},{"style":4260},[4284],{"type":773,"value":4285},"import",{"type":768,"tag":4244,"props":4287,"children":4288},{"style":4266},[4289],{"type":773,"value":4290}," AgentController\n",{"type":768,"tag":4244,"props":4292,"children":4293},{"class":4246,"line":199},[4294,4298,4302,4306,4311,4315,4320,4324],{"type":768,"tag":4244,"props":4295,"children":4296},{"style":4260},[4297],{"type":773,"value":4263},{"type":768,"tag":4244,"props":4299,"children":4300},{"style":4266},[4301],{"type":773,"value":4269},{"type":768,"tag":4244,"props":4303,"children":4304},{"style":4272},[4305],{"type":773,"value":4275},{"type":768,"tag":4244,"props":4307,"children":4308},{"style":4266},[4309],{"type":773,"value":4310},"llm",{"type":768,"tag":4244,"props":4312,"children":4313},{"style":4272},[4314],{"type":773,"value":4275},{"type":768,"tag":4244,"props":4316,"children":4317},{"style":4266},[4318],{"type":773,"value":4319},"llm ",{"type":768,"tag":4244,"props":4321,"children":4322},{"style":4260},[4323],{"type":773,"value":4285},{"type":768,"tag":4244,"props":4325,"children":4327},{"style":4326},"--shiki-default:#C99076",[4328],{"type":773,"value":4329}," LLM\n",{"type":768,"tag":4244,"props":4331,"children":4332},{"class":4246,"line":72},[4333],{"type":768,"tag":4244,"props":4334,"children":4336},{"emptyLinePlaceholder":4335},true,[4337],{"type":773,"value":4338},"\n",{"type":768,"tag":4244,"props":4340,"children":4341},{"class":4246,"line":73},[4342,4346,4351,4356],{"type":768,"tag":4244,"props":4343,"children":4344},{"style":4266},[4345],{"type":773,"value":4319},{"type":768,"tag":4244,"props":4347,"children":4348},{"style":4272},[4349],{"type":773,"value":4350},"=",{"type":768,"tag":4244,"props":4352,"children":4353},{"style":4266},[4354],{"type":773,"value":4355}," LLM",{"type":768,"tag":4244,"props":4357,"children":4358},{"style":4272},[4359],{"type":773,"value":4360},"(\n",{"type":768,"tag":4244,"props":4362,"children":4364},{"class":4246,"line":4363},6,[4365,4371,4375,4381,4387,4391],{"type":768,"tag":4244,"props":4366,"children":4368},{"style":4367},"--shiki-default:#BD976A",[4369],{"type":773,"value":4370},"    model",{"type":768,"tag":4244,"props":4372,"children":4373},{"style":4272},[4374],{"type":773,"value":4350},{"type":768,"tag":4244,"props":4376,"children":4378},{"style":4377},"--shiki-default:#C98A7D77",[4379],{"type":773,"value":4380},"\"",{"type":768,"tag":4244,"props":4382,"children":4384},{"style":4383},"--shiki-default:#C98A7D",[4385],{"type":773,"value":4386},"openai/Qwen3.5-27B",{"type":768,"tag":4244,"props":4388,"children":4389},{"style":4377},[4390],{"type":773,"value":4380},{"type":768,"tag":4244,"props":4392,"children":4393},{"style":4272},[4394],{"type":773,"value":4395},",\n",{"type":768,"tag":4244,"props":4397,"children":4399},{"class":4246,"line":4398},7,[4400,4405,4409,4413,4418,4422],{"type":768,"tag":4244,"props":4401,"children":4402},{"style":4367},[4403],{"type":773,"value":4404},"    base_url",{"type":768,"tag":4244,"props":4406,"children":4407},{"style":4272},[4408],{"type":773,"value":4350},{"type":768,"tag":4244,"props":4410,"children":4411},{"style":4377},[4412],{"type":773,"value":4380},{"type":768,"tag":4244,"props":4414,"children":4415},{"style":4383},[4416],{"type":773,"value":4417},"http://localhost:8000/v1",{"type":768,"tag":4244,"props":4419,"children":4420},{"style":4377},[4421],{"type":773,"value":4380},{"type":768,"tag":4244,"props":4423,"children":4424},{"style":4272},[4425],{"type":773,"value":4395},{"type":768,"tag":4244,"props":4427,"children":4429},{"class":4246,"line":4428},8,[4430,4435,4439,4443,4448],{"type":768,"tag":4244,"props":4431,"children":4432},{"style":4367},[4433],{"type":773,"value":4434},"    api_key",{"type":768,"tag":4244,"props":4436,"children":4437},{"style":4272},[4438],{"type":773,"value":4350},{"type":768,"tag":4244,"props":4440,"children":4441},{"style":4377},[4442],{"type":773,"value":4380},{"type":768,"tag":4244,"props":4444,"children":4445},{"style":4383},[4446],{"type":773,"value":4447},"your-key",{"type":768,"tag":4244,"props":4449,"children":4450},{"style":4377},[4451],{"type":773,"value":4452},"\"\n",{"type":768,"tag":4244,"props":4454,"children":4456},{"class":4246,"line":4455},9,[4457],{"type":768,"tag":4244,"props":4458,"children":4459},{"style":4272},[4460],{"type":773,"value":4461},")\n",{"type":768,"tag":4244,"props":4463,"children":4465},{"class":4246,"line":4464},10,[4466],{"type":768,"tag":4244,"props":4467,"children":4468},{"emptyLinePlaceholder":4335},[4469],{"type":773,"value":4338},{"type":768,"tag":4244,"props":4471,"children":4473},{"class":4246,"line":4472},11,[4474,4478,4482,4487,4492,4496,4500,4504],{"type":768,"tag":4244,"props":4475,"children":4476},{"style":4266},[4477],{"type":773,"value":4280},{"type":768,"tag":4244,"props":4479,"children":4480},{"style":4272},[4481],{"type":773,"value":4350},{"type":768,"tag":4244,"props":4483,"children":4484},{"style":4266},[4485],{"type":773,"value":4486}," AgentController",{"type":768,"tag":4244,"props":4488,"children":4489},{"style":4272},[4490],{"type":773,"value":4491},"(",{"type":768,"tag":4244,"props":4493,"children":4494},{"style":4367},[4495],{"type":773,"value":4310},{"type":768,"tag":4244,"props":4497,"children":4498},{"style":4272},[4499],{"type":773,"value":4350},{"type":768,"tag":4244,"props":4501,"children":4502},{"style":4266},[4503],{"type":773,"value":4310},{"type":768,"tag":4244,"props":4505,"children":4506},{"style":4272},[4507],{"type":773,"value":4461},{"type":768,"tag":4244,"props":4509,"children":4511},{"class":4246,"line":4510},12,[4512,4517,4521,4526,4530,4535,4539,4544,4548,4552,4557,4561],{"type":768,"tag":4244,"props":4513,"children":4514},{"style":4266},[4515],{"type":773,"value":4516},"result ",{"type":768,"tag":4244,"props":4518,"children":4519},{"style":4272},[4520],{"type":773,"value":4350},{"type":768,"tag":4244,"props":4522,"children":4523},{"style":4266},[4524],{"type":773,"value":4525}," controller",{"type":768,"tag":4244,"props":4527,"children":4528},{"style":4272},[4529],{"type":773,"value":4275},{"type":768,"tag":4244,"props":4531,"children":4532},{"style":4266},[4533],{"type":773,"value":4534},"run",{"type":768,"tag":4244,"props":4536,"children":4537},{"style":4272},[4538],{"type":773,"value":4491},{"type":768,"tag":4244,"props":4540,"children":4541},{"style":4367},[4542],{"type":773,"value":4543},"task",{"type":768,"tag":4244,"props":4545,"children":4546},{"style":4272},[4547],{"type":773,"value":4350},{"type":768,"tag":4244,"props":4549,"children":4550},{"style":4377},[4551],{"type":773,"value":4380},{"type":768,"tag":4244,"props":4553,"children":4554},{"style":4383},[4555],{"type":773,"value":4556},"Fix the failing test in tests/test_parser.py",{"type":768,"tag":4244,"props":4558,"children":4559},{"style":4377},[4560],{"type":773,"value":4380},{"type":768,"tag":4244,"props":4562,"children":4563},{"style":4272},[4564],{"type":773,"value":4461},{"type":768,"tag":4244,"props":4566,"children":4568},{"class":4246,"line":4567},13,[4569,4575,4579,4584],{"type":768,"tag":4244,"props":4570,"children":4572},{"style":4571},"--shiki-default:#B8A965",[4573],{"type":773,"value":4574},"print",{"type":768,"tag":4244,"props":4576,"children":4577},{"style":4272},[4578],{"type":773,"value":4491},{"type":768,"tag":4244,"props":4580,"children":4581},{"style":4266},[4582],{"type":773,"value":4583},"result",{"type":768,"tag":4244,"props":4585,"children":4586},{"style":4272},[4587],{"type":773,"value":4461},{"type":768,"tag":817,"props":4589,"children":4591},{"id":4590},"驗測規劃",[4592],{"type":773,"value":4590},{"type":768,"tag":769,"props":4594,"children":4595},{},[4596],{"type":773,"value":4597},"建議在你的實際 codebase 上選取 10–20 個已知難度的 issue，分別用至少兩個主流框架（如 SWE-agent 和 OpenHands）測試同一模型。若分數差異超過 20%，代表框架影響大於模型本身，應優先最佳化框架設定，再評估模型選型。",{"type":768,"tag":817,"props":4599,"children":4601},{"id":4600},"常見陷阱",[4602],{"type":773,"value":4600},{"type":768,"tag":894,"props":4604,"children":4605},{},[4606,4611,4616],{"type":768,"tag":898,"props":4607,"children":4608},{},[4609],{"type":773,"value":4610},"直接引用 SWE-bench Verified 分數做採購決策：已知污染問題使高分不等於真實場景領先",{"type":768,"tag":898,"props":4612,"children":4613},{},[4614],{"type":773,"value":4615},"忽略 ELO 分數的難度分層：Qwen3.5-397B 在 hard/expert 難度表現良好，問題出在 master 難度以上",{"type":768,"tag":898,"props":4617,"children":4618},{},[4619],{"type":773,"value":4620},"沒有控制框架變數就比較不同 benchmark 的數字：跨測試的分數沒有可比性",{"type":768,"tag":817,"props":4622,"children":4624},{"id":4623},"上線檢核清單",[4625],{"type":773,"value":4623},{"type":768,"tag":894,"props":4627,"children":4628},{},[4629,4634,4639],{"type":768,"tag":898,"props":4630,"children":4631},{},[4632],{"type":773,"value":4633},"觀測：記錄模型在你的任務難度分布下的 pass@1 率，與 APEX ELO 分數交叉驗證",{"type":768,"tag":898,"props":4635,"children":4636},{},[4637],{"type":773,"value":4638},"成本：397B 模型的 API 費用或硬體折舊 vs. 27B 本地部署的 TCO，建議先試算再決定",{"type":768,"tag":898,"props":4640,"children":4641},{},[4642],{"type":773,"value":4643},"風險：APEX 排行榜更新後（預計 24 小時內）重新核對數字；GLM-4.7 版本確認前暫不跟進",{"type":768,"tag":4645,"props":4646,"children":4647},"style",{},[4648],{"type":773,"value":4649},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":378,"searchDepth":775,"depth":775,"links":4651},[],{"data":4653,"body":4654,"excerpt":-1,"toc":4834},{"title":378,"description":378},{"type":765,"children":4655},[4656,4660,4665,4671,4680,4723,4732,4765,4770,4774,4779,4783,4808,4812,4830],{"type":768,"tag":817,"props":4657,"children":4658},{"id":4206},[4659],{"type":773,"value":4206},{"type":768,"tag":769,"props":4661,"children":4662},{},[4663],{"type":773,"value":4664},"需要安裝 Codex CLI，並持有有效的 OpenAI API Key。Figma 帳號需達 Org／Pro 開發席位以上（每日 200 次工具呼叫）；若使用 Starter 方案則每月僅 6 次，不適合日常開發使用。本地模式需保持 Figma 桌面應用程式持續開啟。",{"type":768,"tag":817,"props":4666,"children":4668},{"id":4667},"遷移整合步驟",[4669],{"type":773,"value":4670},"遷移／整合步驟",{"type":768,"tag":769,"props":4672,"children":4673},{},[4674,4678],{"type":768,"tag":847,"props":4675,"children":4676},{},[4677],{"type":773,"value":2180},{"type":773,"value":4679},"（推薦用於 CI/CD 環境）：",{"type":768,"tag":4234,"props":4681,"children":4685},{"className":4682,"code":4683,"language":4684,"meta":378,"style":378},"language-bash shiki shiki-themes vitesse-dark","codex mcp add figma --url https://mcp.figma.com/mcp\n","bash",[4686],{"type":768,"tag":875,"props":4687,"children":4688},{"__ignoreMap":378},[4689],{"type":768,"tag":4244,"props":4690,"children":4691},{"class":4246,"line":4247},[4692,4698,4703,4708,4713,4718],{"type":768,"tag":4244,"props":4693,"children":4695},{"style":4694},"--shiki-default:#80A665",[4696],{"type":773,"value":4697},"codex",{"type":768,"tag":4244,"props":4699,"children":4700},{"style":4383},[4701],{"type":773,"value":4702}," mcp",{"type":768,"tag":4244,"props":4704,"children":4705},{"style":4383},[4706],{"type":773,"value":4707}," add",{"type":768,"tag":4244,"props":4709,"children":4710},{"style":4383},[4711],{"type":773,"value":4712}," figma",{"type":768,"tag":4244,"props":4714,"children":4715},{"style":4326},[4716],{"type":773,"value":4717}," --url",{"type":768,"tag":4244,"props":4719,"children":4720},{"style":4383},[4721],{"type":773,"value":4722}," https://mcp.figma.com/mcp\n",{"type":768,"tag":769,"props":4724,"children":4725},{},[4726,4730],{"type":768,"tag":847,"props":4727,"children":4728},{},[4729],{"type":773,"value":2195},{"type":773,"value":4731},"（透過 Figma 桌面應用，可存取未發布草稿）：",{"type":768,"tag":4234,"props":4733,"children":4737},{"className":4734,"code":4735,"language":4736,"meta":378,"style":378},"language-toml shiki shiki-themes vitesse-dark","# ~/.codex/config.toml\n[mcp_servers.figma]\nurl = \"http://127.0.0.1:3845/mcp\"\n","toml",[4738],{"type":768,"tag":875,"props":4739,"children":4740},{"__ignoreMap":378},[4741,4749,4757],{"type":768,"tag":4244,"props":4742,"children":4743},{"class":4246,"line":4247},[4744],{"type":768,"tag":4244,"props":4745,"children":4746},{},[4747],{"type":773,"value":4748},"# ~/.codex/config.toml\n",{"type":768,"tag":4244,"props":4750,"children":4751},{"class":4246,"line":775},[4752],{"type":768,"tag":4244,"props":4753,"children":4754},{},[4755],{"type":773,"value":4756},"[mcp_servers.figma]\n",{"type":768,"tag":4244,"props":4758,"children":4759},{"class":4246,"line":199},[4760],{"type":768,"tag":4244,"props":4761,"children":4762},{},[4763],{"type":773,"value":4764},"url = \"http://127.0.0.1:3845/mcp\"\n",{"type":768,"tag":769,"props":4766,"children":4767},{},[4768],{"type":773,"value":4769},"設定後在 Figma 桌面應用啟用 MCP Server，即可在 Codex CLI 提示詞中直接引用 Figma 設計稿進行轉換。",{"type":768,"tag":817,"props":4771,"children":4772},{"id":4590},[4773],{"type":773,"value":4590},{"type":768,"tag":769,"props":4775,"children":4776},{},[4777],{"type":773,"value":4778},"建議先用一個現有 UI 組件做端對端測試：從 Figma 匯出組件描述 → Codex 生成 React 程式碼 → 再將修改後程式碼逆向生成 Figma 稿。比對生成稿與原稿的元件樣式一致性（間距、色票、字體大小），評估在你的設計系統中的還原度，再決定是否納入正式工作流。",{"type":768,"tag":817,"props":4780,"children":4781},{"id":4600},[4782],{"type":773,"value":4600},{"type":768,"tag":894,"props":4784,"children":4785},{},[4786,4791,4803],{"type":768,"tag":898,"props":4787,"children":4788},{},[4789],{"type":773,"value":4790},"配額耗盡無預警：Starter 方案每月 6 次極易在測試階段耗盡，建議先確認方案等級再制定 PoC 規劃",{"type":768,"tag":898,"props":4792,"children":4793},{},[4794,4796,4801],{"type":773,"value":4795},"本地端點依賴桌面應用：本地模式若 Figma 應用關閉，",{"type":768,"tag":875,"props":4797,"children":4799},{"className":4798},[],[4800],{"type":773,"value":2202},{"type":773,"value":4802}," 端點即斷線，建議腳本中加入端點健康檢查",{"type":768,"tag":898,"props":4804,"children":4805},{},[4806],{"type":773,"value":4807},"逆向生成的是全新檔案：Code → Figma 方向生成的是全新設計檔，不會修改原始 Figma 稿，組件庫連結與 Auto Layout 設定不會被保留，需手動合併差異",{"type":768,"tag":817,"props":4809,"children":4810},{"id":4623},[4811],{"type":773,"value":4623},{"type":768,"tag":894,"props":4813,"children":4814},{},[4815,4820,4825],{"type":768,"tag":898,"props":4816,"children":4817},{},[4818],{"type":773,"value":4819},"觀測：工具呼叫次數（追蹤配額消耗速率）、生成程式碼與設計稿的還原度差異、CI 流程中 MCP 連線穩定性",{"type":768,"tag":898,"props":4821,"children":4822},{},[4823],{"type":773,"value":4824},"成本：Figma 方案升級費用（Pro/Org 席位）、OpenAI API token 消耗量估算",{"type":768,"tag":898,"props":4826,"children":4827},{},[4828],{"type":773,"value":4829},"風險：設計稿資料透過遠端 MCP 傳輸的資安合規（特別是含有 NDA 保護設計資產的場景）、生成程式碼的智慧財產權歸屬確認",{"type":768,"tag":4645,"props":4831,"children":4832},{},[4833],{"type":773,"value":4649},{"title":378,"searchDepth":775,"depth":775,"links":4835},[],{"data":4837,"body":4838,"excerpt":-1,"toc":5158},{"title":378,"description":378},{"type":765,"children":4839},[4840,4844,4881,4885,5059,5063,5068,5072,5118,5122,5154],{"type":768,"tag":817,"props":4841,"children":4842},{"id":4206},[4843],{"type":773,"value":4206},{"type":768,"tag":769,"props":4845,"children":4846},{},[4847,4849,4855,4857,4863,4865,4871,4873,4879],{"type":773,"value":4848},"建立技能無需額外依賴，只需在專案根目錄建立 ",{"type":768,"tag":875,"props":4850,"children":4852},{"className":4851},[],[4853],{"type":773,"value":4854},".claude/skills/\u003Cskill-name>/",{"type":773,"value":4856}," 資料夾結構。Claude Code 會自動偵測並載入，GitHub Copilot 亦相容此路徑。若要從 anthropics/skills 倉庫安裝現有技能，可使用社群工具 ",{"type":768,"tag":875,"props":4858,"children":4860},{"className":4859},[],[4861],{"type":773,"value":4862},"npx skills add \u003Cskill-name>",{"type":773,"value":4864}," 指令，或手動將技能資料夾複製至 ",{"type":768,"tag":875,"props":4866,"children":4868},{"className":4867},[],[4869],{"type":773,"value":4870},"~/.claude/skills/",{"type":773,"value":4872},"（全域）或 ",{"type":768,"tag":875,"props":4874,"children":4876},{"className":4875},[],[4877],{"type":773,"value":4878},"./.claude/skills/",{"type":773,"value":4880},"（專案層級）。",{"type":768,"tag":817,"props":4882,"children":4883},{"id":4229},[4884],{"type":773,"value":4232},{"type":768,"tag":4234,"props":4886,"children":4890},{"className":4887,"code":4888,"language":4889,"meta":378,"style":378},"language-yaml shiki shiki-themes vitesse-dark","# .claude/skills/frontend-design/SKILL.md\n---\nname: frontend-design\ndescription: 前端設計規範，適用於元件開發、CSS 架構決策與無障礙合規審查\n---\n\n## 元件命名\n- 使用 PascalCase 命名 React 元件\n- 容器元件加 Container 後綴\n\n## CSS 架構\n- 採用 CSS Modules，禁止全域樣式污染\n- 色彩變數集中定義於 tokens/colors.css\n\n## 無障礙\n- 互動元件必須有 aria-label 或 aria-labelledby\n","yaml",[4891],{"type":768,"tag":875,"props":4892,"children":4893},{"__ignoreMap":378},[4894,4902,4910,4927,4943,4950,4957,4965,4978,4990,4997,5005,5017,5029,5037,5046],{"type":768,"tag":4244,"props":4895,"children":4896},{"class":4246,"line":4247},[4897],{"type":768,"tag":4244,"props":4898,"children":4899},{"style":4251},[4900],{"type":773,"value":4901},"# .claude/skills/frontend-design/SKILL.md\n",{"type":768,"tag":4244,"props":4903,"children":4904},{"class":4246,"line":775},[4905],{"type":768,"tag":4244,"props":4906,"children":4907},{"style":4694},[4908],{"type":773,"value":4909},"---\n",{"type":768,"tag":4244,"props":4911,"children":4912},{"class":4246,"line":199},[4913,4917,4922],{"type":768,"tag":4244,"props":4914,"children":4915},{"style":4571},[4916],{"type":773,"value":2588},{"type":768,"tag":4244,"props":4918,"children":4919},{"style":4272},[4920],{"type":773,"value":4921},":",{"type":768,"tag":4244,"props":4923,"children":4924},{"style":4383},[4925],{"type":773,"value":4926}," frontend-design\n",{"type":768,"tag":4244,"props":4928,"children":4929},{"class":4246,"line":72},[4930,4934,4938],{"type":768,"tag":4244,"props":4931,"children":4932},{"style":4571},[4933],{"type":773,"value":2596},{"type":768,"tag":4244,"props":4935,"children":4936},{"style":4272},[4937],{"type":773,"value":4921},{"type":768,"tag":4244,"props":4939,"children":4940},{"style":4383},[4941],{"type":773,"value":4942}," 前端設計規範，適用於元件開發、CSS 架構決策與無障礙合規審查\n",{"type":768,"tag":4244,"props":4944,"children":4945},{"class":4246,"line":73},[4946],{"type":768,"tag":4244,"props":4947,"children":4948},{"style":4694},[4949],{"type":773,"value":4909},{"type":768,"tag":4244,"props":4951,"children":4952},{"class":4246,"line":4363},[4953],{"type":768,"tag":4244,"props":4954,"children":4955},{"emptyLinePlaceholder":4335},[4956],{"type":773,"value":4338},{"type":768,"tag":4244,"props":4958,"children":4959},{"class":4246,"line":4398},[4960],{"type":768,"tag":4244,"props":4961,"children":4962},{"style":4251},[4963],{"type":773,"value":4964},"## 元件命名\n",{"type":768,"tag":4244,"props":4966,"children":4967},{"class":4246,"line":4428},[4968,4973],{"type":768,"tag":4244,"props":4969,"children":4970},{"style":4272},[4971],{"type":773,"value":4972},"-",{"type":768,"tag":4244,"props":4974,"children":4975},{"style":4383},[4976],{"type":773,"value":4977}," 使用 PascalCase 命名 React 元件\n",{"type":768,"tag":4244,"props":4979,"children":4980},{"class":4246,"line":4455},[4981,4985],{"type":768,"tag":4244,"props":4982,"children":4983},{"style":4272},[4984],{"type":773,"value":4972},{"type":768,"tag":4244,"props":4986,"children":4987},{"style":4383},[4988],{"type":773,"value":4989}," 容器元件加 Container 後綴\n",{"type":768,"tag":4244,"props":4991,"children":4992},{"class":4246,"line":4464},[4993],{"type":768,"tag":4244,"props":4994,"children":4995},{"emptyLinePlaceholder":4335},[4996],{"type":773,"value":4338},{"type":768,"tag":4244,"props":4998,"children":4999},{"class":4246,"line":4472},[5000],{"type":768,"tag":4244,"props":5001,"children":5002},{"style":4251},[5003],{"type":773,"value":5004},"## CSS 架構\n",{"type":768,"tag":4244,"props":5006,"children":5007},{"class":4246,"line":4510},[5008,5012],{"type":768,"tag":4244,"props":5009,"children":5010},{"style":4272},[5011],{"type":773,"value":4972},{"type":768,"tag":4244,"props":5013,"children":5014},{"style":4383},[5015],{"type":773,"value":5016}," 採用 CSS Modules，禁止全域樣式污染\n",{"type":768,"tag":4244,"props":5018,"children":5019},{"class":4246,"line":4567},[5020,5024],{"type":768,"tag":4244,"props":5021,"children":5022},{"style":4272},[5023],{"type":773,"value":4972},{"type":768,"tag":4244,"props":5025,"children":5026},{"style":4383},[5027],{"type":773,"value":5028}," 色彩變數集中定義於 tokens/colors.css\n",{"type":768,"tag":4244,"props":5030,"children":5032},{"class":4246,"line":5031},14,[5033],{"type":768,"tag":4244,"props":5034,"children":5035},{"emptyLinePlaceholder":4335},[5036],{"type":773,"value":4338},{"type":768,"tag":4244,"props":5038,"children":5040},{"class":4246,"line":5039},15,[5041],{"type":768,"tag":4244,"props":5042,"children":5043},{"style":4251},[5044],{"type":773,"value":5045},"## 無障礙\n",{"type":768,"tag":4244,"props":5047,"children":5049},{"class":4246,"line":5048},16,[5050,5054],{"type":768,"tag":4244,"props":5051,"children":5052},{"style":4272},[5053],{"type":773,"value":4972},{"type":768,"tag":4244,"props":5055,"children":5056},{"style":4383},[5057],{"type":773,"value":5058}," 互動元件必須有 aria-label 或 aria-labelledby\n",{"type":768,"tag":817,"props":5060,"children":5061},{"id":4590},[5062],{"type":773,"value":4590},{"type":768,"tag":769,"props":5064,"children":5065},{},[5066],{"type":773,"value":5067},"建立技能後，在 Claude Code 中觸發相關任務（如「幫我建一個按鈕元件」），觀察 Agent 是否自動遵循技能中的命名與 CSS 規範，無需在提示詞中重複說明。可準備一份刻意違反規範的 code snippet，請 Agent review 並確認它能主動指出問題所在。",{"type":768,"tag":817,"props":5069,"children":5070},{"id":4600},[5071],{"type":773,"value":4600},{"type":768,"tag":894,"props":5073,"children":5074},{},[5075,5085,5090,5100],{"type":768,"tag":898,"props":5076,"children":5077},{},[5078,5083],{"type":768,"tag":875,"props":5079,"children":5081},{"className":5080},[],[5082],{"type":773,"value":2596},{"type":773,"value":5084}," 欄位過於籠統會導致 Agent 在不相關任務中載入技能，白白消耗 context；建議描述精確到「適用情境」而非「包含內容」",{"type":768,"tag":898,"props":5086,"children":5087},{},[5088],{"type":773,"value":5089},"技能指令與 CLAUDE.md 規範衝突時，優先順序行為需實測確認，避免兩套規則互相覆蓋造成行為不穩定",{"type":768,"tag":898,"props":5091,"children":5092},{},[5093,5098],{"type":768,"tag":875,"props":5094,"children":5096},{"className":5095},[],[5097],{"type":773,"value":2627},{"type":773,"value":5099}," 欄位目前為實驗性功能，跨平台行為尚未穩定，生產環境暫時不依賴此功能",{"type":768,"tag":898,"props":5101,"children":5102},{},[5103,5105,5110,5111,5116],{"type":773,"value":5104},"技能路徑規範尚有 ",{"type":768,"tag":875,"props":5106,"children":5108},{"className":5107},[],[5109],{"type":773,"value":2707},{"type":773,"value":2709},{"type":768,"tag":875,"props":5112,"children":5114},{"className":5113},[],[5115],{"type":773,"value":2715},{"type":773,"value":5117}," 社群爭議，建議持續觀察 agentskills.io 規格更新再做路徑選擇",{"type":768,"tag":817,"props":5119,"children":5120},{"id":4623},[5121],{"type":773,"value":4623},{"type":768,"tag":894,"props":5123,"children":5124},{},[5125,5130,5135],{"type":768,"tag":898,"props":5126,"children":5127},{},[5128],{"type":773,"value":5129},"觀測：技能是否在正確情境被自動載入；Agent 輸出是否實際反映技能指令而非通用預設行為",{"type":768,"tag":898,"props":5131,"children":5132},{},[5133],{"type":773,"value":5134},"成本：單份技能 SKILL.md 建議控制在 500 tokens 以內，避免技能數量過多導致 context 成本失控",{"type":768,"tag":898,"props":5136,"children":5137},{},[5138,5140,5145,5147,5152],{"type":773,"value":5139},"風險：確認技能資料夾未意外提交含商業機密的 ",{"type":768,"tag":875,"props":5141,"children":5143},{"className":5142},[],[5144],{"type":773,"value":2663},{"type":773,"value":5146}," 文件；審查 ",{"type":768,"tag":875,"props":5148,"children":5150},{"className":5149},[],[5151],{"type":773,"value":2652},{"type":773,"value":5153}," 中的腳本是否有潛在的命令注入風險",{"type":768,"tag":4645,"props":5155,"children":5156},{},[5157],{"type":773,"value":4649},{"title":378,"searchDepth":775,"depth":775,"links":5159},[]]