AI loves to wrap everything in try/catch, then swallow the error with an empty block, a generic console.log, or a re-throw with no context. The app looks robust and is actually blind. Make every catch do one of three things: recover meaningfully, surface the error to the user, or log it with enough context to debug (what failed, the inputs, the stack). Never an empty catch. This and silently-wrong business logic are the most common and most dangerous AI failures, because nothing tells you they happened.
Prompt to paste
Find every try/catch in this change. For each, tell me whether it recovers from the error, surfaces it to the user, or just swallows it. Flag every silent catch (empty, a bare console.log, or a re-throw with no context) and rewrite it to either handle the error meaningfully or fail loudly with the inputs and stack trace. Don't add any new catch blocks.