AGENT SKILL

principle-minimize-reader-load

Minimise reader load. Apply when reviewing or shaping code that is hard to follow.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 2
Forks
0

01 前言 Front Matter

name
principle-minimize-reader-load
license
MIT
metadata
{ "source": "pstack principle-minimize-reader-load, MIT, Copyright (c) 2026 Lauren Tan, github.com/cursor/plugins, adapted; checked against pstack 0.15.36 at commit 0bb6f37" }
description
Minimise reader load. Apply when reviewing or shaping code that is hard to follow.

03 SKILL.md 正文

<!-- Generated by scripts/build.mjs from the sources; edit the source, then run npm run build. -->

Minimise reader load

Maintainability is the work a reader does to understand the code. Track two axes: layers to trace (indirections between the question and the answer) and state to hold (hidden or mutable context). Line counts, complexity scores and "clean architecture" are proxies. The axes are independent: a flat file with fifty globals can be as hard as a six-layer adapter stack. Guard both.

  • Collapse layers that cost more than they save: one-caller wrappers, adapters with no second implementation, unneeded indirection.
  • Make each layer change the abstraction. A pass-through layer adds load without compression.
  • Demand interface compression. A boundary hides real decisions; a broad interface that hides little makes the reader learn both sides.
  • Shrink state scope: pure functions over mutation, locals over fields, fields over module state, module state over globals. Derive instead of synchronising.
  • Name the invariant at the boundary, not in every consumer.
  • Add a layer or state only when it saves at least as much reader load elsewhere.

The test. Can a new reader answer "where does X come from?" and "what can change X?" in thirty seconds? If not, cut layers or state. A reviewer reports it in a finding.

04 同仓库更多 Skills

erickb336
erickb336/sage-stack

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.

★ 2
erickb336
erickb336/sage-stack

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.

★ 2
erickb336
erickb336/sage-stack

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.

★ 2
erickb336
erickb336/sage-stack

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.

★ 2
erickb336
erickb336/sage-stack

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.

★ 2
erickb336
erickb336/sage-stack

readme-guide

Write a project README. Apply when you write, change or review a README of any project, in any language.

★ 2