full-output-enforcement

Apply explicit output-enforcement rules that ban placeholder patterns like "// rest of code" and "for brevity". This Skill locks the expected deliverable count before generation and cross-checks it before responding, so nothing is silently omitted.

Instruct the model to treat partial output as failure and forbid structural shortcuts like first-and-last-section patterns. This Skill enforces full implementations with runnable code rather than descriptions of what the code would do.

The output 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", "// 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 quick exploratory questions, brainstorming, or when a short summary is genuinely what you want. The enforcement optimizes for completeness over brevity, which adds unnecessary length to simple conversational answers.