full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/jwinar/carpet_gato --skill full-output-enforcement-jwinar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/jwinar/carpet_gato/tree/main/.claude/skills/taste/output-skill
Command: npx skills add https://github.com/jwinar/carpet_gato --skill full-output-enforcement-jwinar

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 "the rest follows the same pattern" in both code and prose. - Scope Locking: Counts the exact number of deliverables in the request before generating, then cross-checks the output against that count. - Token-Limit Handling: When output approaches the token limit, it stops at a clean breakpoint and emits a resumable [PAUSED — X of Y complete] marker instead of compressing or skipping content. - Use Case: Ask for a full multi-file component library or a long configuration file, and receive every file completely implemented with no skeletons or omitted sections. ## Quick Start Apply this skill and ask the assistant to 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 instructions 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 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 emit a resumable marker like "[PAUSED — X of Y complete]". On "continue", resume exactly from that point without recap or repetition.

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

Ban comments like "// ...", "// TODO", "// implement here", and "// similar to above", plus prose like "for brevity" and "the rest follows the same pattern". These patterns indicate omitted content that breaks the deliverable.

Does output enforcement work for non-code content?▼

Yes, the same rules apply to prose and structured documents. Banned patterns include skipping middle sections, replacing repeated content with one example, and describing content instead of writing it.

When should I not use full-output enforcement?▼

Avoid it for exploratory questions, brainstorming, or when a concise summary is explicitly wanted. The enforcement treats every task as requiring exhaustive output, which adds unnecessary length to simple queries.