Issue 21 · 25 Sep 2026 · Easy · Free
Error Message Poet
The error tells the developer the stack is unhappy and tells the user nothing about what to do next.
Paste a harsh error. Get a version a person can act on, a short UI string, and a joke you can delete without losing the fix.
- Category
- Fun & Weird
- Runs in
- ChatGPT
- Claude
- Gemini
What you put in and what you get out
You put in
Paste the current error and the facts. Include who sees the string and what they can actually do. Paste the log line separately if it must stay out of the interface.
Agent
Error Message Poet
You get out
The joke, optional. A line about the cart and the typed number disagreeing. The order id stays in the log, not in the joke.
Sample you can paste
Current UI string: "Invariant violation: refund total mismatch (code R3)." What is true: the client sent a total that does not match the cart. The user can reload the order. They cannot fix a database invariant. The audience of this string is the shopper, not the on-call engineer. Log line, already exists, do not put it in the UI: R3 order=1844 expected=40 got=1. Do not joke about the shopper's money in a cruel way.
Share this agent
Error Message Poet — You put in Current UI string: "Invariant violation: refund total mismatch (code R3).". You get out The joke, optional. Free from One Agent a Day.
30-second demo
0:00
The old string
Invariant violation, code R3. A shopper cannot act on that. The log already has the order and the totals.
How it works
The poet returns three strings so the joke cannot hold the fix hostage. You paste the harsh error, who sees it, and what they can do. The plain version is the meaning. The UI string is short enough to ship. The joke can leave.
The joke may tease the software. It may not tease the person, their money, or a group. Internal ids stay in the log. A shopper does not get a stack trace wearing a costume.
Ship the short string. If you love the joke, put it where a frustrated person will still see the action in the same glance.
Use it
Step 1
Paste the current error and the facts
Include who sees the string and what they can actually do. Paste the log line separately if it must stay out of the interface.
Step 2
Paste the prompt
You get three layers: the plain explanation, the short UI string, and a joke. The joke is optional. The UI string is the one you ship.
Step 3
Ship the short string
Put the UI string in the product. Keep the plain explanation in the docs or the log-side comment. Leave the joke out if it softens the action.
Step 4
Read it as the shopper
If the joke names their money, their intelligence, or a group, delete it. The plain string still tells them to reload.
Prompt
error-message-poet.prompt.txt
You rewrite one error for the human who has to see it. You always provide a plain version so a joke cannot be the only instruction.
INPUTS
- Current string.
- Audience: shopper, teammate, or developer.
- What they can do next.
- Facts that must stay in the log and out of the UI.
RULES
- Three outputs: plain, UI, joke.
- The UI string is under 90 characters, names the next action, and contains no stack, no internal code unless the audience is a developer, and no secret.
- The plain version can be longer and still has the action.
- The joke may tease the software. It may not tease the person's body, intelligence, money, identity, or family.
- If the joke needs a cruelty to work, replace it with: "The joke did not survive the rule. Ship the UI string."
- Do not invent a cause beyond the facts they gave.
OUTPUT
## Plain
## UI
## Joke
## Kept in the log
Facts you refused to put in the UI.Related agents
Tomorrow's drop
Get the next agent in your inbox
One email when the drop goes up. No digest, no course. Unsubscribe whenever the provider lets you.
Pro and custom
€9/month when Pro opens
Early look at the next drop, a better archive, and the occasional agent that does not fit the public mix. The daily agent stays free. A custom build is €49–199. Nothing is charged from this form.
Join the Pro waitlist