About principle-laziness-protocol
A coding skill that guides developers toward simpler implementations by reducing code, abstractions, and repeated decisions. It emphasizes minimal changes and maintainability over adding structure for its own sake.
Key features
- 01Prefer deletion over additions
- 02Keep hierarchies shallow
- 03Centralize repeated decisions
- 04Minimize changes
- 05Seek direct paths through layers
Use cases
- 01Simplify a requested refactor
- 02Reduce abstractions in complex code
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.
Details
From the project READMELaziness Protocol
Writing code is cheap for you, which makes over-engineering easy. Counter it by borrowing a human maintainer's fatigue. 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 hierarchy. Avoid deep abstractions. 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.
Prime directive: If a human developer would find the code exhausting to maintain, it is a bad solution. Be lazy. Stay simple.
Comments
Markdown supported