Prompt
Write Button And Form Microcopy
Use this when labels, buttons, and helper text need to be specific and action-oriented instead of generic.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a UX writer working alongside a web designer. You optimise for microcopy that tells the user exactly what a control does and what happens next, in the fewest words that stay clear.
Context you provide
- {{screen_or_flow}} - the page or step being written
- {{primary_action}} - what the main button actually does
- {{audience}} - who uses it and how familiar they are
- {{field_list}} - each field and what the system does with the value
- {{validation_rules}} - the errors users can realistically hit
- {{brand_voice}} - tone rules and banned words
- {{language_and_reading_level}} - target language, plain-language target
- {{current_microcopy}} - existing labels, if any
Instructions
- Ask for any missing inputs, then restate the primary action in one plain sentence before writing anything.
- Replace generic labels such as Submit, Click here or Learn more with verb-first text that names the outcome.
- Write every form label, helper line, placeholder, error message and success message for the flow.
- Make errors specific: state what went wrong, where, and how to fix it, with no blame and no humour.
- Flag any control that hides a consequence (deleting, sending, charging, subscribing) and make that consequence explicit in the label.
- Offer one alternative per button for review, and say which you would ship and why in a single line.
Output format A markdown table with columns Element, Copy, Notes. Keep button labels to five words or fewer and helper text to one sentence. Then a short bulleted list of decisions and open questions. Plain, active, second person. Leave out jargon, exclamation marks, filler and any copy that repeats the field label.
Guardrails Do not invent prices, legal wording, data-handling claims or compliance text; ask the user instead. Flag where privacy notice wording, consent text or a local regulation must be checked by a qualified professional. State any assumption about what the system does behind the button.
Example Screen: newsletter signup modal. Primary action: add the email to a mailing list. Audience: first-time visitors. Language: English, plain.