skills.rest
cherishwins
cherishwinsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

full-output-enforcement

Enforces complete code generation by banning placeholder patterns and truncation.

3|Updated Apr 25, 2026
Search Tags:#code generation#completeness#token limit#llm output#prompt instructions#anti-truncation#placeholder ban
One-click install
npx skills add https://github.com/cherishwins/npsi-site --skill full-output-enforcement-cherishwins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: full-output-enforcement
Source: https://github.com/cherishwins/npsi-site/tree/main/.agents/skills/full-output-enforcement
Command: npx skills add https://github.com/cherishwins/npsi-site --skill full-output-enforcement-cherishwins

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 both code and prose. - Scope Locking: Counts the exact number of requested deliverables before generating, then cross-checks the output against that count. - Token-Limit Handling: When output approaches the limit, it 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 one of them 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?▼

Apply explicit output-enforcement instructions that ban placeholder patterns like "// rest of code" and require a deliverable count check before responding. This Skill locks the expected scope, generates every item fully, and cross-checks completeness before finalizing.

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 and the next section. On "continue", resume exactly from that point with no 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 "and so on" when replacing real content. These indicate truncated or skeleton output instead of complete implementations.

When should I not use full-output enforcement?▼

Avoid it for exploratory brainstorming, quick prototypes, or when you only need a sketch of an approach. Enforcing exhaustive output on small questions wastes tokens and slows iteration.

Related Skills

Explore More Software Engineering Skills→
edupazogleedupazogle

full-output-enforcement

Enforce complete, non-truncated code generation with resumable output markers.

Community
Intermediate
Long-NguyenHaiLong-NguyenHai

verification-loop

Verify Claude Code sessions with build, type, lint, test, security, and diff checks.

Community
Advanced
sheawinklersheawinkler
78

requesting-code-review

Automate pre-commit verification with static scans, tests, linting, and reviewer gates.

Community
Advanced
fegome90-cmdfegome90-cmd

superpowers-brainstorming

Generate structured design options and validate concepts through iterative dialogue.

Community
Intermediate