Error message decode
Read an error message back in plain words, separate what it states from what it implies, and rank the causes by how cheap they are to check.
The prompt
Read this error message back to me. What I was doing: CONTEXT. Where it appeared: WHERE. Error, in full: PASTE IT Five parts. Plain reading. What the message says, in one or two sentences. What it states. The facts the message itself contains: the component, the operation, the code, the value. Quote them. What it does not state. What people will assume from this message that it does not actually say. Misreadings here cost more time than the error does. Likely causes, ranked. For each: the cause, why this message would appear if that were true, and the cheapest way to check it. Rank by cost to check, not by likelihood, because a five second check on a less likely cause beats an hour on a more likely one. What would tell us more. Which log, which flag, which command output, stated specifically. Rules. You cannot see my system, so distinguish clearly between what the message proves and what you are inferring. If the message is truncated or the important part is missing, say what part you need. Do not guess a version specific behaviour: say what to confirm.
How to use it
Run this in Chat. It is a thinking tool, not a deliverable.
Use when an error is unfamiliar and you want the reading before you start changing things.
Vibe prepares and drafts. You verify and decide. Ask for a citation on every finding: a confident answer is not evidence.
What you get back
A plain reading, what the message does and does not state, ranked candidate causes with a cheap check for each.
What it writes
Nothing. This one only answers.
From the source file in awesome-mistral-vibe-prompts, CC BY-SA 4.0. Not affiliated with, or endorsed by, Mistral AI.