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。