full-output-enforcement

Enforces complete, unabridged LLM output by banning placeholder patterns and truncation.

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill full-output-enforcement-avatar-arts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/AvaTar-ArTs/.Agent-skills/tree/main/skills/taste-skill/skills/output-skill
Command: npx skills add https://github.com/AvaTar-ArTs/.Agent-skills --skill full-output-enforcement-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLMs frequently truncate long responses, insert placeholder comments like "// rest of code", or skip deliverables to save tokens, leaving users with incomplete code and partial answers that require repeated follow-up prompts. ## Core Features & Use Cases - Placeholder Ban: Hard-blocks patterns such as "// ...", "// TODO", "for brevity", and "the rest follows the same pattern" in both code and prose. - Deliverable Counting: Scopes the request first, locks the expected number of deliverables, and cross-checks the output against that count before responding. - Token-Limit Handling: Pauses at clean breakpoints with a resumable marker instead of compressing or skipping remaining sections. - Use Case: When asking an AI to generate five full React components or a complete configuration file, this Skill ensures every item is delivered in full, runnable form without 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 output-enforcement instructions that ban placeholder patterns like "// rest of code" and require every requested deliverable to be completed. This Skill locks the deliverable count before generation and cross-checks it before responding.

How to handle token limits during long code generation?

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 without recap or repetition.

What placeholder patterns should be banned in AI code generation?

Ban patterns like "// ...", "// TODO", "// implement here", "// similar to above", and prose such as "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 brainstorming, quick prototypes, or when you explicitly want a short summary or skeleton. Enforcing exhaustive output on simple questions wastes tokens and slows iteration.