Imported from michael-denyer/pstack-claude (plugins/pstack/skills/principle-laziness-protocol/SKILL.md). Install upstream with npx skills add michael-denyer/pstack-claude --skill principle-laziness-protocol. Copyright stays with the author.

Laziness Protocol

Name: principle-laziness-protocol
Author: michael-denyer

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.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

{ "ocm": "1", "id": "michael-denyer-pstack-claude-principle-laziness-protocol", "kind": "skill", "name": "principle-laziness-protocol", "description": "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.", "publisher": "michael-denyer", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/michael-denyer/pstack-claude", "path": "plugins/pstack/skills/principle-laziness-protocol/SKILL.md", "ref": "HEAD", "url": "https://github.com/michael-denyer/pstack-claude/blob/HEAD/plugins/pstack/skills/principle-laziness-protocol/SKILL.md", "key": "michael-denyer/pstack-claude/plugins/pstack/skills/principle-laziness-protocol/SKILL.md" } }, "instructions": "# Laziness Protocol\n\nAim for the most result with the least code and complexity.\n\n- **Prefer deletion.** When asked to refactor or improve, look for removals before additions.\n- **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.\n- **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.\n- **Minimize the diff.** Make the smallest change t", "cost": { "context_tokens": 276 } }

principle-laziness-protocol

About

Laziness Protocol

Use it

Manifest

Reviews