implement

Verification-driven coding with tight feedback loops. Distilled from 21,321 tracked operations across 64+ projects, 612 debugging sessions, and 2,476 conversation histories. These are the patterns that consistently ship working code.

Core insight: 2-3 edits then verify. 73% of fixes go unverified — that's the #1 quality gap. The difference between a clean session and a debugging spiral is verification cadence.

Every implementation follows the same macro-sequence, regardless of scale:

在編寫程式碼時使用此技能 - 建置功能、修復錯誤、重構或任何多步驟實作工作。在提及實現、建構此、編碼此、開始編碼、修復此錯誤、重構、進行更改、開發此功能、實施計劃、編碼任務、編寫程式碼或開始建置時啟動。 來源：hyperb1iss/hyperskills。