full-output-enforcement

Name: full-output-enforcement
Availability: InStock
Author: javiruu

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Mar 26, 2026

Search Tags:#code generation #token limit #llm prompting #output enforcement #placeholder ban #complete output

Ready to run

npx skills add https://github.com/javiruu/viru-air --skill full-output-enforcement-javiruu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/javiruu/viru-air/tree/main/.agents/skills/full-output-enforcement
Command: npx skills add https://github.com/javiruu/viru-air --skill full-output-enforcement-javiruu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLMs often truncate long outputs, insert placeholder comments like "// rest of code", or ask "want me to continue?" instead of delivering complete results. 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 skeleton-only outputs. - Scope Locking: Counts expected deliverables before generating and cross-checks completeness before responding. - Token-Limit Handling: Stops at clean breakpoints with a structured `[PAUSED]` marker and resumes exactly on "continue" without repetition. - Use Case: Ask for a full multi-file implementation (e.g., five React components with tests) and receive every file completely, with no omitted sections or "similar to above" shortcuts. ## 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 output?▼

Apply output enforcement rules that ban placeholder patterns like "// rest of code" and require every requested deliverable to be generated fully. The skill counts expected deliverables upfront and cross-checks completeness before responding.

How to get complete code instead of skeleton implementations?▼

Use enforcement instructions that treat skeletons, first-and-last-section outputs, and "similar to above" shortcuts as hard failures. The AI must write actual runnable code for every function and file requested.

What happens when output exceeds the token limit?▼

Generation stops at a clean breakpoint such as the end of a function or file, then emits a [PAUSED — X of Y complete] marker. Sending "continue" resumes exactly from that point with no recap or repetition.

Which placeholder patterns are banned in generated code?▼

Banned patterns include "// ...", "// TODO", "// implement here", "// rest of code", bare ellipses, and prose like "for brevity" or "the rest follows the same pattern". Any of these counts as a failed output.

When should I not use full-output enforcement?▼

Avoid it for exploratory brainstorming, quick prototypes, or when you only need a short snippet or high-level outline. The enforcement optimizes for completeness, which adds length unnecessary for casual questions.