ux-copy
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese/ux-copy
/ux-copy
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Write or review UX copy for any interface context.
如果遇到不熟悉的占位符或需要查看已连接的工具，请参阅CONNECTORS.md。
为任意界面场景撰写或审核UX文案。
Usage
使用方法
/ux-copy $ARGUMENTS/ux-copy $ARGUMENTSWhat I Need From You
我需要你提供的信息
- Context: What screen, flow, or feature?
- User state: What is the user trying to do? How are they feeling?
- Tone: Formal, friendly, playful, reassuring?
- Constraints: Character limits, platform guidelines?
- 场景背景：对应的是哪个页面、流程或功能？
- 用户状态：用户试图完成什么操作？他们的情绪状态如何？
- 语气风格：正式、友好、活泼、安心？
- 限制条件：字符限制、平台规范？
Principles
核心原则
- Clear: Say exactly what you mean. No jargon, no ambiguity.
- Concise: Use the fewest words that convey the full meaning.
- Consistent: Same terms for the same things everywhere.
- Useful: Every word should help the user accomplish their goal.
- Human: Write like a helpful person, not a robot.
- 清晰明确：准确表达含义，避免行话和歧义。
- 简洁凝练：用最少的词汇传递完整信息。
- 保持一致：同一事物在各处使用统一术语。
- 实用有效：每一个词汇都要帮助用户达成目标。
- 贴近人性：像乐于助人的人一样写作，而非机器人。
Copy Patterns
文案模板
CTAs
CTA文案
- Start with a verb: "Start free trial", "Save changes", "Download report"
- Be specific: "Create account" not "Submit"
- Match the outcome to the label
- 以动词开头：比如“开始免费试用”、“保存更改”、“下载报告”
- 表述具体：用“创建账户”而非“提交”
- 标签与操作结果匹配
Error Messages
错误提示文案
Structure: What happened + Why + How to fix
- "Payment declined. Your card was declined by your bank. Try a different card or contact your bank."
结构：发生了什么 + 原因 + 解决方法
- 示例：“支付失败。您的银行卡被银行拒绝，请尝试更换银行卡或联系您的银行。”
Empty States
空状态文案
Structure: What this is + Why it's empty + How to start
- "No projects yet. Create your first project to start collaborating with your team."
结构：功能说明 + 空状态原因 + 启动指引
- 示例：“暂无项目。创建您的第一个项目，即可开始与团队协作。”
Confirmation Dialogs
确认对话框文案
- Make the action clear: "Delete 3 files?" not "Are you sure?"
- Describe consequences: "This can't be undone"
- Label buttons with the action: "Delete files" / "Keep files" not "OK" / "Cancel"
- 明确操作内容：比如“删除3个文件？”而非“您确定吗？”
- 说明后果：“此操作无法撤销”
- 按钮标签对应操作：用“删除文件”/“保留文件”而非“确定”/“取消”
Tooltips
提示工具文案
- Concise, helpful, never obvious
- 简洁实用，避免赘述显而易见的内容
Loading States
加载状态文案
- Set expectations, reduce anxiety
- 明确预期，缓解用户焦虑
Onboarding
引导流程文案
- Progressive disclosure, one concept at a time
- 逐步展示信息，一次传递一个概念
Voice and Tone
语气风格适配
Adapt tone to context:
- Success: Celebratory but not over the top
- Error: Empathetic and helpful
- Warning: Clear and actionable
- Neutral: Informative and concise
根据场景调整语气：
- 成功场景：带有庆祝感但不过分张扬
- 错误场景：共情且提供帮助
- 警告场景：清晰且具备可操作性
- 中性场景：信息详实且简洁
Output
输出格式
markdown
undefinedmarkdown
undefinedUX Copy: [Context]
UX文案：[场景背景]
Recommended Copy
推荐文案
[Element]: [Copy]
[界面元素]：[文案内容]
Alternatives
备选方案
| Option | Copy | Tone | Best For |
|---|---|---|---|
| A | [Copy] | [Tone] | [When to use] |
| B | [Copy] | [Tone] | [When to use] |
| C | [Copy] | [Tone] | [When to use] |
| 选项 | 文案 | 语气 | 适用场景 |
|---|---|---|---|
| A | [文案内容] | [语气] | [适用场景] |
| B | [文案内容] | [语气] | [适用场景] |
| C | [文案内容] | [语气] | [适用场景] |
Rationale
设计理由
[Why this copy works — user context, clarity, action-orientation]
[该文案的优势——结合用户场景、清晰性、行动导向]
Localization Notes
本地化注意事项
[Anything translators should know — idioms to avoid, character expansion, cultural context]
undefined[译者需要了解的内容——需避免的习语、字符扩展问题、文化背景]
undefinedIf Connectors Available
若已连接工具
If ~~knowledge base is connected:
- Pull your brand voice guidelines and content style guide
- Check for existing copy patterns and terminology standards
If ~~design tool is connected:
- View the screen context in Figma to understand the full user flow
- Check character limits and layout constraints from the design
如果已连接~~知识库：
- 调取您的品牌语气指南和内容风格规范
- 检查现有文案模板和术语标准
如果已连接~~设计工具：
- 在Figma中查看界面场景，理解完整用户流程
- 从设计文件中查看字符限制和布局约束
Tips
小贴士
- Be specific about context — "Error message when payment fails" is better than "error message."
- Share your brand voice — "We're professional but warm" helps me match your tone.
- Consider the user's emotional state — Error messages need empathy. Success messages can celebrate.
- 明确场景背景——“支付失败时的错误提示”比“错误提示”更具体。
- 告知品牌语气——比如“我们的风格是专业但亲切”，有助于我匹配您的需求。
- 考虑用户情绪状态——错误提示需要共情，成功提示可以带有庆祝感。