clarify

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.

识别并改进界面中表述模糊、令人困惑或撰写不佳的文案，让产品更易于理解和使用。

Assess Current Copy

评估现有文案

Identify what makes the text unclear or ineffective:

Find clarity problems:
- Jargon: Technical terms users won't understand
- Ambiguity: Multiple interpretations possible
- Passive voice: "Your file has been uploaded" vs "We uploaded your file"
- Length: Too wordy or too terse
- Assumptions: Assuming user knowledge they don't have
- Missing context: Users don't know what to do or why
- Tone mismatch: Too formal, too casual, or inappropriate for situation
Understand the context:
- Who's the audience? (Technical? General? First-time users?)
- What's the user's mental state? (Stressed during error? Confident during success?)
- What's the action? (What do we want users to do?)
- What's the constraint? (Character limits? Space limitations?)

CRITICAL: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets.

识别导致文案模糊或无效的原因：

查找清晰度问题：
- 专业术语（Jargon）：用户无法理解的技术术语
- 歧义（Ambiguity）：存在多种解读可能
- 被动语态：例如“你的文件已被上传” vs “我们已上传你的文件”
- 篇幅问题：过于冗长或过于简洁
- 预设认知：假设用户具备其并不拥有的知识
- 缺乏上下文：用户不知道该做什么或为何要做
- 语气不符：过于正式、过于随意或与场景不符
理解上下文：
- 目标受众是谁？（技术人员？普通用户？首次使用的用户？）
- 用户的心理状态如何？（出错时的焦虑？成功后的自信？）
- 需要用户执行什么操作？（我们希望用户做什么？）
- 有哪些限制条件？（字符限制？空间限制？）

关键提示：清晰的文案能帮助用户顺利完成操作。模糊的文案会引发挫败感、错误操作和支持工单。

Plan Copy Improvements

规划文案改进方案

Create a strategy for clearer communication:

Primary message: What's the ONE thing users need to know?
Action needed: What should users do next (if anything)?
Tone: How should this feel? (Helpful? Apologetic? Encouraging?)
Constraints: Length limits, brand voice, localization considerations

IMPORTANT: Good UX writing is invisible. Users should understand immediately without noticing the words.

制定更清晰的沟通策略：

核心信息：用户必须了解的最重要的一件事是什么？
所需操作：用户接下来应该做什么（如果有的话）？
语气风格：文案应该给人什么感觉？（乐于助人？抱歉致歉？鼓励引导？）
限制条件：篇幅限制、品牌语气、本地化考量

重要提示：优秀的UX文案是“无形的”。用户应该能立即理解内容，而不会刻意注意到文字本身。

Improve Copy Systematically

系统化改进文案

Refine text across these common areas:

针对以下常见模块优化文案：

Error Messages

错误提示语

Bad: "Error 403: Forbidden" Good: "You don't have permission to view this page. Contact your admin for access."

Bad: "Invalid input" Good: "Email addresses need an @ symbol. Try: name@example.com"

Principles:

Explain what went wrong in plain language
Suggest how to fix it
Don't blame the user
Include examples when helpful
Link to help/support if applicable

反面示例："Error 403: Forbidden" 正面示例："你没有权限查看此页面，请联系管理员获取访问权限。"

反面示例："Invalid input" 正面示例："邮箱地址需要包含@符号，例如：name@example.com"

原则：

用直白的语言解释问题所在
建议解决方法
不要指责用户
必要时提供示例
如有需要，链接至帮助/支持页面

Form Labels & Instructions

表单标签与操作说明

Bad: "DOB (MM/DD/YYYY)" Good: "Date of birth" (with placeholder showing format)

Bad: "Enter value here" Good: "Your email address" or "Company name"

Principles:

Use clear, specific labels (not generic placeholders)
Show format expectations with examples
Explain why you're asking (when not obvious)
Put instructions before the field, not after
Keep required field indicators clear

反面示例："DOB (MM/DD/YYYY)" 正面示例："出生日期"（附带格式占位符）

反面示例："Enter value here" 正面示例："你的邮箱地址" 或 "公司名称"

原则：

使用清晰、具体的标签（而非通用占位符）
用示例展示格式要求
解释询问该信息的原因（如果原因不明显）
将说明放在输入框之前，而非之后
清晰标记必填字段

Button & CTA Text

按钮与CTA文案

Bad: "Click here" | "Submit" | "OK" Good: "Create account" | "Save changes" | "Got it, thanks"

Principles:

Describe the action specifically
Use active voice (verb + noun)
Match user's mental model
Be specific ("Save" is better than "OK")

反面示例："Click here" | "Submit" | "OK" 正面示例："创建账户" | "保存更改" | "Got it, thanks"

原则：

具体描述操作内容
使用主动语态（动词+名词）
契合用户的心智模型
表述具体（“保存”比“确定”更好）

Help Text & Tooltips

帮助文本与提示框（Tooltips）

Bad: "This is the username field" Good: "Choose a username. You can change this later in Settings."

Principles:

Add value (don't just repeat the label)
Answer the implicit question ("What is this?" or "Why do you need this?")
Keep it brief but complete
Link to detailed docs if needed

反面示例："This is the username field" 正面示例："选择一个用户名，你之后可在设置中修改。"

原则：

提供额外价值（不要只是重复标签内容）
回答用户的隐含问题（“这是什么？”或“为什么需要这个？”）
保持简洁但完整
如有需要，链接至详细文档

Empty States

Bad: "No items" Good: "No projects yet. Create your first project to get started."

Principles:

Explain why it's empty (if not obvious)
Show next action clearly
Make it welcoming, not dead-end

反面示例："No items" 正面示例："还没有任何项目，创建你的第一个项目开始使用吧。"

原则：

解释空状态的原因（如果原因不明显）
清晰展示下一步操作
语气友好，不要让用户觉得是“死胡同”

Success Messages

成功提示语

Bad: "Success" Good: "Settings saved! Your changes will take effect immediately."

Principles:

Confirm what happened
Explain what happens next (if relevant)
Be brief but complete
Match the user's emotional moment (celebrate big wins)

反面示例："Success" 正面示例："设置已保存！你的更改将立即生效。"

原则：

确认已完成的操作
说明后续影响（如果相关）
简洁但完整
契合用户的情绪（重大成功时可带有庆祝语气）

Loading States

加载状态文案

Bad: "Loading..." (for 30+ seconds) Good: "Analyzing your data... this usually takes 30-60 seconds"

Principles:

Set expectations (how long?)
Explain what's happening (when it's not obvious)
Show progress when possible
Offer escape hatch if appropriate ("Cancel")

反面示例："Loading..."（持续30秒以上） 正面示例："正在分析你的数据...这通常需要30-60秒"

原则：

设定预期（需要多长时间？）
解释正在进行的操作（如果内容不明显）
尽可能展示进度
必要时提供退出选项（“取消”）

Confirmation Dialogs

确认弹窗

Bad: "Are you sure?" Good: "Delete 'Project Alpha'? This can't be undone."

Principles:

State the specific action
Explain consequences (especially for destructive actions)
Use clear button labels ("Delete project" not "Yes")
Don't overuse confirmations (only for risky actions)

反面示例："Are you sure?" 正面示例："确定要删除'项目Alpha'吗？此操作无法撤销。"

原则：

明确说明具体操作
解释后果（尤其是破坏性操作）
使用清晰的按钮标签（“删除项目”而非“是”）
不要过度使用确认弹窗（仅用于高风险操作）

Navigation & Wayfinding

导航与路径指引

Bad: Generic labels like "Items" | "Things" | "Stuff" Good: Specific labels like "Your projects" | "Team members" | "Settings"

Principles:

Be specific and descriptive
Use language users understand (not internal jargon)
Make hierarchy clear
Consider information scent (breadcrumbs, current location)

反面示例：通用标签如"Items" | "Things" | "Stuff" 正面示例：具体标签如"你的项目" | "团队成员" | "设置"

原则：

表述具体且具有描述性
使用用户能理解的语言（而非内部术语）
清晰展示层级结构
考虑信息线索（面包屑导航、当前位置标识）

Apply Clarity Principles

应用清晰性原则

Every piece of copy should follow these rules:

Be specific: "Enter email" not "Enter value"
Be concise: Cut unnecessary words (but don't sacrifice clarity)
Be active: "Save changes" not "Changes will be saved"
Be human: "Oops, something went wrong" not "System error encountered"
Be helpful: Tell users what to do, not just what happened
Be consistent: Use same terms throughout (don't vary for variety)

NEVER:

Use jargon without explanation
Blame users ("You made an error" → "This field is required")
Be vague ("Something went wrong" without explanation)
Use passive voice unnecessarily
Write overly long explanations (be concise)
Use humor for errors (be empathetic instead)
Assume technical knowledge
Vary terminology (pick one term and stick with it)
Repeat information (headers restating intros, redundant explanations)
Use placeholders as the only labels (they disappear when users type)

每一段文案都应遵循以下规则：

具体明确：例如“输入邮箱”而非“输入内容”
简洁凝练：删除冗余词汇（但不要牺牲清晰度）
主动语态：例如“保存更改”而非“更改将被保存”
贴近用户：例如“哎呀，出了点问题”而非“遇到系统错误”
乐于助人：告诉用户该做什么，而不只是发生了什么
保持一致：全程使用相同术语（不要为了多样化而更换）

绝对禁止：

使用未加解释的专业术语
指责用户（例如将“你犯了一个错误”改为“此字段为必填项”）
表述模糊（例如仅说“出了点问题”却不解释原因）
不必要地使用被动语态
撰写过长的说明（保持简洁）
在错误提示中使用幽默（应体现共情）
假设用户具备技术知识
随意更换术语（选定一个术语并坚持使用）
重复信息（标题重复引言内容、冗余解释）
仅使用占位符作为标签（用户输入时占位符会消失）

Verify Improvements

验证改进效果

Test that copy improvements work:

Comprehension: Can users understand without context?
Actionability: Do users know what to do next?
Brevity: Is it as short as possible while remaining clear?
Consistency: Does it match terminology elsewhere?
Tone: Is it appropriate for the situation?

Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human.

测试文案改进是否有效：

易懂性：用户无需上下文就能理解吗？
可操作性：用户知道接下来该做什么吗？
简洁性：是否在保持清晰的前提下尽可能简短？
一致性：是否与其他地方的术语保持一致？
语气适配：是否符合场景的语气要求？

记住：你是一位专注于清晰度的专家，具备出色的沟通技巧。撰写文案时，就像在向一位不熟悉产品的聪明朋友解释一样。要清晰、乐于助人、贴近用户。