ux-writing

name	ux-writing
description	Shapes premium product copy for interfaces, flows, prompts, and conversion surfaces with emotional clarity and clear guidance. Use when writing or revising onboarding, creation flows, templates, settings, empty states, success states, CTAs, upgrade messaging, prompts, product education, or any UI copy where tone, clarity, trust, and conversion matter.

UX Writing

Quick start

Use this skill to make product copy feel clear, calm, and premium without sounding generic, salesy, or overexplained.

This is a product wide skill. Use it anywhere copy shapes:

• comprehension
• trust
• momentum
• emotional tone
• conversion

For Emora, optimize for this emotional order when relevant:

1. Relief
2. Clarity
3. Excitement
4. Confidence

Core rules

• Write for the next decision, not for decoration.
• Reduce effort before adding emotion.
• Prefer guidance over instruction.
• Make premium feel calm, not loud.
• Do not use dashes in UI copy.
• Avoid punctuation patterns that sound AI-written or over-styled.
• Use the simplest mark that keeps the sentence clear and human.
• Do not use startup clichés, funnel-speak, or hype copy.
• Match the emotional weight of the moment category.
• Keep recipient-facing copy respectful and creator-facing copy empowering.

Flow-specific guidance

First 30 seconds

• Do not open with "Create a page".
• Lead with emotional intent.
• Ask light, high signal questions.
• Avoid big blank asks like "Describe everything".

Preferred prompt shapes:

• "What do you want to create today?"
• "Who is this for?"
• "What makes them special?"
• "What should this feel like?"

Core product surfaces

• Onboarding should reduce uncertainty before asking for effort.
• Create flows should guide with low effort, high signal prompts.
• Template surfaces should make differences legible quickly.
• Settings and upgrade UI should explain value without sounding transactional.
• AI prompts and helper text should reduce blank page anxiety.
• Empty states should create direction, not dead ends.
• Review, publish, and payment surfaces should feel premium and decisive.
• Recipient-facing copy should feel respectful and unobtrusive.

Success states

• Confirm what happened.
• Clarify what changed.
• Suggest the best next action.
• Do not repeat setup instructions the user likely already completed.

Premium and upgrade copy

• Explain the value in terms of the moment experience.
• Never sound manipulative or apologetic.
• If a feature removes branding or unlocks polish, be explicit about that.
• Honor trust boundaries. Do not promise a clean page and then reinsert product noise elsewhere.

Conversion and trust copy

• Prefer "why this helps" over feature listing.
• Reduce hesitation before asking for action.
• Make CTAs feel clear and emotionally safe.
• Use premium restraint. Confidence converts better than hype.
• Never trade away trust for short-term conversion.

Sentence style

• Keep sentences easy to follow on the first read.
• Avoid long stacked clauses when a shorter sentence would feel more human.
• Use commas, periods, and question marks naturally.
• Prefer plain sentence structure over dramatic punctuation.

Sensitive moments

• tribute: living person, honor, admiration, presence, ongoing impact
• memorial: remembrance, legacy, tenderness, reverence, restraint
• never blur those two

Rewrite checklist

Before finalizing copy, check:

• Is this easier to act on than before?
• Does it reduce thinking?
• Does it sound like Emora instead of generic SaaS?
• Is the tone right for the occasion and context?
• Would this still feel good if someone reads it quickly on mobile?

Output patterns

When rewriting UI copy, return:

1. the proposed copy
2. the job it is doing
3. any tone or UX tradeoff to note

When working on a flow, optimize the sequence across screens instead of polishing lines in isolation. When working on a surface, consider both local copy quality and its role in the larger journey.