full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated May 21, 2025
One-click install
npx skills add https://github.com/nielslataire/Group-LN --skill full-output-enforcement-nielslataire
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/nielslataire/Group-LN/tree/main/.agents/skills/full-output-enforcement
Command: npx skills add https://github.com/nielslataire/Group-LN --skill full-output-enforcement-nielslataire

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLMs often truncate long outputs, insert placeholder comments like "// rest of code", or skip deliverables to save tokens, leaving users with incomplete and unusable results. This Skill overrides that default behavior so every requested file, function, or section is delivered in full. ## Core Features & Use Cases - Placeholder Ban: Hard-fails on patterns like "// ...", "// TODO", "for brevity", and "the rest follows the same pattern" in both code and prose. - Scope Locking: Counts the exact number of requested deliverables before generating, then cross-checks the output against that count before responding. - Token-Limit Handling: When output approaches the token limit, stops at a clean breakpoint with a resumable pause marker instead of compressing or skipping content. - Use Case: Ask for a full multi-file project scaffold or five complete React components, and receive every file and component fully implemented with no skeletons or omissions. ## Quick Start Apply the full-output-enforcement skill and generate the complete implementation of all requested files with no placeholders or omissions.

Frequently Asked Questions about full-output-enforcement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an LLM from truncating code output?▼

Use explicit anti-truncation rules that ban placeholder patterns like "// rest of code" and "for brevity". This Skill locks the deliverable count before generation and cross-checks the output so nothing is skipped or shortened.

How to handle token limits when generating long code files?▼

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. On "continue", resume exactly from that point with no recap or repetition.

What placeholder patterns should be banned in AI code generation?▼

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

Does output enforcement work for non-code content?▼

Yes, the same rules apply to prose and structured documents. Banned phrases like "for brevity" and "let me know if you want more" are treated as failures in any deliverable type, not just code.

When should I not use full-output enforcement?▼

Avoid it for quick exploratory questions, brainstorming, or when a short illustrative snippet is genuinely sufficient. Enforcing exhaustive output on simple queries wastes tokens and slows down iteration.