full-output-enforcement

Apply explicit output-enforcement instructions that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated completely. This Skill also cross-checks the deliverable count against the original request 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 such as "for brevity" or "the rest follows the same pattern". These signal omitted content and produce non-runnable skeletons instead of complete implementations.

Yes, the same rules apply to prose and structured documents. Banned patterns include phrases like "and so on" replacing actual content, and structural shortcuts such as showing only the first and last sections while skipping the middle.

Avoid it for exploratory brainstorming, quick prototypes, or when you intentionally want a brief sketch. The enforcement treats every task as production-critical, which adds length and latency unnecessary for casual or iterative queries.