About principle-laziness-protocol
A development skill for keeping code changes and designs as simple as possible. It recommends deleting unnecessary code, flattening call paths, centralizing decisions, and minimizing diffs to reduce maintenance burden.
Key features
- 01Prefer deletion over additions
- 02Keep call hierarchies flat
- 03Centralize repeated decisions
- 04Minimize code changes
- 05Look for direct paths across layers
- 06Remove small pass-throughs
Use cases
- 01Simplify a requested refactor
- 02Reduce the scope of a code change
- 03Make code easier to maintain
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 filesagents/openai.yaml
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