full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation in LLM outputs.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Gito125/gideon_portfolio --skill full-output-enforcement-gito125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/Gito125/gideon_portfolio/tree/main/.github/skills/full-output-enforcement
Command: npx skills add https://github.com/Gito125/gideon_portfolio --skill full-output-enforcement-gito125

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 and unusable output. 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, it pauses at a clean breakpoint with a resumable marker instead of compressing or skipping content. - Use Case: Ask for a full Next.js project scaffold with 12 components. Instead of receiving 3 components and "similar for the rest", you receive all 12 complete, or a clean pause marker with exact resume instructions. ## Quick Start Apply this skill and ask the AI 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 AI from truncating code with placeholder comments?▼

Apply explicit output rules that ban patterns like "// rest of code", "// TODO", and "for brevity". This skill enforces full generation by locking the deliverable count upfront and cross-checking the response before it is sent.

How to get complete multi-file code generation from an LLM?▼

Count the exact number of files or components requested, generate each one fully, and verify the count before responding. If the token limit is reached, pause at a clean breakpoint with a resume marker instead of compressing remaining files.

What happens when generated output exceeds the token limit?▼

The skill writes at full quality up to a clean breakpoint such as the end of a function or file, then emits a pause marker stating progress and the next section. On "continue", generation resumes exactly where it stopped with no recap.

Which output patterns are banned by full-output enforcement?▼

Banned patterns include "// ...", "// implement here", "// similar to above", bare ellipses in code, and prose like "for brevity", "the rest follows the same pattern", and "let me know if you want me to continue".

When should I not use full-output enforcement?▼

Avoid it for exploratory brainstorming, quick prototypes, or when you intentionally want a skeleton or outline. The skill treats every request as production-critical, which adds length and latency to casual queries.