Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cursor/principle-minimize-reader-load
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
Passed 21 of 23 test cases with the skill, and 21 of 23 without it.
1 fixed20 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
An internal user management service exposes an interface with 28 public methods covering raw database queries, session tokens, audit logging, and email sending. Most callers only need to verify if a user has an active subscription. How should this interface boundary be refactored?
| Checked | Without skill | With skill |
|---|---|---|
| Recommend narrowing the interface to expose high-level domain operations. | Passed | Passed |
| Recommend hiding low-level session details behind the service boundary. | Missed | Passed |
The instructions your model reads when the skill loads.
Maintainability is the work a reader must do to understand code. Track two axes:
Why: Code is read far more than it is written. LOC, cyclomatic complexity, and "clean architecture" are proxies. Reader load is the thing that matters. The two axes are independent. A flat file with 50 globals can be as hard to reason about as a 6-layer adapter stack. Guard both. This is the human analog of Guard the Context Window. Working memory is finite for readers too.
The pattern:
The test: Can a new reader answer "where does X come from?" and "what can change X?" in under 30 seconds? If not, cut layers or cut state.
test cases passed, vs 21 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.