full-output-enforcement

Apply output enforcement rules that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated fully. The skill counts expected deliverables upfront and cross-checks completeness before responding.

Use enforcement instructions that treat skeletons, first-and-last-section outputs, and "similar to above" shortcuts as hard failures. The AI must write actual runnable code for every function and file requested.

Generation stops at a clean breakpoint such as the end of a function or file, then emits a [PAUSED — X of Y complete] marker. Sending "continue" resumes exactly from that point with no recap or repetition.

Banned patterns include "// ...", "// TODO", "// implement here", "// rest of code", bare ellipses, and prose like "for brevity" or "the rest follows the same pattern". Any of these counts as a failed output.

Avoid it for exploratory brainstorming, quick prototypes, or when you only need a short snippet or high-level outline. The enforcement optimizes for completeness, which adds length unnecessary for casual questions.