awb-output-guardlisted

# Output guard — finish what you generate > **Announce on activation:** "Using awb-output-guard — I'll generate the whole thing, no stubs." A partial output is a broken output: a truncated function won't import, an empty template renders blank, a query missing its filter returns everything. The cheapest place to catch that is before you hit send. ## Banned in generated code | Where | Don't emit | |---|---| | any language | `# ... rest of <thing>`, `# TODO: implement`, `# same as above`, a bare `pass` / `return None` left as a placeholder | | templates | empty blocks (`{% block x %}{% endblock %}`), `{# ... #}` / `<!-- ... -->` standing in for real markup | | SQL | `-- ... rest of query`, a CTE with no `SELECT`, conditions commented out | | prose around code | "for brevity", "omitted for space", "etc.", "you can add the rest", "similar to above" | ## Too long for one turn? Continue, don't compress Never shrink content to fit a reply. Instead: 1. Write completely **to a clean breakpoint** — end of a function, a closed template block, a finished CTE. 2. Mark where you stopped: `# === NEXT: <the next section> ===`. 3. Say what's left and how to resume: "Wrote through `<X>`. Say 'continue' for the rest." 4. Do **not** treat the file as done — or commit it — until every part is written. ## Before you send - No banned pattern above is present. - Every requested item is there and complete; code blocks hold runnable code, not a description of it. - After writing a long file,