full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/divinaarmuela/Content --skill full-output-enforcement-divinaarmuela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/divinaarmuela/Content/tree/main/.claude/skills/full-output-enforcement
Command: npx skills add https://github.com/divinaarmuela/Content --skill full-output-enforcement-divinaarmuela

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. 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 code and prose. - 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 for a full multi-file project scaffold or five complete React components, and receive every item fully implemented with no 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 anti-truncation rules that ban placeholder patterns like "// rest of code" and "for brevity". This Skill locks the deliverable count upfront, generates every item fully, and cross-checks completeness before responding.

How to get complete code instead of skeleton implementations?

Request full implementations and forbid structural shortcuts such as showing only the first and last sections. The Skill treats skeletons, omitted middles, and described-instead-of-written code as hard failures.

What happens when the output exceeds the token limit?

Generation stops at a clean breakpoint such as the end of a function or file, then emits a pause marker stating progress. 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", "// similar to above", bare ellipses, and prose like "the rest follows the same pattern" or "and so on" replacing actual content.

When should I not use full-output enforcement?

Avoid it for exploratory brainstorming or quick prototypes where brevity is preferred. The Skill treats every task as production-critical and always optimizes for completeness over conciseness.