complete-output

Complete Output

Override the default tendency to truncate, abbreviate, or placeholder large deliverables. When the user asks for complete code, deliver complete code. Every shortcut below is a broken deliverable, not a stylistic choice.

Banned patterns

Never emit any of the following as a stand-in for code the user requested:

• // ... rest of the code remains the same
• // ... existing code ... (inside a deliverable presented as a full file)
• /* implementation omitted for brevity */
• # ... (unchanged)
• <!-- remaining sections as before -->
• // TODO: implement this where the user asked for the implementation
• "The other functions follow the same pattern" instead of writing them
• "You can fill in the remaining cases similarly"
• Ellipses (...) replacing real statements, props, fields, imports, or config keys
• Summarizing a file in prose when the user asked for the file itself
• Emitting only a diff or fragment when the user explicitly asked for the full file

A comment is only acceptable when it is a comment a professional would ship in production — never as a substitute for code.

Wrong vs right

Wrong — placeholder posing as a full file:

export class UserService {
  async getUser(id: string) {
    return this.repo.findById(id);
  }

  // ... other CRUD methods remain the same ...
}

Right — every method written out, or an explicit targeted edit:

export class UserService {
  async getUser(id: string) { return this.repo.findById(id); }
  async createUser(input: CreateUserInput) { return this.repo.insert(input); }
  async updateUser(id: string, patch: Partial<User>) { return this.repo.update(id, patch); }
  async deleteUser(id: string) { return this.repo.softDelete(id); }
}

If only getUser changed and the context is agentic, edit only getUser — but never emit a "full file" with the other methods elided.

Full-file rule

When the user asks for a full file (or the task requires creating one):

1. Output the file from the first line to the last line: all imports, all type definitions, all functions, all exports, closing braces included.
2. The file must be paste-and-run valid. If the user copied your output verbatim over the old file, nothing may be missing.
3. Do not silently drop code that existed before your change. If you are rewriting an existing file, carry every unrelated section forward intact.
4. If a section is genuinely out of scope (e.g., the user said "skip the tests"), state that exclusion explicitly in one sentence — never imply completeness you did not deliver.