principle-laziness-protocol
Laziness protocol. Apply when refactoring, judging a diff's size, or tempted to add an abstraction, a layer or a threaded signal.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- principle-laziness-protocol
- license
- MIT
- metadata
- { "source": "pstack principle-laziness-protocol, MIT, Copyright (c) 2026 Lauren Tan, github.com/cursor/plugins, adapted; checked against pstack 0.15.36 at commit 0bb6f37" }
- description
- Laziness protocol. Apply when refactoring, judging a diff's size, or tempted to add an abstraction, a layer or a threaded signal.
03 SKILL.md 正文
<!-- Generated by scripts/build.mjs from the sources; edit the source, then run npm run build. -->
Laziness protocol
Aim for the most result with the least code and complexity.
- Prefer deletion. When asked to refactor or improve, look for removals before additions.
- Keep the call hierarchy flat. If answering a question means tracing through more than three files or layers, flatten it. A rich interface that hides real work is fine; a chain of thin layers is not.
- Consolidate decisions. Do not repeat the same choice in several places. Put it behind one source of truth and pass the result on as a simple flag.
- Minimise the diff. Make the smallest change that solves the problem. Fewer lines beat elegant boilerplate.
- Question the threading. If the task asks you to pass a new signal through types, schemas, pipelines or similar layers, look for a more direct path first.
- Sweat the small leaks. Remove tiny pass-throughs and duplicated choices before they spread.
The test. If a developer would find the code exhausting to maintain, it is a bad solution.
04 同仓库更多 Skills
writing-standard
Write at 80% of Simplified Technical English. Apply to any text an agent writes for a person: messages, reports, specs, findings, reviews, plans.
sage
The state tool of sage mode: records tasks, routes, agent runs, findings, verdicts by head SHA and the user's gates in ~/.claude/sage/<project>/. Use in sage mode for every change of a task's state, and before any merge. Claude Code only.
sage-help
Help with sage: how to set it up, switch sage mode and autopilot, read the board, answer the chief's questions, pick a skill or a principle, fix a run that went wrong, and find where sage keeps its files. The user types /sage:sage-help (or /sage-help) with a question. Load it only when the user types it; do not load it on your own. Claude Code only.
report
The report that every sage agent ends with: STATUS, RESULT, EVIDENCE, FINDINGS, QUESTIONS, NOT VERIFIED, BRANCH. Use at the end of any task that the sage chief of staff gave you. Claude Code only.
remote-control
Set up Remote Control, so that the user can follow, steer and start Claude Code sessions from the Claude app on a phone. It turns Remote Control on for every new session, and it can run a server in a folder (such as ~/workspace) that starts at each login. Use when the user asks to reach sessions or start new ones from a phone, or to set up, check or undo Remote Control. Claude Code only.
readme-guide
Write a project README. Apply when you write, change or review a README of any project, in any language.