[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-kiro-aws-healthomics-bioinformatics-workflow-zh":3,"tags-kiro-aws-healthomics-bioinformatics-workflow-zh":33,"related-lang-kiro-aws-healthomics-bioinformatics-workflow-zh":48,"related-posts-kiro-aws-healthomics-bioinformatics-workflow-zh":52,"series-tools-4cbaa31a-f971-4bb3-8607-96d12e6548aa":89},{"id":4,"title":5,"content":6,"summary":7,"source":8,"source_url":9,"author":10,"image_url":11,"keywords":12,"language":21,"translated_content":10,"views":22,"is_premium":23,"created_at":24,"updated_at":24,"cover_image":11,"published_at":25,"rewrite_status":26,"rewrite_error":10,"rewritten_from_id":27,"slug":28,"category":29,"related_article_id":30,"status":31,"google_indexed_at":32,"x_posted_at":10,"tweet_text":10,"title_rewritten_at":10,"title_original":10,"key_takeaways":10,"topic_cluster_id":10,"embedding":10,"is_canonical_seed":23},"4cbaa31a-f971-4bb3-8607-96d12e6548aa","Kiro 搭 HealthOmics，生資流程少卡關","\u003Cp>生資 workflow 很磨人。你要懂 biology，也要會 WDL、Nextflow，還得顧雲端設定。AWS 這次把 \u003Ca href=\"https:\u002F\u002Fkiro.dev\" target=\"_blank\" rel=\"noopener\">Kiro\u003C\u002Fa> 接上 \u003Ca href=\"https:\u002F\u002Faws.amazon.com\u002Fhealthomics\u002F\" target=\"_blank\" rel=\"noopener\">AWS HealthOmics\u003C\u002Fa>，直接把痛點搬進 IDE。AWS 說，workflow 建置和 migration 的速度，能拉到 2 倍以上。還有一個 RNA-seq migration，從數天壓到半天內。\u003C\u002Fp>\u003Cp>講白了，這不是在比誰 p\u003Ca href=\"\u002Fnews\u002Fprompt-engineering-explained-without-the-hype-zh\">romp\u003C\u002Fa>t 寫得帥。這是在比誰少踩坑。生資工程最貴的，常常不是寫 code，而是等跑完才發現 container 壞了、directive 不支援，或參數根本不合規。\u003C\u002Fp>\u003Cp>這次 AWS 的做法很直白。它想把平台知識塞進工具裡。讓你不用每次都重新教 AI 一遍 HealthOmics 規則。這點我覺得蠻實際的。\u003C\u002Fp>\u003Ch2>AWS 這次到底做了什麼\u003C\u002Fh2>\u003Cp>核心是 \u003Ca href=\"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Findustries\u002Ffrom-prompt-to-pipeline-ai-powered-bioinformatics-workflow-development-with-kiro-and-aws-healthomics\u002F\" target=\"_blank\" rel=\"noopener\">AWS HealthOmics extension for Kiro\u003C\u002Fa>，再加上 AWS HealthOmics Kiro Power。兩個東西合起來，讓 Kiro 多了 HealthOmics 的語境。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775167427064-u1q3.png\" alt=\"Kiro 搭 HealthOmics，生資流程少卡關\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>這代表 IDE 不再只會補字。它還能幫你看部署、驗證、除錯，甚至更新 workflow。對一般 app 開發者來說，這很像把 lint、deploy、runbook 全塞回編輯器。\u003C\u002Fp>\u003Cp>對生資團隊來說，這種整合很重要。因為一個錯誤常常不是小 bug，而是幾小時 compute 白燒。你不想等到跑完才知道 container image 不對。你想在寫的時候就被攔下來。\u003C\u002Fp>\u003Cul>\u003Cli>支援 \u003Ca href=\"https:\u002F\u002Fwww.nextflow.io\u002F\" target=\"_blank\" rel=\"noopener\">Nextflow\u003C\u002Fa> 和 \u003Ca href=\"https:\u002F\u002Fopenwdl.org\u002F\" target=\"_blank\" rel=\"noopener\">WDL\u003C\u002Fa>\u003C\u002Fli>\u003Cli>提供 IntelliSense 和即時診斷\u003C\u002Fli>\u003Cli>內建 HealthOmics Explorer，可看 workflow 和 run\u003C\u002Fli>\u003Cli>可先檢查不支援的 directive 與 container 格式\u003C\u002Fli>\u003Cli>透過 \u003Ca href=\"https:\u002F\u002Fmodelcontextprotocol.io\u002F\" target=\"_blank\" rel=\"noopener\">Model Context Protocol\u003C\u002Fa> 做自然語言操作\u003C\u002Fli>\u003C\u002Ful>\u003Cp>這裡的重點不是 AI 很會聊。重點是它知道你在 HealthOmics 裡做事。這種 context 才值錢。沒有 context 的 AI，常常只是在猜。\u003C\u002Fp>\u003Cp>而且 AWS 沒叫你改用自家新語言。它還是吃 Nextflow 和 WDL。這很務實。因為生資團隊早就有既有 pi\u003Ca href=\"\u002Fnews\u002Fopenai-vs-deepmind-models-apps-2026-zh\">pe\u003C\u002Fa>line，不可能為了 AI 再重寫一輪。\u003C\u002Fp>\u003Ch2>為什麼 MCP 這層很關鍵\u003C\u002Fh2>\u003Cp>MCP 是這次最有意思的地方。因為它決定 AI 回答的品質。沒有 domain context，模型可以寫 code，但常常漏掉平台限制。對 HealthOmics 來說，漏一條規則就可能整個部署失敗。\u003C\u002Fp>\u003Cp>AWS 說，Kiro Power 會自動設定 HealthOmics MCP server，還會加上 steering guides。這些 guide 會管第一次設定、spec-driven 開發、跨平台 migration。也就是說，Kiro 不只會寫，還知道怎麼包、怎麼 deploy、怎麼查錯。\u003C\u002Fp>\u003Cp>這種設計很像把資深同事的腦袋，做成工作區設定。你不用每次問「這個 container 可以嗎」。工具自己先幫你擋一次。這對團隊協作也有幫助，因為規則會比較一致。\u003C\u002Fp>\u003Cblockquote>“You can ask Kiro to create a totally new workflow definition from only a natural language description,” AWS wrote in the blog post announcing the extension and power.\u003C\u002Fblockquote>\u003Cp>這句話很直球。AWS 想把起點放在自然語言，再一路走到 spec、部署、執行。流程不是聊天而已。它是把聊天接到可跑的 pipeline。\u003C\u002Fp>\u003Cp>我覺得這種模式比空泛的 AI demo 實在。因為它把問題縮小了。不是問 AI 會不會萬用。是問它懂不懂這個系統。\u003C\u002Fp>\u003Ch2>跟舊流程比，差在哪\u003C\u002Fh2>\u003Cp>傳統生資流程很像打地鼠。你改一版，跑一次，等很久，然後爆掉。再改，再跑，再等。這種迴圈很耗人。也很耗雲端費用。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775167434634-kugb.png\" alt=\"Kiro 搭 HealthOmics，生資流程少卡關\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>AWS 在文章裡給了幾個數字。這些數字比形容詞有用多了。因為你可以直接拿來估工時，也能拿來算成本。\u003C\u002Fp>\u003Cp>它的說法很簡單：把錯誤提早抓出來，把重複工作交給工具。這樣一來，很多本來要靠手動檢查的步驟，就能在 editor 裡先過濾掉。\u003C\u002Fp>\u003Cul>\u003Cli>一般 workflow 建置與 migration：速度超過 2 倍\u003C\u002Fli>\u003Cli>一個 RNA-seq migration：從數天縮到半天內\u003C\u002Fli>\u003Cli>失敗診斷：從 run 後才知道，改成寫的時候先檢查\u003C\u002Fli>\u003Cli>部署方式：直接從 IDE 送出，不用一直切 console\u003C\u002Fli>\u003C\u002Ful>\u003Cp>這種差異很像一般軟體開發從命令列，走到完整 IDE 的過程。差別是，生資的錯誤代價更高。你不是只浪費時間。你還可能浪費樣本、算力，甚至研究排程。\u003C\u002Fp>\u003Cp>如果拿競品來看，\u003Ca href=\"https:\u002F\u002Fwww.nextflow.io\u002F\" target=\"_blank\" rel=\"noopener\">Nextflow\u003C\u002Fa> 本身已經很成熟。\u003Ca href=\"https:\u002F\u002Fopenwdl.org\u002F\" target=\"_blank\" rel=\"noopener\">WDL\u003C\u002Fa> 也有穩定社群。AWS 的差別，不在語言本身，而在整合層。\u003C\u002Fp>\u003Cp>它想做的是把 workflow 語言、雲端資源、AI 助手綁在一起。這跟單純賣一個 chatbot 不一樣。它比較像工作台。\u003C\u002Fp>\u003Ch2>這件事對 AI 工具的意思\u003C\u002Fh2>\u003Cp>這次更新其實在講一件事。AI coding 工具要有領域知識，才真的有用。通用模型很強，但不代表懂每個雲端服務的規則。\u003C\u002Fp>\u003Cp>在科學軟體裡，這件事更明顯。你寫得對，不代表能跑。你跑得動，不代表合規。你合規，也不代表省錢。這些條件常常同時存在。\u003C\u002Fp>\u003Cp>所以 HealthOmics extension 的價值，不是它會聊天。是它知道 HealthOmics 的邊界。知道什麼可以做，什麼不行。這種知識，才是生資團隊真正需要的。\u003C\u002Fp>\u003Cp>我也覺得這會影響其他領域。像 lab automation、影像 pipeline、金融風控流程，都很吃 domain context。未來如果 AI 工具只會泛用回答，競爭力會很有限。\u003C\u002Fp>\u003Cp>真正有用的工具，會把模型包進工作流程。不是叫你換腦袋，而是叫工具先學會你現在的規矩。\u003C\u002Fp>\u003Ch2>這波更新背後的產業脈絡\u003C\u002Fh2>\u003Cp>生資軟體本來就很碎。研究人員、資料工程師、雲端工程師，常常要一起配合。每個人看問題的角度都不同。這也是 workflow 開發一直難搞的原因。\u003C\u002Fp>\u003Cp>另外，雲端算力越來越貴。尤其是長時間跑的分析。像 RNA-seq、variant calling、meta\u003Ca href=\"\u002Fnews\u002Fprompt-engineering-agents-structured-outputs-zh\">gen\u003C\u002Fa>omics，任何一個節點出錯，都會拖掉整條鏈。這時候，早點發現問題，比事後修正重要很多。\u003C\u002Fp>\u003Cp>從產業角度看，AWS 這次是把 AI 助手往垂直場景推。不是再做一個萬用聊天介面，而是把它塞進既有平台。這種做法比較容易被企業買單。因為它能直接對到工時、錯誤率、和 cloud bill。\u003C\u002Fp>\u003Cp>如果你問我，這類工具會不會取代生資工程師？我覺得不會。它比較像把重複勞動壓縮掉。人還是要負責判斷。尤其是資料品質、實驗設計、和結果解讀，AI 還差很遠。\u003C\u002Fp>\u003Cp>但如果你問它會不會改變團隊寫 pipeline 的方式？我覺得會。至少從現在開始，大家會更期待 IDE 直接懂平台，而不是只會幫你補幾行 code。\u003C\u002Fp>\u003Ch2>接下來該看什麼\u003C\u002Fh2>\u003Cp>如果你已經在用 HealthOmics，我會先試 Kiro 和 extension。不要先想大改架構。先拿一條現有 pipeline 試水溫。看它能不能真的幫你抓錯、補 spec、縮短 migration。\u003C\u002Fp>\u003Cp>如果你是做一般軟體開發，也可以把這次當成一個訊號。AI 工具正在往「懂場景」走。下一個有用的助手，不一定是最會講話的那個。可能是最懂你專案規則的那個。\u003C\u002Fp>\u003Cp>我自己的判斷很直接。這類整合如果真的穩，接下來 12 個月，會有更多雲端服務學這一套。問題不是會不會跟上。問題是你的團隊準備好把流程標準化了沒。\u003C\u002Fp>\u003Cp>你如果是生資或資料平台團隊，現在就該問一句：我們的 pipeline，有沒有哪一段，其實可以先交給工具處理？\u003C\u002Fp>","AWS 把 Kiro 接上 HealthOmics，主打把生資 workflow 建置速度拉高 2 倍以上；一個 RNA-seq migration 甚至從數天縮到半天內。","aws.amazon.com","https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Findustries\u002Ffrom-prompt-to-pipeline-ai-powered-bioinformatics-workflow-development-with-kiro-and-aws-healthomics\u002F",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1775167427064-u1q3.png",[13,14,15,16,17,18,19,20],"Kiro","AWS HealthOmics","生物資訊","Nextflow","WDL","MCP","AI 工具","workflow","zh",0,false,"2026-04-02T22:03:31.71144+00:00","2026-04-02T22:03:31.359+00:00","done","29e7e7ef-4020-457d-b44f-a1c545542acd","kiro-aws-healthomics-bioinformatics-workflow-zh","tools","9bf2d3e1-bb4a-4feb-9ad4-6cfcfdbfa5c5","published","2026-04-08T09:00:48.252+00:00",[34,36,38,40,42,43,45,47],{"name":19,"slug":35},"ai-工具",{"name":14,"slug":37},"aws-healthomics",{"name":18,"slug":39},"mcp",{"name":16,"slug":41},"nextflow",{"name":20,"slug":20},{"name":13,"slug":44},"kiro",{"name":17,"slug":46},"wdl",{"name":15,"slug":15},{"id":30,"slug":49,"title":50,"language":51},"kiro-aws-healthomics-bioinformatics-workflow-en","Kiro and AWS HealthOmics Cut Workflow Friction","en",[53,59,65,71,77,83],{"id":54,"slug":55,"title":56,"cover_image":57,"image_url":57,"created_at":58,"category":29},"d058a76f-6548-4135-8970-f3a97f255446","why-gemini-api-pricing-is-cheaper-than-it-looks-zh","為什麼 Gemini API 定價其實比看起來更便宜","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778869845081-j4m7.png","2026-05-15T18:30:25.797639+00:00",{"id":60,"slug":61,"title":62,"cover_image":63,"image_url":63,"created_at":64,"category":29},"68e4be16-dc38-4524-a6ea-5ebe22a6c4fb","why-vidhub-huiyuan-hutong-bushi-quan-shebei-tongyong-zh","為什麼 VidHub 會員互通不是「買一次全設備通用」","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778789450987-advz.png","2026-05-14T20:10:24.048988+00:00",{"id":66,"slug":67,"title":68,"cover_image":69,"image_url":69,"created_at":70,"category":29},"7a1e174f-746b-4e82-a0e3-b2475ab39747","why-buns-zig-to-rust-experiment-is-right-zh","為什麼 Bun 的 Zig-to-Rust 實驗是對的","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778767879127-5dna.png","2026-05-14T14:10:26.886397+00:00",{"id":72,"slug":73,"title":74,"cover_image":75,"image_url":75,"created_at":76,"category":29},"e742fc73-5a65-4db3-ad17-88c99262ceb7","why-openai-api-pricing-is-product-strategy-zh","為什麼 OpenAI API 定價是產品策略，不是註腳","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778749859485-chvz.png","2026-05-14T09:10:26.003818+00:00",{"id":78,"slug":79,"title":80,"cover_image":81,"image_url":81,"created_at":82,"category":29},"c757c5d8-eda9-45dc-9020-4b002f4d6237","why-claude-code-prompt-design-beats-ide-copilots-zh","為什麼 Claude Code 的提示設計贏過 IDE Copilot","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778742645084-dao9.png","2026-05-14T07:10:29.371901+00:00",{"id":84,"slug":85,"title":86,"cover_image":87,"image_url":87,"created_at":88,"category":29},"4adef3ab-9f07-4970-91cf-77b8b581b348","why-databricks-model-serving-is-right-default-zh","為什麼 Databricks Model Serving 是生產推論的正確預設","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778692245329-a2wt.png","2026-05-13T17:10:30.659153+00:00",[90,95,100,105,110,115,120,125,130,135],{"id":91,"slug":92,"title":93,"created_at":94},"de769291-4574-4c46-a76d-772bd99e6ec9","googles-biggest-gemini-launches-in-2026-zh","Google 2026 最大 Gemini 盤點","2026-03-26T07:26:39.21072+00:00",{"id":96,"slug":97,"title":98,"created_at":99},"855cd52f-6fab-46cc-a7c1-42195e8a0de4","surepath-real-time-mcp-policy-controls-zh","SurePath 推出即時 MCP 政策控管","2026-03-26T07:57:40.77233+00:00",{"id":101,"slug":102,"title":103,"created_at":104},"9b19ab54-edef-4dbd-9ce4-a51e4bae4ebb","mcp-in-2026-the-ai-tool-layer-teams-use-zh","2026 年 MCP：團隊真的在用的 AI 工具層","2026-03-26T08:01:46.589694+00:00",{"id":106,"slug":107,"title":108,"created_at":109},"af9c46c3-7a28-410b-9f04-32b3de30a68c","prompting-in-2026-what-actually-works-zh","2026 提示工程，真正有用的是什麼","2026-03-26T08:08:12.453028+00:00",{"id":111,"slug":112,"title":113,"created_at":114},"05553086-6ed0-4758-81fd-6cab24b575e0","garry-tan-open-sources-claude-code-toolkit-zh","Garry Tan 開源 Claude Code 工具包","2026-03-26T08:26:20.068737+00:00",{"id":116,"slug":117,"title":118,"created_at":119},"042a73a2-18a2-433d-9e8f-9802b9559aac","github-ai-projects-to-watch-in-2026-zh","2026 必看 20 個 GitHub AI 專案","2026-03-26T08:28:09.619964+00:00",{"id":121,"slug":122,"title":123,"created_at":124},"a5f94120-ac0d-4483-9a8b-63590071ac6a","claude-code-vs-cursor-2026-zh","Claude Code 與 Cursor 深度對比：202…","2026-03-26T13:27:14.279193+00:00",{"id":126,"slug":127,"title":128,"created_at":129},"0975afa1-e0c7-4130-a20d-d890eaed995e","practical-github-guide-learning-ml-2026-zh","2026 機器學習入門 GitHub 實用指南","2026-03-27T01:16:49.712576+00:00",{"id":131,"slug":132,"title":133,"created_at":134},"bfdb467a-290f-4a80-b3a9-6f081afb6dff","aiml-2026-student-ai-ml-lab-repo-review-zh","AIML-2026：像課綱的學生實驗 Repo","2026-03-27T01:21:51.467798+00:00",{"id":136,"slug":137,"title":138,"created_at":139},"80cabc3e-09fc-4ff5-8f07-b8d68f5ae545","ai-trending-github-repos-and-research-feeds-zh","AI Trending：把 AI 資源收成一張表","2026-03-27T01:31:35.262183+00:00"]