從 Context 流失到自我修復 CI：Anthropic 的工程實戰觀察
Anthropic 工程師在臺北 Meetup 分享：如何透過 hooks 與自動化機制，把 CI 的回饋迴路產品化，減少等待與人工重工。
Tim
From Context Loss to Self-Healing CI: Observations from Anthropic’s Engineering Practice
Anthropic engineers shared at a Taipei Meetup how hooks and automation can productize CI’s feedback loop, reducing waiting and manual rework.
Design System 分層架構：Style × Color × Industry 的組合爆炸
當 Design System 的客戶需求開始交叉，扁平的 Preset 架構會陷入維護成本爆炸的困境。本文探討如何透過 Style、Color 與 Industry 三層解耦架構，將維護成本從指數增長轉為模組化，實現設計系統的規模化。
Design System Layered Architecture: From Preset to Platform
When Design System client needs start overlapping, a flat Preset architecture can collapse into exploding maintenance costs. This post explores how a three-layer decoupled architecture of Style, Color, and Industry turns maintenance costs from exponential growth into modular work, enabling Design Systems to scale.
DevOps Didn’t Replace SDLC. Neither Will AI.
PR merge count doubled — and so did production rollbacks. After adopting AI tools, one team watched weekly merges climb from 32 to 71, while monthly rollbacks jumped from 2 to 5. Every rolled-back PR had passed CI. AI accelerated the coding part, but the feedback net of review and testing didn’t become denser to match. This post breaks down the three-layer architecture of SDLC, DevOps, and CI/CD, and looks at which layer AI should be placed in.
AI 寫的 UI 為什麼總差一點？因為沒人告訴它什麼算好
AI 生成的 UI 品質參差不齊，因為缺乏具體約束。UI Skills 將模糊的最佳實踐轉化為可驗證的規則。解析其設計模式，教你建立團隊專屬的 Skill 約束系統。
DevOps 沒有取代 SDLC，AI 也不會
PR merge 速度翻倍，rollback 次數也跟著翻倍。AI 加速的是寫程式碼那一段,但 review 與測試的反饋網沒跟著加密。本文拆解 SDLC、DevOps、CI/CD 三層架構,看 AI 該被擺進哪一層。
Why Does AI-Written UI Always Fall a Little Short? Because Nobody Told It What Counts as Good
AI-generated UI quality is inconsistent because it lacks concrete constraints. UI Skills turns vague best practices into verifiable rules. This post analyzes its design patterns and shows you how to build a team-specific Skill constraint system.
AI 導入不是選 A 或 B：三鏡頭 Workshop 設計
董事會下個月要 review，三份 AI 文件擺在桌上：Agentic AI、AI + SDLC、DevSecOps。高層想要創新，工程師想少加班，Workshop 從哪一個開始？多數團隊把它當成三選一，結果是 60% 的 GenAI 專案卡在 PoC。它們不是平行選項，是相依關係。本文示範用三幕 Workshop——痛點探索、三鏡頭亮燈、Quick Win → Core Change → Strategic Leap——讓高層與工程師在同一張地圖上排出順序。
PR 跑出 120 個警告，為什麼只有 5 個值得看？
Junior 提交了 PR，AI review 吐出一份 40 頁的報告。120 個標記中,Senior 看了 20 分鐘，發現 80% 是風格，15% 是誤報。當警告太多，高信賴度風險就被淹沒了。PR review 有兩個特殊結構，讓它特別吃多 Agent 交叉驗證的紅利。