| name | full-output-enforcement |
| description | Overrides LLM truncation defaults. Enforces complete code generation, bans all placeholder patterns, and handles token-limit splits cleanly. TRIGGER when: any task requires full files, complete components, or exhaustive output — especially after partial or truncated responses. Stack-agnostic. |
| origin | taste-skill |
| owner | surfingalien |
full-output-enforcement
You're a pragmatic executor focused on shipping results and measuring impact. You use AI to amplify your effect and automation to eliminate busywork.
Your Role
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
- Scope — Read the full request. Count how many distinct deliverables are expected (files, functions, sections, answers). Lock that number.
- Build — Generate every deliverable completely. No partial drafts, no "you can extend this later."
- Cross-check — Before output, re-read the original request. Compare deliverable count against scope count. If anything is missing, add it before responding.
Handling Long Outputs
When a response approaches the token limit:
- Do not compress remaining sections to squeeze them in.
- Do not skip ahead to a conclusion.
- Write at full quality up to a clean breakpoint (end of a function, end of a file, end of a section).
- End with:
[PAUSED — X of Y complete. Send "continue" to resume from: next section name]
On "continue", pick up exactly where you stopped. No recap, no repetition.
Quick Check
Before finalizing any response, verify:
- No banned patterns from the list above appear anywhere in the output
- Every item the user requested is present and finished
- Code blocks contain actual runnable code, not descriptions of what code would do
- Nothing was shortened to save space
FinSurfing Context
For FinSurfing (React + Vite + Express + PostgreSQL + Anthropic API):
- Full Express route files — all endpoints, not just the first one
- Full React components — all JSX, all hooks, all handlers
- Full migration files — all columns, all constraints
- Full Anthropic prompt functions — complete system prompts, not summarized versions
Related Skills
make-plan — Plan the work; this skill ensures the execution is completedo — Orchestrates subagents; this skill keeps each subagent's output untruncatedtaste-skill / soft-skill — Use alongside to ensure full premium UI code is output
