All 141 tools / Interface writing and content
Assemble inline, banner and full-page error message drafts from the problem, cause and fix you give
Error state skeletonFreeFor writers, designers and product teams
25/day
free runs a day, no sign-in.
Before: what you give it
The example input, as typed in. You paste text, CSS, markup or notes.
problem: We could not charge the card ending 4242 cause: the bank declined it fix: Use a different card or ask your bank to allow the payment where: payment form severity: recoverable dataSaved: yes canRetry: yes contact: support
After: what comes back
The first lines of a real run on that input. Nothing here is edited by hand.
Error copy skeleton (recoverable, at payment form). Square brackets mark what you still need to write. Structure: 1. what happened 2. why (only if it helps) 3. what to do next. Put reassurance about lost data only when it is true. Inline (under the field or control): Use a different card or ask your bank to allow the payment. Banner or toast: We could not charge the card ending 4242. The bank declined it. Use a different card or ask your bank to allow the payment. Your changes are saved. Full-page state: Title: We could not charge the card ending 4242 Body: The bank declined it. Use a different card or ask your bank to allow the payment. Nothing you entered has been lost. Buttons: Try again | Contact support ... full output on the tool page
What you get
Three layouts from your wording with bracketed gaps, plus flags for blame, codes and missing next steps
What it cannot do
It assembles your facts into structure; it does not invent the cause or the fix for you.
Who it is for
- Writers
- Designers
- Product teams
Free and Pro
| Free | 25 runs a day per IP address, up to 3,000 characters a run. |
|---|---|
| Pro | No daily limit, 300 requests a minute, up to 200,000 characters a run. |
Use it from your assistant
The tool is called error_state_writer_template. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.
claude mcp add --transport http designers https://designers.allthepossibles.com/mcpcurl -X POST https://designers.allthepossibles.com/api/error-state-template -H 'content-type: application/json' -d '{"problem":"We could not charge the card ending 4242","cause":"the bank declined it","fix":"Use a different card or ask your bank to allow the payment","where":"payment form","severity":"recoverable","dataSaved":"yes","canRetry":"yes","contact":"support"}'Try it here
The form starts with the same example input, so you can run it first and then swap in your own.
More in interface writing and content
- UI copy
Review buttons, errors, empty states and tooltips for what each must do, and flag AI-writing tells.
- Disclosure copy
Score fee, rate, terms, consent and error copy for reading level and flag legalese and vague money words.
- Dark patterns
Look for deceptive-design signals, such as confirmshaming and pre-ticked boxes, in copy, markup or a page.
- Error message check
Find error and status messages that blame, give no next step or vanish too fast, and get a fix template
- Microcopy review
Review buttons, labels, tooltips, empty states and confirmations for vague or filler wording
- Content hierarchy
Check that key terms appear early and headings work on their own, inverted-pyramid style