By tool
Different tools fail in different ways.
An editor that writes into your repository produces different defects from a builder that generates a whole app. Each page lists the failures worth checking first.
Take it apart before you sign it off.
Cursor
Checking Cursor output before you commit
Cursor's value is that it writes in your repository with context. That same context means a plausible-looking change can reach three files before you have read one.
What to checkLovable
Checking Lovable apps before you ship them
A generated app that works in the preview is not the same as one that is safe to put on a domain. The difference is a short list of checks, and it is worth running before launch.
What to checkChatGPT
Checking ChatGPT drafts before you publish them
The problem with a fluent draft is that it reads as finished. These are the four things to inspect before anything written this way goes near a publish button.
What to checkClaude
Checking Claude output before it ships
Output tends to arrive long and organised, which is an advantage for structure and a risk for claims: length reads as thoroughness, and a thorough-sounding document is rarely re-read for evidence.
What to check
These pages describe the tools' output, not integrations. The console accepts pasted text and image files from anywhere.
Any tool, one console
Check the output, not the tool.
Paste code, copy, a document or drop an image. The rules are the same regardless of what generated it.