full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/po4yka/blog --skill full-output-enforcement-po4yka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/po4yka/blog/tree/main/.agents/skills/output-skill
Command: npx skills add https://github.com/po4yka/blog --skill full-output-enforcement-po4yka

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 code. This Skill overrides that default behavior so every requested deliverable is generated 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. - Token-Limit Handling: When output approaches the token limit, it pauses at a clean breakpoint with a resumable marker instead of compressing or skipping content. - Use Case: Ask for a full implementation of five React components and receive all five complete, runnable files with no skeletons, no omissions, and a clean continuation point if the response hits the token limit. ## 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?

Apply explicit output enforcement rules that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated in full. This Skill locks the deliverable count before generating and cross-checks the output against it.

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 end with a pause marker stating progress and the next section. On "continue", resume exactly where you stopped without recap or repetition.

What placeholder patterns should be banned in AI code generation?

Banned patterns include "// ...", "// 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 output.

When should I not use full-output enforcement?

Avoid it for exploratory questions, quick prototypes, or when a concise summary is explicitly wanted. The enforcement treats every task as production-critical, which adds length that is unnecessary for casual or iterative prompts.