laziness
Apply when sizing a change, reviewing a diff that grew, or tempted to add an abstraction, layer, option or helper. Make the smallest change that solves the problem, and delete before you add.
- License 许可
- MIT
- 最近更新
- 2026-11-04
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- laziness
- metadata
- { "layer": "L2", "source": "cursor/plugins@1e5c90a:pstack/skills/principle-laziness-protocol/SKILL.md + pstack/skills/principle-subtract-before-you-add/SKILL.md", "license": "MIT" }
- description
- Apply when sizing a change, reviewing a diff that grew, or tempted to add an abstraction, layer, option or helper. Make the smallest change that solves the problem, and delete before you add.
03 SKILL.md 正文
Laziness
Make the smallest change that solves the problem. Remove before you build. Every line you add is a line someone has to read, test and keep correct.
Why: Diffs grow by accretion: a helper for one caller, an option nobody sets, a guard for a case that never happens. Each looks cheap alone. Together they bury the change a reviewer needs to see, and they outlive the task that added them.
Pattern:
- One decision, one place. When the same choice shows up in several spots, make it once behind a single source of truth and pass the result down as a plain value.
- Subtract first. Before adding, delete the dead code, stale stubs and redundant checks in the area you touch. Build on the smaller base.
- Build for observed use. Handle the cases the spec and real callers need. No speculative parameters, extension points or validators.
- Cut before you polish. Reach the minimum that works, then spend effort on quality.
- Reuse before you write. Look for an existing function, command or pattern in the repo before adding a new one.
- Plain beats clever. Three plain lines that repeat cost less than an abstraction with one user.
The test:
- Could the diff be smaller and still solve the problem? Then make it smaller.
- Does every new parameter, branch, file and dependency have a caller today?
- Is the touched area simpler than you found it, or at least no more complex?
Stop: Laziness is about the size of the change, not the effort behind it. Never skip the proof, the test or the real cause to keep a diff small. A one-line fix in the wrong place is not lazy; it is unfinished.
04 同仓库更多 Skills
yeet
Take every local change green through the repo's own checks, slice it into conventional commits, push, and with --pr open a pull request on the code host. Use only when the user explicitly asks to yeet, or to commit and push everything; never on your own initiative.
write-docs
Write or update documentation from the code: gather facts, pick the shape for the reader, write it plain, and prove every command and path in it. Use when asked to document a repo, module or feature, or to bring stale docs up to date.
why
Find why code is shaped the way it is (design rationale, trade-offs, regressions, odd thresholds) from history, tickets, docs and chat, citing every claim and stating its confidence. Use for 'why does X work this way', 'why did we pick Y', or before changing code whose purpose is unclear.
verify
Prove a change works with the check that matches its type, do the read-back, and log the pass against the exact tree. Use when a change is ready to call done, before review, commit or stopping, and whenever ven-decisions end refuses an unverified tree.
unslop
Cut AI writing tells (filler, model vocabulary, metaphor nouns, hedging, formatting tics) from text while keeping every fact. Use when editing or checking any prose before it ships: docs, PR bodies, reports, skill text.
type-discipline
Apply when designing types or data shapes, reviewing a signature, or handling outside data, in any language. Make wrong states fail early: in the compiler for typed languages, in validated runtime contracts for untyped ones.