← LeaderboardThe Skill Leaderboard

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.

Published by michael-denyer ↗michael-denyer/pstack-claude

Try your first task

principle-laziness-protocol

Start a fresh conversation. Replace the highlighted placeholders.

Use principle-laziness-protocol to refactor [code area] for [goal], favoring deletion and the smallest maintainable change; avoid unnecessary abstractions, deep call chains, and signal threading.

Required inputs

  • [code area]
  • [goal]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: principle-laziness-protocoldescription: "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."user-invocable: false

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.