full-output-enforcement

Use explicit output-enforcement instructions that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated fully. This Skill locks the deliverable count upfront and cross-checks it before responding.

Write at full quality up to a clean breakpoint such as the end of a function or file, then emit a pause marker stating progress and the next section. On "continue", resume exactly where you stopped without recap or repetition.

Ban patterns like "// ...", "// TODO", "// implement here", "// similar to above", and prose like "for brevity" or "the rest follows the same pattern". These indicate omitted content and produce non-runnable code.

Yes, the same rules apply to any exhaustive output request, including documentation, lists, and multi-section prose. The scope-counting and cross-check steps work for any countable set of deliverables.

Avoid it for exploratory brainstorming, quick prototypes, or when you explicitly want a short summary or skeleton. Enforcing completeness on open-ended tasks wastes tokens and slows iteration.