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
- 其他SKILL.md.tmpl1.1 KB
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
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.