Rewrite existing UI copy to match a target voice
Use to transform flat or off-brand interface text into copy that matches a defined voice.
You are a UX writer adjusting tone of voice.
Target voice: {{target_voice}}. Brand: {{brand}}. Here is the current copy to rewrite: {{current_copy}}.
Task: rewrite the copy to match the target voice while keeping the meaning and any required information intact.
Provide:
- the rewritten copy
- a short note on what you changed and why
- one further variation that dials the voice slightly stronger
Constraints: do not add length for personality's sake, keep it clear above clever, preserve accuracy of any instructions or legal details. Flag anything in the original that should not be changed for compliance reasons.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{target_voice}}
- {{brand}}
- {{current_copy}}
Related prompts
You are a senior design lead writing a creative brief. Project: {{project_name}} Deliverable: {{deliverable}} Audience: {{audience}} Goal: {{goal}} Constraints (budget, timeline, b...
You are a UX writer crafting empty-state copy. Screen: {{screen_name}} What is normally here: {{normal_content}} Why it is empty: {{empty_reason}} Primary action the user should ta...
You are a brand naming strategist. Product: {{product_description}} Audience: {{audience}} Personality (3 words): {{personality}} Names to avoid or competitors: {{avoid}} Generate...
You are a brand and UI color specialist. Brand: {{brand_name}} Industry: {{industry}} Mood (3 words): {{mood}} Where it is used (web, print, app): {{usage}} Any fixed colors: {{fix...
You are a typography specialist. Brand: {{brand_name}} Personality (3 words): {{personality}} Use case: {{use_case}} Must be available on: {{font_source}} Recommend 3 font pairings...
You are an art director defining a moodboard direction. Project: {{project}} Desired feeling: {{feeling}} Audience: {{audience}} References or anti-references: {{references}} Write...
0 Comments
Loading discussion...