full-output-enforcement

Use explicit anti-truncation rules that ban placeholder patterns like "// rest of code" and "for brevity". This Skill locks the deliverable count upfront, generates every item fully, and cross-checks completeness before responding.

Request full implementations and prohibit structural shortcuts such as showing only first and last sections. The Skill treats partial output as broken output and requires runnable code in every block rather than descriptions of what code would do.

The output pauses at a clean breakpoint, such as the end of a function or file, and ends with a marker like "[PAUSED — X of Y complete]". Sending "continue" resumes exactly from that point with no recap or repetition.

Banned patterns include "// ...", "// TODO", "// implement here", "// similar to above", bare ellipses, and prose like "the rest follows the same pattern" or "let me know if you want me to continue". Any of these counts as a hard failure.

Avoid it for exploratory brainstorming, quick prototypes, or when you only need a short illustrative snippet. The enforcement optimizes for completeness over brevity, which adds unnecessary length to casual or partial requests.