Principle Laziness Protocol

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

107 stars 21 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Dimon94/skills --skill principle-laziness-protocol
Manual install
git clone --depth 1 https://github.com/Dimon94/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/principle-laziness-protocol ~/.claude/skills/principle-laziness-protocol

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Laziness Protocol

- **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.
Read the full skill on GitHub

Details

Skill name
principle-laziness-protocol
Repository
Dimon94/skills
Path
skills/principle-laziness-protocol/SKILL.md
Repo updated
18 November 2026
Copies
Found in 3 GitHub repos

FAQ

What does the Principle Laziness Protocol skill do?

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

How do I install the Principle Laziness Protocol skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dimon94/skills --skill principle-laziness-protocol. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Principle Laziness Protocol popular?

It lives in Dimon94/skills, which has 107 GitHub stars and 21 forks, and is included in 2 curated skill lists.

Related skills

Maintain Verification Skill

107

Dimon94/skills

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".

Git & Code ReviewIn 2 lists21

Create Verification Skill

107

Dimon94/skills

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.

Software DevelopmentIn 2 lists21

How

107

Dimon94/skills

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

Software DevelopmentIn 2 lists21

Principle Migrate Callers Then Delete Legacy Apis

107

Dimon94/skills

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

Software DevelopmentIn 2 lists21

Principle Boundary Discipline

107

Dimon94/skills

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.

Software DevelopmentIn 2 lists21

Principle Minimize Reader Load

107

Dimon94/skills

Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.

Software DevelopmentIn 2 lists21

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.