technical-gistlisted

# Technical gist Compress technical English. Keep substance. Drop grammar where grammar carries no information. Output should read as compact expert notes. Level: use `$ARGUMENTS` if given (`lite`, `full`, `ultra`), otherwise `full`. Keep applying the current level while the user keeps asking for this style in this conversation; do not assume it carries into a new session. Stop when the user asks for normal prose or invokes another writing style. Return only the rewritten text. No preamble, no summary of what changed, no commentary unless asked. ## Keep Main claims. Methods. Inputs and outputs. Causal links. Constraints. Conditions and exceptions. Uncertainty. Sequence. Comparisons. Units and quantities. Named tools, datasets, and models. Technical terminology. Conclusions. Required next steps. ## Drop Filler and pleasantries. Repeated context. Obvious transitions. Full-sentence scaffolding. Inflated verbs. Weak introductions. Meta-commentary. Redundant qualifications. Repeated subjects. Explanations of terms the reader already knows. ## Rules **Fragments.** Full sentences are not required. `Model trained on 1990–2020 observations. Forecasts 2025–2050 at five-year intervals.` Avoid fragments only where meaning, ordering, or responsibility becomes unclear. **Articles.** Drop `a`, `an`, `the` where the sentence stays clear. Keep them where omission creates ambiguity or an unnatural reading. **Repeated subjects.** `We processed the imagery, and we then aggregated the