righter

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Righter

A UX writing skill. Review existing UI copy against a defined set of principles, or write new copy from scratch applying those principles from the start.

Reference files — read these when relevant:

```
references/components.md
```
— per-component writing rules (Alert Dialog, Toast, Inline Alert, Helper Text, Alert Banner, Tooltip)
```
references/weakeners.md
```
— full word lists for all weakener categories
```
references/phonaesthetics.md
```
— full sound concepts and cluster table for word choice

一款UX写作技能工具，可对照既定原则集审核现有UI文案，或从零开始应用这些原则撰写全新文案。

参考文件——相关场景下请先阅读：

```
references/components.md
```
— 各组件写作规则（Alert Dialog、Toast、Inline Alert、Helper Text、Alert Banner、Tooltip）
```
references/weakeners.md
```
— 所有弱化表达分类的完整词表
```
references/phonaesthetics.md
```
— 选词用的完整语音概念和音簇表

Two Modes

两种模式

Mode 1: Review Existing Copy

模式1：审核现有文案

For each piece of content:

Check against the review checklist below
Identify every violation
Rewrite it
Output in the review format below

针对每一段内容：

对照下方审核清单检查
识别所有不符合原则的问题
重写文案
按照下方审核格式输出结果

Mode 2: Write New Copy

模式2：撰写新文案

Apply all relevant principles
For labels, CTAs, and microcopy: read
```
references/phonaesthetics.md
```
and apply sound guidance
Output in the new copy format below

应用所有相关原则
针对标签、CTA和微文案：阅读
```
references/phonaesthetics.md
```
并应用语音指导规则
按照下方新文案格式输出结果

Output Formats

输出格式

Review format

审核格式

Use this block for every piece of copy reviewed:

Before: [original copy] After: [rewritten copy]

Principles applied:

[Principle name]: [one sentence on why this improved the copy]

Weakeners removed:

"[word or phrase]" → removed because [category, e.g. hedging / filler adverb / weak verb]. If none found, write "None found."

Phonaesthetics:

Note any sound improvements made (rhythm, stress pattern, sound cluster choices, ease of mouth). If phonaesthetics wasn't a factor (e.g. error messages), write "Not applicable for this copy type."

Reading metrics (Before → After):

Word count: X → Y
ARI score: X.X → Y.Y
Grade level: Grade X (age X–X) → Grade X (age X–X)
Target: ARI ≤ 6 (Grade 5, age 10–11)

每一段审核的文案都使用该模块输出：

修改前： [原始文案] 修改后： [重写后的文案]

应用的原则：

[原则名称]：[一句话说明该原则对文案的优化点]

移除的弱化表达：

"[单词或短语]" → 移除原因是[分类，例如模糊表述/填充副词/弱动词]。如果没有找到则填写"未找到。"

语音美学：

说明所有语音层面的优化（节奏、重音模式、音簇选择、发音流畅度）。如果语音美学不适用该类文案（例如错误信息），则填写"该文案类型不适用。"

阅读指标（修改前 → 修改后）：

单词数：X → Y
ARI分数：X.X → Y.Y
年级水平：X年级（X–X岁） → X年级（X–X岁）
目标：ARI ≤ 6（5年级，10–11岁）

New copy format

新文案格式

Copy: [final copy]

Principles applied:

[Principle name]: [one sentence on why]

Weakeners avoided:

Note any weakener patterns consciously avoided, or write "None present."

Phonaesthetics:

Explain the sound choices made — rhythm, stress, clusters, ease of mouth. If not applicable, say so.

Reading metrics:

Word count: X
ARI score: X.X
Grade level: Grade X (age X–X)
Target: ARI ≤ 6 (Grade 5, age 10–11)

文案： [最终文案]

应用的原则：

[原则名称]：[一句话说明应用原因]

避免的弱化表达：

说明所有刻意规避的弱化表达模式，没有则填写"无。"

语音美学：

解释做出的语音选择：节奏、重音、音簇、发音流畅度。不适用则说明。

阅读指标：

单词数：X
ARI分数：X.X
年级水平：X年级（X–X岁）
目标：ARI ≤ 6（5年级，10–11岁）

UX Writing Principles

UX写作原则

Apply all of these when reviewing or writing.

审核或写作时需应用所有以下原则：

1. Use active voice

1. 使用主动语态

Subject → verb → object. Active voice is shorter and easier to follow.

✗ "Rewards can be earned by clicking here."
✓ "Click here to start earning rewards."

主语 → 动词 → 宾语结构。主动语态更简短，更容易理解。

✗ "Rewards can be earned by clicking here."
✓ "Click here to start earning rewards."

2. Write at or below a fifth grade reading level

2. 写作难度不超过5年级阅读水平

Short sentences. Simple words. Clear structure. Target ARI ≤ 6.

✗ "If you have forgotten your password, please click on the 'Forgot Password' link and submit your registered email address."
✓ "Click 'Forgot Password'. Enter your email. Check your inbox for a reset link."

短句、简单词汇、清晰结构。目标ARI ≤ 6。

✗ "If you have forgotten your password, please click on the 'Forgot Password' link and submit your registered email address."
✓ "Click 'Forgot Password'. Enter your email. Check your inbox for a reset link."

3. Avoid jargon

3. 避免行业黑话

Replace technical terms with plain language. Don't assume domain knowledge.

✗ "Authenticate your credentials."
✓ "Log in with your username and password."

用通俗语言替换技术术语，不要假设用户具备领域知识。

✗ "Authenticate your credentials."
✓ "Log in with your username and password."

4. Avoid complex sentence structures

4. 避免复杂句式

One idea per sentence. Avoid dependent clauses stacked on independent clauses.

✗ "The fox, which was red, over the gate jumped."
✓ "The red fox jumped over the gate."

每句话只表达一个想法，不要在独立从句上叠加多个从属从句。

✗ "The fox, which was red, over the gate jumped."
✓ "The red fox jumped over the gate."

5. Avoid double negatives

5. 避免双重否定

Double negatives increase misreads and cognitive load.

✗ "Please don't fail to save your changes."
✓ "Please save your changes."

双重否定会提升误读概率和认知负担。

✗ "Please don't fail to save your changes."
✓ "Please save your changes."

6. Use contractions

6. 使用缩略形式

Contractions sound human. Formal constructions feel stiff.

✗ "Do not submit the form until all fields are complete."
✓ "Don't submit until all fields are complete."

缩略形式更有亲和力，正式表达会显得生硬。

✗ "Do not submit the form until all fields are complete."
✓ "Don't submit until all fields are complete."

7. Write in present tense

7. 使用现在时态

Describe what's happening now or what the user can do.

✗ "Your file was uploaded."
✓ "Your file is uploading."

描述当前正在发生的事，或者用户可以执行的操作。

✗ "Your file was uploaded."
✓ "Your file is uploading."

8. Frame around the user's goals, not the system

8. 围绕用户目标而非系统逻辑表述

Users care about what they're doing, not how the system works.

✗ "Due to an HTTPS network security issue, some features are not available."
✓ "This site may be insecure. Some features aren't available."

用户关心的是自己要做什么，而非系统的运行原理。

✗ "Due to an HTTPS network security issue, some features are not available."
✓ "This site may be insecure. Some features aren't available."

9. Avoid describing the interface

9. 避免描述界面元素

Don't reference UI elements like "tab," "panel," "menu," "page," or "section."

✗ "Go to the Settings panel."
✓ "Go to Settings."

不要提及"标签页"、"面板"、"菜单"、"页面"、"区块"等UI元素。

✗ "Go to the Settings panel."
✓ "Go to Settings."

10. Use consistent terminology

10. 使用统一术语

Pick one word for each concept and stick to it.

✗ Using "Sign Up," "Register," and "Create Account" interchangeably
✓ Always "Sign up"

每个概念固定使用一个表述，保持一致性。

✗ 混用"Sign Up"、"Register"和"Create Account"
✓ 统一使用"Sign up"

11. Apply progressive disclosure

11. 应用渐进式披露

Lead with what the user needs now. Offer detail only when needed.

✗ "Your password must be at least 8 characters, contain a number, a symbol, and a capital letter."
✓ "Your password must be at least 8 characters." [+ optional detail link]

优先展示用户当前需要的信息，仅在必要时提供细节。

✗ "Your password must be at least 8 characters, contain a number, a symbol, and a capital letter."
✓ "Your password must be at least 8 characters." [+ 可选的详情链接]

12. Don't apologize unnecessarily

12. 不要无意义道歉

Reserve "sorry" for serious errors. Hollow apologies undermine trust.

✗ "Whoops! We can't upload your picture. Try again."
✓ "We couldn't upload your picture. Try again."

仅在出现严重错误时使用"抱歉"，空洞的道歉会损害信任。

✗ "Whoops! We can't upload your picture. Try again."
✓ "We couldn't upload your picture. Try again."

13. Limit exclamation marks

13. 限制感叹号使用

Use words to convey energy, not punctuation. One per screen max, only for genuine celebration.

✓ "Your profile has been updated!" (success state)
✗ "Error! You can't submit the form! Please fix the errors!"

用文字传递情绪而非标点，每个页面最多1个感叹号，仅用于真实的成功庆祝场景。

✓ "Your profile has been updated!" (成功状态)
✗ "Error! You can't submit the form! Please fix the errors!"

14. Check prepositions

14. 检查介词使用

Prepositions sit between two nouns. Never start or end a sentence with one.

✗ "Click on the Submit button."
✓ "Click Submit."

介词应放在两个名词之间，不要在句首或句尾使用介词。

✗ "Click on the Submit button."
✓ "Click Submit."

15. Eliminate weakeners

15. 移除弱化表达

Remove all hedging words, softeners, empty intensifiers, filler adverbs, throat-clearing, passive-aggressive politeness, vague quantifiers, redundant framing, weak verb phrases, and meta-commentary.

Read
references/weakeners.md
for the full word lists and examples.

Key patterns to catch immediately:

Hedging: maybe, probably, might be, appears to, seems like
Filler: actually, basically, literally, just, simply
Weak verbs: "make a decision" → decide, "conduct an analysis" → analyze
Throat-clearing: "I think," "we believe," "it is important to note that"

删除所有模糊表述、软化词、无意义的强化词、填充副词、铺垫性表述、被动攻击性的礼貌用语、模糊量词、冗余表述、弱动词短语和元评论。

阅读
references/weakeners.md
查看完整词表和示例。

需要立即识别的核心模式：

模糊表述：maybe, probably, might be, appears to, seems like
填充词：actually, basically, literally, just, simply
弱动词："make a decision" → decide, "conduct an analysis" → analyze
铺垫性表述："I think," "we believe," "it is important to note that"

Error Message Guidelines

错误信息指南

Apply these on top of the general principles when reviewing or writing error messages.

审核或撰写错误信息时，在通用原则基础上额外应用以下规则：

Structure

结构

Every error must answer:

What happened? (required)
Why? (only if it genuinely helps)
What should they do next? (required)

每个错误信息必须回答：

发生了什么？（必填）
为什么发生？（仅当确实有帮助时提供）
用户接下来应该做什么？（必填）

Voice and tone

语气和风格

Instructive — describe the issue precisely, optimize for understanding
Reassuring — no disparaging tone, no unnecessary humor
Supportive — always provide a clear next step

指导性 — 精准描述问题，优先保证可理解性
安抚性 — 没有贬低性语气，不使用不必要的幽默
支持性 — 始终提供清晰的下一步操作指引

Mechanics

格式规则

Sentence case: "This field is required." not "This Field Is Required."
No ALL CAPS (except real acronyms)
1–2 sentences max

句首大写："This field is required." 而非 "This Field Is Required."
不要全大写（真实的缩写除外）
最多1-2句话

Don't blame the user

不要指责用户

Describe the situation, not the mistake.

✗ "You didn't enter enough characters."
✓ "This field needs 8 characters."

描述客观情况，而非错误本身。

✗ "You didn't enter enough characters."
✓ "This field needs 8 characters."

Form field vs system errors

表单字段错误 vs 系统错误

Form field — what's wrong and how to fix it: "Enter a valid email address."
System error — what happened and what to try next: "We couldn't connect. Check your internet or try again."

表单字段错误 — 说明问题和修复方式："Enter a valid email address."
系统错误 — 说明发生的问题和后续尝试方向："We couldn't connect. Check your internet or try again."

Other rules

其他规则

Preserve user input where possible — let users edit rather than start over
Place errors adjacent to the element that triggered them (Law of Proximity)

尽可能保留用户输入 — 让用户可以编辑而非重新填写
把错误放在触发错误的元素旁边（接近性法则）

Component decision tree

组件决策树

Use this before writing any error message to pick the right component. Then read

references/components.md

for full writing rules for that component.

Does it block progress and require immediate action?
  └─ Yes → Alert Dialog

Is it a system-level issue (outage, permissions, account)?
  └─ Yes → Alert Banner

Is it confirming something that just happened?
  └─ Yes → Toast

Is it attached to a specific form field?
  └─ Yes → Helper Text

Is it contextual to a page section, non-blocking?
  └─ Yes → Inline Alert

Is it a hover label for an icon or interactive element?
  └─ Yes → Tooltip

撰写任何错误信息前使用该决策树选择合适的组件，之后阅读

references/components.md

查看该组件的完整写作规则。

Does it block progress and require immediate action?
  └─ Yes → Alert Dialog

Is it a system-level issue (outage, permissions, account)?
  └─ Yes → Alert Banner

Is it confirming something that just happened?
  └─ Yes → Toast

Is it attached to a specific form field?
  └─ Yes → Helper Text

Is it contextual to a page section, non-blocking?
  └─ Yes → Inline Alert

Is it a hover label for an icon or interactive element?
  └─ Yes → Tooltip

Phonaesthetics

语音美学

When writing new copy — especially labels, CTAs, empty states, and microcopy — consider sound alongside meaning. Copy that sounds good is easier to remember and more pleasant to use.

Read
references/phonaesthetics.md
for the full concept guide and sound cluster table.

Core rules to apply immediately:

Prefer consonant-vowel alternation (CVCV) for labels — natural rhythm, easy to say
Two-beat phrases are catchy; three-beat phrases are melodic; irregular stress is awkward
Liquids and nasals (l, m, n, r, w, y) → calm, gentle contexts
Plosives (p, b, t, d, k, g) → energetic, action-oriented CTAs
Avoid tongue twisters — if it's hard to say, it's hard to remember

Sound clusters to reach for:

```
gl-
```
→ clarity, light (insight, vision, illumination features)
```
fl-
```
→ flow, ease (smooth UX, motion)
```
sp-
```
→ speed, energy (action, innovation)
```
cl-
```
→ precision, closure (tools, interactions)

撰写新文案时——尤其是标签、CTA、空状态和微文案——除了语义之外还要考虑语音效果。听起来舒适的文案更容易记忆，使用体验也更好。

阅读
references/phonaesthetics.md
查看完整的概念指南和音簇表。

可立即应用的核心规则：

标签优先使用辅音-元音交替结构（CVCV）——节奏自然，容易发音
两拍短语容易记忆；三拍短语更有韵律；不规则重音会很生硬
流音和鼻音（l, m, n, r, w, y）→ 适合平静、温和的场景
爆破音（p, b, t, d, k, g）→ 适合有活力、行动导向的CTA
避免绕口令——如果很难念出来，就很难记住

推荐使用的音簇：

```
gl-
```
→ 清晰、轻盈（洞察、视觉、照明类功能）
```
fl-
```
→ 流畅、轻松（顺滑UX、动效相关）
```
sp-
```
→ 速度、活力（行动、创新相关）
```
cl-
```
→ 精准、闭环（工具、交互相关）

Reading Metrics

阅读指标

Calculate and show these for all reviewed and written copy.

所有审核和撰写的文案都需要计算并展示以下指标。

ARI Formula

ARI计算公式

ARI = 4.71 × (characters ÷ words) + 0.5 × (words ÷ sentences) − 21.43

Characters = letters and numbers only (no spaces or punctuation)
Words = space-separated tokens
Sentences = units ending in
```
.
```
```
?
```
or
```
!
```

Round to one decimal place. Always include grade and age range.

ARI = 4.71 × (characters ÷ words) + 0.5 × (words ÷ sentences) − 21.43

字符数 = 仅统计字母和数字（不含空格和标点）
单词数 = 空格分隔的标记数
句子数 = 以
```
.
```
```
?
```
或
```
!
```
结尾的单元数

结果四舍五入保留1位小数，始终同时展示年级和年龄范围。

Grade Level Table

年级水平对照表

ARI	Grade	Age
1	Kindergarten	5–6
2	Grade 1	6–7
3	Grade 2	7–8
4	Grade 3	8–9
5	Grade 4	9–10
6	Grade 5	10–11
7	Grade 6	11–12
8	Grade 7	12–13
9	Grade 8	13–14
10	Grade 9	14–15
11	Grade 10	15–16
12	Grade 11	16–17
13	Grade 12	17–18
14+	Professional	18+

Target: ARI ≤ 6 (Grade 5, age 10–11)

ARI	年级	年龄
1	幼儿园	5–6
2	1年级	6–7
3	2年级	7–8
4	3年级	8–9
5	4年级	9–10
6	5年级	10–11
7	6年级	11–12
8	7年级	12–13
9	8年级	13–14
10	9年级	14–15
11	10年级	15–16
12	11年级	16–17
13	12年级	17–18
14+	专业水平	18+

目标：ARI ≤ 6（5年级，10–11岁）

Review Checklist

审核清单

Run through this for every piece of copy before finalizing.

Voice and structure

Passive voice present?
Complex sentence structure?
Double negatives?
Past or future tense where present tense works?
Missing contractions (do not → don't)?

Clarity

Jargon or technical terms?
Reading level above Grade 5?
Interface elements named (tab, panel, section)?
System-framing instead of user-goal framing?
Too much information up front (no progressive disclosure)?

Tone

Unnecessary apology?
Overuse of exclamation marks?
Any weakener words? (see
```
references/weakeners.md
```
)

Mechanics

Inconsistent terminology?
Preposition starting or ending a sentence?

Errors (if applicable)

Clear next step provided?
Does it blame the user?
Right component chosen? (use decision tree above)

最终定稿前针对每一段文案检查以下内容：

语气和结构

是否存在被动语态？
是否有复杂句式？
是否有双重否定？
可以用现在时态的场景是否用了过去或将来时态？
应该用缩略形式的地方没有用（例如do not → don't）？

清晰度

是否有黑话或技术术语？
阅读难度是否超过5年级？
是否提及了界面元素（标签页、面板、区块）？
是否围绕系统逻辑而非用户目标表述？
是否前置了过多信息（没有使用渐进式披露）？

语气

是否有无意义的道歉？
是否过度使用感叹号？
是否有弱化表达词？（参考
```
references/weakeners.md
```
）

格式规则

术语使用是否不一致？
句首或句尾是否有介词？

错误信息（如适用）

是否提供了清晰的下一步操作？
是否指责了用户？
是否选择了正确的组件？（参考上方决策树）