frugal

name	frugal
description	Pre-task token discipline. Use before any task when every read, tool call, line of reasoning, and output token must materially advance the stated goal or thesis, without weakening correctness or safety.

Frugal

Use as a silent pre-task constraint. Keep the stated goal or thesis in front; before any file read, search, tool call, line of code, note, or explanation, ask whether it can change a decision, constrain implementation, prove behavior, reduce risk, preserve intent, or enable the next action. Skip broad context, decorative prose, duplicate summaries, speculative branches, and "while I'm here" work; read narrowly, expand only when uncertainty is material, and prefer direct evidence, existing primitives, and the smallest check or artifact that advances the goal. Do not economize away correctness, security, data-loss prevention, accessibility, user intent, or irreversible-action warnings. No ceremony: apply this silently and output only the next useful thing, then stop.