如何用 Kiro 規格驅動開發構建 PROMETHEUS-iPSC(Kiroween 2026)
Building PROMETHEUS-iPSC with Kiro spec-driven development (Kiroween 2026)
作者以 Kiro 的規格驅動開發構建 PROMETHEUS-iPSC,參加 Kiroween 2026 hackathon;項目包含六項經同行評審的幹細胞實驗,以及設計嵌合體、在生物反應器中培養並參與 16 秒 AI 影片對戰的怪物實驗室。項目設有 7 份規格,並以 21 個 fast-check 檔案進行屬性測試,404 項測試通過。
This post is written as part of the Kiroween 2026 hackathon.
PROMETHEUS-iPSC is my Frankenstein-track entry: a dark lab of six real, peer-reviewed stem-cell experiments, plus a monster lab where you design a chimera, grow it in a bioreactor, and send it into a 16-second AI video battle.
- Live app: https://asura.cafeblanc.kr
- Code: https://github.com/cafeblanc/kiroween
How I used Kiro
1) Spec-driven, not vibe coding. Every feature started as requirements -> design -> tasks under /.kiro/specs (7 specs total). Writing EARS-style "WHEN ... THE SYSTEM SHALL ..." requirements before coding kept a fast, feature-heavy hackathon project from collapsing under its own scope.
2) Agent hooks that paid off. .kiro/hooks/prometheus-lab.json runs related tests on save, scans saved files for leaked tokens, guards private docs, and re-verifies every scientific citation against Europe PMC. That last hook caught a real mistake: my first experiment card claimed a "92% human-brain mouse" the paper (Nature 2022, which used rats) never reported. I corrected it before judging.
3) Steering as guardrails. product.md, tech.md and AGENTS.md held the vision, the key-free API rules, and working rules (retry limits, one dev server, no secrets in the repo).
4) Property-based testing. 21 fast-check files cover stage timing, the 450-point stat budget, and battle odds that are never 0% or 100%. 404 tests pass.
What I learned
Real biology is stranger than fiction, video models need very concrete direction to actually fight instead of posing for the camera, and spec-driven development is what let a solo build stay coherent under a deadline.
來源:DEV Community · dev.to