Skip to main content
UI Guides

Search rules

Search all UI Guides rules by name, category, or source

contentVercel

Errors Include the Fix

MUST

MUST: Every error message states the fix, not just the problem: the expected format, the missing permission, or a link/button to the place the user can resolve it.

State what went wrong, what correct looks like, and give the user the next step

Bad

Good

Why it matters

An error that only names the problem ("Invalid input") leaves the user guessing which of several rules they broke. Pair the diagnosis with a concrete remedy — the expected format, the missing permission, a link or button to the place where they can fix it — so the message ends the dead end instead of announcing it.

References

Built by Gleb Stroganov, design engineer at Evil Martians.

The rules come from other people's skills and guidelines — Vercel, Rauno Freiberg, @Ibelick, impeccable, Emil Kowalski, Tailwind, RAMS — each one credited on the Sources page. The work here is extraction and wiring: every rule is pulled into one corpus, given a good and a bad example you can operate, a MUST/SHOULD/NEVER rule an agent can paste, and a link back to where it came from.