Developer Message Templates & UX Microcopy Library

Choose and adapt developer messages

Browse reusable interface copy for success states, validation feedback, errors, authentication and account actions. Filter by tone or message type, then adapt the wording to the action the user just completed and the next step they should take.

Replace placeholders such as {entity}, {min}, {max}, {date} and {time} with values from your application. Review each message in context so it remains clear, accurate and accessible.

Write interface messages people can act on

Success messages should confirm the result and, when useful, say what happens next. Validation messages work best beside the field they describe: name the missing or invalid value and give a concrete correction. Error messages should explain whether the action was saved, whether retrying is safe, and what the person can do next; avoid technical stack traces in user-facing copy.

Authentication and account messages need extra care. Never include passwords, full access tokens, or one-time codes in a generic error. Avoid revealing whether an email address or account exists during sign-in and recovery flows unless the product has a deliberate, reviewed reason to do so. Keep wording consistent across screens so the same action is described the same way.

This library offers tone and severity variants so you can compare concise, friendly, formal, and actionable wording. Replace placeholders such as {entity} with escaped, user-appropriate values, and check awkward grammar when a value is missing or plural. Use text as well as color or an icon to communicate status, associate field errors with their inputs for assistive technology, and provide a clear next step when the message describes a problem.