Go from error message to fix, fast
Ranked likely causes and a quick test for each, instead of guess-and-check.
What most people type
Short prompts like this get generic answers, because the AI has to guess who you are and what you need.
A better prompt
Fill in the blanks
Swap each highlighted part for your own details. Here’s an example.
- [LANGUAGE AND FRAMEWORK]
TypeScript, React 18 - [THE ERROR MESSAGE]
TypeError: Cannot read properties of undefined (reading 'map') at OrderList (OrderList.tsx:14) - [THE CODE THAT FAILS]
const { data } = useOrders(); return <ul>{data.orders.map(o => <li key={o.id}>{o.total}</li>)}</ul> - [WHAT CHANGED RECENTLY]
the orders API was updated yesterday
What a good answer looks like
This is a sample answer for the example above. Yours will be different, so check it against your own facts.
Make it even better
Paste the exact error text, never a paraphrase. Small wording details often point straight to the cause.
Stay safe
Learn the skill behind it
This prompt comes from the course AI for software engineers. The next lesson to watch is “Debug a production error with AI”.
Try this in Tau
In Tau, you can fill in the blanks, run the prompt and get feedback, then watch the one-minute lesson that explains why it works. Join the waitlist for early access.
We’ll only email you about Tau, and you can unsubscribe any time. Privacy policy.
We’ll email you as soon as Tau opens.
More prompts like this
Turn a messy client email into an issues list
Walk into the first call with the issues mapped and the right questions ready.
Draft a method statement from your site notes
A structured first draft in minutes, so your time goes on the engineering checks.
Prepare a one-page brief for a client meeting
Walk in with the client's likely needs and sharp questions, in 5 minutes.
Draft month-end variance commentary fast
Clear variance explanations ready for review, with the maths shown so you can check it.