full-output-enforcement

Enforces complete code generation by banning placeholder patterns and managing token-limit splits.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill full-output-enforcement-desarrolloainia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/desarrolloainia/nuevo_circuito_mir/tree/main/frontend/.agents/skills/full-output-enforcement
Command: npx skills add https://github.com/desarrolloainia/nuevo_circuito_mir --skill full-output-enforcement-desarrolloainia

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 broken or incomplete code. 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 skeleton-only responses, forcing actual runnable code. - Scope Locking & Cross-Check: Counts expected deliverables before generating and verifies the count before responding, so nothing is silently dropped. - Clean Token-Limit Handling: When output approaches the token limit, it pauses at a clean breakpoint with a resume marker instead of compressing or skipping content. - Use Case: Ask for five React components or a full configuration file, and receive all five complete implementations with no "similar to above" shortcuts. ## 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 output enforcement rules that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated completely. The Skill locks the deliverable count before generating and cross-checks it before responding.

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 with no 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 count as hard failures.

When should I not use full-output enforcement?▼

Avoid it for exploratory questions, quick snippets, or brainstorming where brevity is appropriate. It is designed for tasks explicitly requiring exhaustive output, such as full file implementations or a fixed number of complete components.