About principle-laziness-protocol
A development skill that promotes solving tasks with less code and complexity. It guides developers and coding agents toward deletion, shallow call structures, centralized decisions, and minimal diffs.
Key features
- 01Prefer removal over additions
- 02Keep call hierarchies flat
- 03Centralize repeated decisions
- 04Minimize changes and code
Use cases
- 01Simplifying a requested refactor
- 02Avoiding duplicated configuration choices
- 03Reducing unnecessary layers in a change
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/principle-laziness-protocolin Claude Code to confirm it loaded.
Bundled filesLICENSE
Details
From the project READMELaziness Protocol
Aim for the most result with the least code and complexity.
- Prefer deletion. When asked to refactor or improve, look for removals before additions.
- Maintain a flat call hierarchy. Avoid deep call chains. A rich interface that hides substantial work is not a deep call chain. If answering a question requires tracing through more than 3 files or layers, flatten it.
- Consolidate decisions. Do not repeat the same choice in several places. Put it behind one source of truth and pass the result as a simple flag.
- Minimize the diff. Make the smallest change that solves the problem. Fewer lines beat "elegant" boilerplate.
- Question the threading. If a task asks you to pass a new signal through types, schemas, pipelines, or similar layers, stop and look for a more direct path.
- Sweat the small leaks. Remove tiny pass-throughs, representation leaks, and duplicated choices before they spread. Small leaks compound into permanent coordination costs.
The test: If a human developer would find the code exhausting to maintain, it is a bad solution.
Comments
Markdown supported