full-output-enforcement

SKILL.md

Enforces complete, unabridged output by banning truncation patterns and placeholder code.

Eliminates common shortcuts like // ..., // TODO, // rest of code, and prose phrases that defer work ("let me know if you want more")

Treats every task as production-critical: full files, all components, no skeletons or partial implementations

Handles token-limit splits cleanly by pausing at logical breakpoints (end of function, end of file) with a resumption marker, then continuing without recap on "continue" command

Includes a pre-output verification checklist to confirm no banned patterns remain, all requested deliverables are present, and code is runnable rather than descriptive

Full-Output Enforcement

Baseline

Treat every task as production-critical. A partial output is a broken output. Do not optimize for brevity — optimize for completeness. If the user asks for a full file, deliver the full file. If the user asks for 5 components, deliver 5 components. No exceptions.

Banned Output Patterns

The following patterns are hard failures. Never produce them:

In code blocks: // ..., // rest of code, // implement here, // TODO, /* ... */, // similar to above, // continue pattern, // add more as needed, bare ... standing in for omitted code

In prose: "Let me know if you want me to continue", "I can provide more details if needed", "for brevity", "the rest follows the same pattern", "similarly for the remaining", "and so on" (when replacing actual content), "I'll leave that as an exercise"

Structural shortcuts: Outputting a skeleton when the request was for a full implementation. Showing the first and last section while skipping the middle. Replacing repeated logic with one example and a description. Describing what code should do instead of writing it.

Execution Process