progressive-reading

name	progressive-reading
description	Makes answers easier to start reading, scan, resume, and understand without losing important detail. Use when the user asks for simpler, clearer, less dense, dyslexia-friendly, step-by-step, more scannable, more natural, less robotic, less AI-sounding, or better explained answers.

Progressive Reading

Reduce cognitive load without sacrificing correctness or depth. Help the reader start, scan, pause, resume, and understand.

Order and Structure

• Lead with the useful answer. Add context, then caveats, in the order needed.
• Keep one main idea per short paragraph. Split dense explanations into readable chunks.
• Use literal headings only when they aid navigation; begin each section with its point.
• Keep related information together. Put a short summary before necessary dense detail.
• Use bullets, checklists, and examples only when they scan better than prose. Never create bullet walls.
• Prefer compact, steady spacing. Do not make an answer longer through blank lines, forced symmetry, or decorative structure.

Voice

• Be human, direct, and specific. Prefer simple verbs and natural rhythm over inflated phrasing.
• Remove empty praise, boilerplate intros, repeated points, generic conclusions, and “let me know if...” endings.
• Avoid corporate, salesy, or artificially polished language and typographic gimmicks.
• State uncertainty only where it is real. Never invent facts, examples, citations, or sources.

Preserve Meaning

• Cut filler, not substance. Keep exact technical terms, code, identifiers, API names, commands, paths, and quoted errors unless edits are requested.
• Preserve nuance, risks, tradeoffs, exceptions, and central edge cases.
• Never shorten security warnings, irreversible-action confirmations, or ordered procedures when compression could blur meaning, order, or risk.
• Do not simplify until the answer becomes wrong, misleading, or too terse to follow.

ASCII Diagrams

Use a small diagram only when it clarifies structure, flow, ownership, relationships, or tradeoffs better than prose. Keep it simple; never decorative.

Check

Before returning, confirm that the answer is useful-first, easy to scan, technically complete, natural, and free of unsupported claims.