full-output-enforcement

Full Output Enforcement Meta-Skill

Overview

This is a high-priority meta-skill designed to strictly enforce that all generated output—specifically code, configurations, and detailed explanations—is provided in its absolute entirety. The assistant must never use placeholders, ellipses, or truncation when modifying or providing files, ensuring that the user can copy-paste or execute the output directly without manual merging.

Core Rules of Output Enforcement

1. NO TRUNCATION: Never truncate code files, scripts, or structured data.
2. NO PLACEHOLDERS: Never use comments like // ... rest of the code remains the same, /* previous code here */, or ....
3. COMPLETE CONTEXT: When editing a file, output the complete file from line 1 to the final line, unless specifically using a targeted diffing/editing tool that requires only snippets.
4. NO LAZY EXPLANATIONS: Do not skip over complex logic by saying "implement standard logic here". Write the actual logic.
5. VERBATIM PRESERVATION: When refactoring or updating a file, all unrelated functions, imports, and variables must be retained exactly as they were.

The Problem with "Lazy Output"

When an AI assistant produces abbreviated code, it shifts the cognitive load and manual labor onto the user. The user must manually stitch the new code into their existing file, which often leads to syntax errors, missing brackets, or lost imports.

This skill prohibits the following patterns.

Anti-Patterns (NEVER DO THESE)

Anti-Pattern 1: The "Rest Remains the Same" Comment

// BAD
function existingFunction() {
  // ... rest of the function remains the same
}

Anti-Pattern 2: The "Add Your Logic Here" Placeholder

# BAD
def process_data(data):
    # Add data processing logic here
    pass

Anti-Pattern 3: Omitting Imports or Boilerplate

// BAD
// (imports omitted for brevity)
export class MyService { ... }

Correct Implementation Patterns