business-ux-copy

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a con

SKILL.md

GitHub

App 执行约定

先读取本技能正文及任务所需的本地参考资源。使用中文;工作目录由任务提供,仅读取用户提供、当前任务授权的资料。正文中的 $ARGUMENTS 及斜杠命令表示用户任务输入,不调用 Claude 专用命令。AskUserQuestion/提问通过 App ask_user;本地文件通过 read_file,成果使用 write_file 后 register_artifact,或 write_artifact。相对资源路径以本 SKILL.md 所在目录为起点。若技能读取结果含目录,按该目录构建资源绝对路径。

正文中 Search/WebFetch、Figma、CRM、广告平台及其它连接名称仅为可选来源;只使用 App 实际提供且已授权的工具。没有连接时从上传材料完成流程,把缺少的外部验证列出,不安装运行时插件或扫描用户全局配置。默认输出 Markdown/CSV 草稿;Office、图表、HTML、PNG 或图像生成只在对应工具和运行库可用时执行。不得擅自发送邮件、发表内容、签约、创建发票、修改线上商品或花费广告预算。

/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.

Usage

/ux-copy $ARGUMENTS

What 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

  1. Clear: Say exactly what you mean. No jargon, no ambiguity.
  2. Concise: Use the fewest words that convey the full meaning.
  3. Consistent: Same terms for the same things everywhere.
  4. Useful: Every word should help the user accomplish their goal.
  5. Human: Write like a helpful person, not a robot.

Copy Patterns

CTAs

  • 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"

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

## UX Copy: [Context]

### 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] |

### Rationale
[Why this copy works — user context, clarity, action-orientation]

### Localization Notes
[Anything translators should know — idioms to avoid, character expansion, cultural context]

If 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

Tips

  1. Be specific about context — "Error message when payment fails" is better than "error message."
  2. Share your brand voice — "We're professional but warm" helps me match your tone.
  3. Consider the user's emotional state — Error messages need empathy. Success messages can celebrate.