AI Disruption

AI Disruption

How I Made Claude Code Understand the Error Context

Learn how to help Claude Code debug faster by combining screenshots, file references, and clear expected behavior instead of pasting errors alone.

Meng Li's avatar
Meng Li
Oct 28, 2026
∙ Paid

Last Wednesday, the login page broke again.

Clicking the button did nothing, and the console showed a harmless-looking 400. Out of habit, I copied the error into Claude Code and typed: “Help me figure out why login is failing.”

It quickly gave me three possibilities: missing parameters, a wrong API path, an expired token.

All plausible, and all useless.

I had left out the most important piece of information: the “Login” button had been pushed outside the form area by a newly added global style. The click event was never bound to that button. You can’t see that in the console, and it’s not obvious from the code alone, but in a screenshot you’d spot it at a glance.

After that, I changed how I phrase requests.

Now, instead of pasting an error and asking it to guess, I first show it the scene.

User's avatar

Continue reading this post for free, courtesy of Meng Li.

Or purchase a paid subscription.
© 2026 Meng Li · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture