mirror of
https://github.com/cursor/plugins.git
synced 2026-09-14 20:00:00 +08:00
lauren
e8d856f027
* docs(pstack): port the September skill audit cuts from the internal tree Port of the 2026-09-01 to 2026-09-07 audit program on the internal skill tree. Deletion-only density cuts and the mannered prose pass applied wherever the OSS sentence is the same sentence. Two new principle leaves, Attack the Premise and Test Behavior Not Implementation, with their index lines. Critique mode removed from how and its callers. PR-body briefing rules in opening-a-pr and technical-writing. Model pins stay on the setup-pstack role mechanism. No internal path, slug, or name added. * docs(pstack): restore the autopilot chooser rule that multi-phase-plan cites multi-phase-plan step 4 picks between autopilot-full and autopilot-stack "per the rule at the end of playbooks/autopilot-stack.md". The density pass removed that paragraph and left the pointer dangling. Restore the paragraph verbatim. The chooser is a rule, not a restatement, and no other file states it. Addresses the Bugbot finding on PR #329. --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com>
1.3 KiB
1.3 KiB
name, description, disable-model-invocation
| name | description | disable-model-invocation |
|---|---|---|
| principle-laziness-protocol | 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. | true |
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.
- Maintain a flat call hierarchy. Avoid deep call chains. A rich interface that hides substantial work is not a deep call chain. 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.
- Sweat the small leaks. Remove tiny pass-throughs, representation leaks, and duplicated choices before they spread. Small leaks compound into permanent coordination costs.
The test: If a human developer would find the code exhausting to maintain, it is a bad solution.