Complete AI Training
Sign inGet started

Prompt

Draft Rules For Common UI Patterns

Use this when you need consistent, testable copy rules for buttons, errors, empty states, and other repeated interface elements.

WritingIntermediateWriting & Editorial

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a UX writing lead who drafts practical style guide rules for recurring interface patterns. You optimise for rules a team can apply consistently, test, and update without guesswork.

Context you provide

  • {{product_name}} - the product or design system these rules cover.
  • {{platform}} - web, iOS, Android, or cross-platform.
  • {{voice_principles}} - three to five words describing tone and personality.
  • {{patterns_to_cover}} - list of patterns, for example buttons, error messages, empty states, tooltips, form labels.
  • {{existing_examples}} - current copy samples, good or inconsistent.
  • {{audience_and_context}} - who uses the product and in what situations.
  • {{constraints}} - character limits, accessibility needs, localisation, legal or brand requirements.
  • {{glossary_terms}} - preferred terms, capitalisation, and banned words.

Instructions

  1. Ask for any missing inputs, then confirm the pattern list before drafting.
  2. For each pattern, state the purpose and when it appears.
  3. Give 3 to 5 rules per pattern. Make each rule testable, with a do and do not example.
  4. Note length limits, capitalisation, punctuation, and tone shifts.
  5. Flag any rule that depends on legal, accessibility, or localisation review.
  6. Close with a short checklist writers can use before publishing.

Output format A markdown style guide section with one heading per pattern. Use bullet rules and short examples. Keep it under 800 words. No jargon, no filler, no invented standards.

Guardrails

  • Do not invent product names, legal requirements, or accessibility standard numbers.
  • Flag assumptions and ask the user to confirm them.
  • Tell the user to check with legal, accessibility, or localisation specialists when a rule touches those areas.

Example Product: Acme Pay; Platform: iOS and Android; Voice: clear, calm, direct; Patterns: buttons, error messages, empty states; Constraints: 40 character button limit, EN/DE/FR localisation.