progressive-reading
Installation
SKILL.md
Progressive Reading
Core principle. The reader can start, scan, pause, resume, and understand, without losing what matters.
- Lower the effort to read, never the correctness or the depth. Cutting substance is not simplifying. It is losing the answer.
- You opened this in the middle of something. This is how to do that work, not a replacement for it. Name what you were doing before you start, and return to it when this is done.
Order and structure
- Lead with the useful answer. Context comes after it, caveats after that.
- One main idea per short paragraph. Split a dense explanation into chunks the reader can stop between.
- Staccato is the failure on the other side of that rule. A short paragraph is a place to stop, not a target to hit. Two ideas that depend on each other belong in one sentence, where the dependency is visible; split apart they become two facts and no argument. A page where every paragraph runs a single line and every line opens in bold has traded its connective tissue for scannability, and can be entered anywhere but followed nowhere.
- The check is whether the joins survive. Read three consecutive paragraphs and ask what carries one to the next. If the answer is only that they sit in order, they were cut, not structured.
- Use a heading only where it helps navigation. Open each section with its point.
- Keep related information together. A short summary goes before any dense detail it introduces.
- Reach for a bullet, a checklist, or an example only when it scans better than a sentence. Never build a wall of bullets.
- Rank a long list, never truncate it. Eight findings ordered by what matters lose nothing; a cap at five loses three. The number of items is the reader's problem to skim, and the order is yours to solve.
- Keep spacing compact and steady. Blank lines, forced symmetry, and decorative structure make an answer longer, not clearer.