AGENT SKILL

trove-principle-laziness

Laziness Protocol — aim for the most result with the least code and complexity; bias toward deletion and the smallest change that solves the problem. Use when refactoring, weighing diff size, or tempted to add abstractions, layers, or signal threading.

License 许可
MIT
所属仓库
bravew/trove
最近更新
2026-11-12
Stars
★ 10
Forks
1

01 前言 Front Matter

name
trove-principle-laziness
metadata
{ "trove-category": "code", "trove-category-label": "Code" }
description
Laziness Protocol — aim for the most result with the least code and complexity; bias toward deletion and the smallest change that solves the problem. Use when refactoring, weighing diff size, or tempted to add abstractions, layers, or signal threading.
when_to_use
is this over-engineered; simplest change; laziness protocol
user-invocable
true

02 资源文件 1

03 SKILL.md 正文

<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->

Principle: Laziness Protocol

Aim for the most result with the least code and complexity. The best change is often a deletion.

  • Prefer removing code to adding it. Minimize the diff that solves the problem.
  • Don't add abstractions, layers, or config for a single caller or a hypothetical future.
  • Borrow a maintainer's fatigue. If tracing how an answer is produced requires jumping through more than ~3 files or layers, flatten it.
  • Three similar lines beat a premature abstraction.

Prime directive: if a human maintainer would find it exhausting to hold this in their head, it's too complex — simplify before shipping.

04 同仓库更多 Skills