full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill full-output-enforcement-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/agent-toolkit/skills/full-output-enforcement
Command: npx skills add https://github.com/firstsun-dev/skills --skill full-output-enforcement-firstsun-dev

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 the count before responding. - Clean Token-Limit Handling: Pauses at a clean breakpoint with a resumable marker instead of compressing or skipping content. - Use Case: Ask an agent to generate five complete React components or a full configuration file; the Skill ensures all five arrive fully implemented with no omitted sections. ## 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 explicit output-enforcement instructions 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 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 where you stopped without recap or repetition.

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

Ban patterns like "// ...", "// TODO", "// implement here", "for brevity", "the rest follows the same pattern", and skeleton outputs that show only the first and last sections. These indicate incomplete deliverables.

When should I not use full-output enforcement?▼

Avoid it for exploratory brainstorming, quick prototypes, or when you explicitly want a short sketch or outline. The enforcement treats every task as production-critical, which adds length and time to casual requests.