| name | principle-build-the-lever |
| description | Apply when work is repetitive or bulk: many similar edits, a check you'll rerun, a population to transform. Build the tool that amortizes it (codemod, script, generator) once you know the recipe, instead of grinding by hand. |
| disable-model-invocation | true |
Build the Lever
When the work repeats, build the tool that does it instead of grinding by hand.
Why: Doing the same edit a hundred times is slow and drifts into inconsistent mistakes. A codemod, generator, or script does it once, the same way every time, reruns for free, and gives a reviewer one artifact to check.
Pattern: When you would otherwise repeat a transform, a check, or a setup more than a handful of times, build the lever instead.
- Do the first few by hand to learn the exact recipe, then build the tool. Don't build on a guess.
- Codemod or script for bulk edits, generator for repetitive files, a dump-to-sqlite query for repeated analysis, a rerunnable check for repeated verification.
- Commit it when the work outlives the session, so the next run reruns it instead of redoing it.
Balance: Leverage, not gold-plating. The Laziness Protocol still holds. Build the lever only when it pays for itself across the remaining work, never for a one-off.
Distinct from Encode Lessons in Structure, which makes a recurring instruction a durable guardrail. This is throughput on the work in front of you.
