Agent Skills
› sediman-agent/OpenSkynet
› principle-laziness-protocol
principle-laziness-protocol
GitHub指导在重构、评估代码变更或避免过度抽象时，优先选择删除和最小化改动。倡导保持扁平结构、集中决策并简化信号传递，以最小代码实现目标，确保代码易于维护。
Trigger Scenarios
进行代码重构时
评估差异大小或添加抽象层时
考虑增加信号线程或复杂逻辑时
Install
npx skills add sediman-agent/OpenSkynet --skill principle-laziness-protocol -g -y
SKILL.md
Frontmatter
{
"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.",
"disable-model-invocation": true
}
Laziness Protocol
Writing code is cheap for you, which makes over-engineering easy. Counter it by borrowing a human maintainer's fatigue. 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 hierarchy. Avoid deep abstractions. 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.
Prime directive: If a human developer would find the code exhausting to maintain, it is a bad solution. Be lazy. Stay simple.
Version History
- c9d8953 Current 2026-07-05 19:53
