Back to Details

writing-for-interfaces

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Writing for Interfaces

界面文案写作

Good interface writing is invisible. When words work seamlessly with design, people don't notice them.
Writing should be part of the design process from the start, not something filled in at the end. When words are considered alongside layout, interaction, and visual design, the result feels seamless. When they're an afterthought, product experiences feel stitched together.
Every piece of text in an interface is a small act of communication: it should respect the person's time, meet them where they are, and help them move forward.
优秀的界面文案是“隐形”的。当文字与设计无缝配合时，用户不会刻意留意它们。
文案写作应从设计流程的一开始就介入，而不是在最后阶段才填充内容。当文字与布局、交互和视觉设计同步考量时，最终的产品体验会浑然一体。如果文案是事后补加的，产品体验会显得零散割裂。
界面中的每一段文字都是一次小型沟通：它应当尊重用户的时间，贴合用户的当前场景，并帮助他们推进操作。

When triggered

触发场景

Step 1: Establish voice and personality

步骤1：确立Voice与个性

Voice is the foundation. All copy decisions — what to say, how to say it, what to leave out — flow from a clear understanding of who this product is, who it's for, and how it should sound. Without a defined voice, copy becomes inconsistent and the product loses coherency.
Search for an existing voice definition. Check for any of the following:
  • A 
    CLAUDE.md
    , 
    AGENTS.md
    , or similar project configuration file that defines voice and/or tone
  • A style guide, design system documentation, or brand guidelines
  • A word list or terminology reference
If a voice definition exists, use it as the lens for all copy work. Confirm it still feels consistent with the copy you're being asked to work on. If it doesn't, flag the drift.
If no voice definition exists, evaluate the existing copy to infer the current voice. Look for patterns: is the language formal or casual? Technical or plain? Warm or matter-of-fact? If the existing copy is inconsistent or there isn't enough to infer from, help the user establish a voice before writing anything.
Voice是基础。所有文案决策——说什么、怎么说、省略什么——都源于对产品定位、目标用户以及应有的语气风格的清晰认知。没有明确的Voice，文案会变得不一致，产品也会失去连贯性。
查找现有的Voice定义。检查以下文件是否存在：
  • 定义了Voice和/或语气的
    CLAUDE.md
    、
    AGENTS.md
    或类似项目配置文件
  • 风格指南、设计系统文档或品牌准则
  • 词汇表或术语参考手册
如果存在Voice定义，将其作为所有文案工作的准则。确认它与当前需要处理的文案仍保持一致。若不一致，需指出这种偏差。
如果没有Voice定义，通过分析现有文案推断当前的Voice。寻找模式：语言是正式还是随意？专业还是平实？热情还是实事求是？如果现有文案不一致或不足以推断，应先帮助用户确立Voice，再进行文案写作。

Establishing voice through conversation

通过对话确立Voice

Walk the user through these questions. The answers shape everything that follows.
  1. What does the product do and who is it for? A banking app for professionals and a savings app for kids serve similar purposes but should sound completely different. The audience determines vocabulary, complexity, and register.
  2. Why do people use it, and where? Someone using a health app during a crisis needs calm clarity. Someone browsing a game at home can handle playfulness. The context of use — physical environment, emotional state, competing attention — shapes how much text people can absorb and what tone they need and which voice is appropriate.
  3. Imagine the product as a person. What personality traits make them unique? Encourage the user to brainstorm freely — smart, playful, calm, authoritative, warm, no-nonsense — then group similar words into themes. Discard traits that are table stakes ("not confusing") and keep the ones that genuinely differentiate the product's personality. Aim for 3–4 key qualities that define the voice.
  4. Look for productive tensions. The best voice definitions have qualities that push against each other in useful ways. "Friendly" and "concise" create a tension that helps modulate tone — if you add a word for friendliness, you sacrifice some brevity, and vice versa. These tensions become the dials you turn when adjusting tone for different situations.
  5. Capture it. Suggest the user write the voice definition somewhere durable — a 
    CLAUDE.md
    , a design doc, a style guide — so it persists across sessions and contributors. A word list pairs well with this and helps prevent terminology drift.
引导用户回答以下问题，答案将决定后续的所有工作。
  1. 这款产品的功能是什么，目标用户是谁？ 面向专业人士的银行应用和面向儿童的储蓄应用功能类似，但语气风格应截然不同。受众决定了词汇、复杂度和语体。
  2. 人们为什么使用它，在什么场景下使用？ 在危机中使用健康应用的用户需要冷静清晰的表述；在家浏览游戏的用户则能接受活泼的语气。使用场景——物理环境、情绪状态、注意力分散情况——会影响用户能吸收的文本量，以及他们需要的语气和合适的Voice。
  3. 把产品想象成一个人，哪些个性特质让它独一无二？ 鼓励用户自由头脑风暴——聪明、活泼、冷静、权威、热情、务实——然后将相似词汇归类为主题。剔除那些必备的基础特质（如“不令人困惑”），保留真正能体现产品差异化的特质。目标是提炼出3-4个定义Voice的核心特质。
  4. 寻找有效的张力平衡。最佳的Voice定义包含相互制衡的特质。“友好”与“简洁”形成的张力有助于调节语气——如果为了增加友好性而添加词汇，就会牺牲一定的简洁性，反之亦然。这些张力就像旋钮，可根据不同场景进行调节。
  5. 记录下来。建议用户将Voice定义记录在持久化的地方——比如
    CLAUDE.md
    、设计文档或风格指南——以便在不同会话和不同贡献者之间保持一致。搭配一份词汇表使用，有助于防止术语偏差。

Step 2: Evaluate the request

步骤2：评估需求

With the voice established, identify what kind of copy work is needed:
  • New copy: Writing from scratch for a screen, flow, or component.
  • Review: Evaluating existing copy for clarity, consistency, and tone.
  • Rewrite: Improving specific text that isn't working.
  • Terminology: Building or maintaining a word list.
Then identify which interface patterns are involved and consult 
references/patterns.md
for the relevant sections.
在确立Voice之后，明确需要完成的文案工作类型：
  • 新文案撰写：为页面、流程或组件从零开始撰写文案。
  • 审核：评估现有文案的清晰度、一致性和语气。
  • 改写优化：改进效果不佳的特定文本。
  • 术语管理：创建或维护词汇表。
然后确定涉及的界面模式，并查阅
references/patterns.md
中的相关章节。

Step 3: Apply voice, then principles

步骤3：先应用Voice，再遵循原则

For every piece of copy, work in this order:
  1. Does it sound like the voice? Read it against the 3–4 qualities. If you read it aloud, would you recognise it as coming from this product?
  2. Which qualities need dialing up or down for this situation? Think of each voice quality as a dial. A celebratory moment turns up warmth; an error turns up clarity. No quality should ever be fully off — you never want to be unclear, or unhelpful, or cold. It's about emphasis.
  3. Apply the core principles (purpose, anticipation, context, empathy — detailed below).
  4. Apply the craft rules (remove filler, avoid repetition, be specific, lead with the why — detailed below).
When reviewing copy across multiple screens or files, flag terminology inconsistencies and suggest word list entries for new, missing or ambiguous terms.
对于每一段文案，按以下顺序处理：
  1. 它符合Voice吗？ 对照3-4个核心特质阅读文案。如果大声朗读，你能识别出这是来自该产品的文案吗？
  2. 针对当前场景，哪些特质需要调强或调弱？ 把每个Voice特质想象成一个旋钮。庆祝时刻可以调强“热情”；错误场景则调强“清晰”。任何特质都不应完全关闭——永远不要让文案变得模糊、无用或冷漠，只是调整侧重点而已。
  3. 应用核心原则（目的、预判、场景、共情——下文详细说明）。
  4. 应用写作技巧（删除冗余、避免重复、具体明确、先讲原因——下文详细说明）。
在审核多个页面或文件中的文案时，需指出术语不一致的地方，并建议为新的、缺失的或模糊的术语添加词汇表条目。

Step 4: Deliver changes

步骤4：交付修改内容

Provide specific rewrites inline — show the original, then the rewrite, with a brief rationale tied to the voice and principles. Prioritise changes that confuse or block users before polish. The user should be able to review the changes and approve or reject them.
提供具体的内联改写——展示原文，再给出改写后的版本，并附上与Voice和原则相关的简短理由。优先修改那些会让用户困惑或阻碍操作的内容，再进行润色。用户应能直接审核修改内容并决定批准或拒绝。

Voice and tone

Voice与语气

Voice vs. tone

Voice vs. 语气

Voice is the consistent personality of the product — the 3–4 qualities that define how it always sounds. These don't change.
Tone is how the voice adapts to the situation. Think of each voice quality as a dial you can turn up or down depending on the moment:
  • Celebrating a milestone? Turn up warmth, dial back brevity.
  • Reporting an error? Turn up clarity and helpfulness, dial back friendliness.
  • Onboarding a new user? Balance helpfulness with warmth.
  • Confirming a destructive action? Turn up direct, keep calm and concise.
No quality should ever be turned all the way off.
Voice是产品始终如一的个性——定义其语气风格的3-4个核心特质。这些特质不会改变。
语气是Voice根据场景做出的调整。把每个Voice特质想象成一个旋钮，可根据具体场景调高调低：
  • 庆祝里程碑？调强“热情”，调弱“简洁”。
  • 报告错误？调强“清晰”和“实用性”，调弱“友好”。
  • 用户新手指引？平衡“实用性”与“热情”。
  • 确认破坏性操作？调强“直接”，保持“冷静”和“简洁”。
任何特质都不应完全关闭。

Applying tone: a practical method

语气应用：实用方法

  1. Pick the 3–4 qualities that define the voice.
  2. For the specific situation, decide which qualities need emphasis.
  3. Place each quality on a spectrum from low to high emphasis.
  4. Write with that balance.
Example: For an error where someone can't connect to the network, clarity and helpfulness go way up — the person needs to know exactly what to do. Simplicity stays moderate because they need the most important details. Friendliness dials back because getting them unstuck is more important than sounding warm.
  1. 提炼出定义Voice的3-4个特质。
  2. 针对具体场景，确定哪些特质需要重点突出。
  3. 将每个特质置于“低-高”的侧重程度光谱上。
  4. 按照这个平衡来撰写文案。
示例：对于用户无法连接网络的错误场景，“清晰”和“实用性”要大幅调强——用户需要明确知道该怎么做。“简洁”保持中等，因为他们需要最重要的细节。“友好”调弱，因为帮他们解决问题比显得热情更重要。

Voice should never override usefulness

Voice永远不应凌驾于实用性之上

Personality shines in moments where it can — welcome screens, milestones, empty states. Don't force it into error messages or critical flows. If voice gets in the way of clarity, clarity wins every time. This is especially true for error messages, destructive actions and situations where the writing is articulating a problem.
个性应在合适的时刻展现——比如欢迎页面、里程碑时刻、空状态。不要在错误提示或关键流程中强行加入个性。如果Voice影响了清晰度，那么清晰度永远是第一位的。这一点在错误提示、破坏性操作和表述问题的场景中尤为重要。

Core principles

核心原则

These four principles — Purpose, Anticipation, Context, Empathy — form a framework for thinking about what to write, how to write it, and when. They apply through the lens of your voice.
这四个原则——目的、预判、场景、共情——构成了思考文案内容、表达方式和时机的框架。它们需在Voice的指导下应用。

1. Purpose

1. 目的

Every screen, every message, every label exists to help someone do something or understand something. Before writing, answer: what is the single most important thing the person needs to know right now?
  • Use information hierarchy to signal what matters most. Headlines and buttons carry the primary message. Supporting text fills in detail. People often read headers and buttons first — if someone reads only those, they should understand the situation.
  • Know what to leave out. If information doesn't serve the purpose of this moment, move it elsewhere or cut it. When a screen is trying to do too much, go back to its purpose and strip away everything that doesn't serve it.
  • Have a purpose for every screen in a flow. Define the purpose of the entire flow and each screen within it. This prevents redundant steps and keeps things brief.
  • Tell people the purpose — it's not a secret. When introducing a feature, tell them why it exists and why it matters to them using the voice and tone as appropriate to the situation.
每个页面、每条消息、每个标签的存在都是为了帮助用户完成某项操作或理解某个信息。撰写前先回答：用户当前最需要知道的一件事是什么？
  • 用信息层级突出重点。标题和按钮承载核心信息，辅助文本补充细节。用户通常会先阅读标题和按钮——如果用户只看这些内容，也应能理解当前场景。
  • 知道该省略什么。如果信息与当前时刻的目的无关，就将其移至别处或删除。如果一个页面试图承载太多内容，回到其核心目的，剔除所有无关的信息。
  • 明确流程中每个页面的目的。定义整个流程以及流程中每个页面的目的。这能避免冗余步骤，保持内容简洁。
  • 告知用户目的——这不是秘密。介绍功能时，结合场景和Voice，告诉用户它存在的原因以及对他们的价值。

2. Anticipation

2. 预判

Think of the interface as a conversation. In any good conversation there's a natural back and forth — listening, responding, anticipating what the other person needs to hear next.
  • After telling someone about a problem, tell them how to fix it.
  • After asking someone to do something, make it obvious how to do it.
  • After someone completes something, acknowledge it and point forward.
  • Lead with the "why". Put the benefit or reason before the instruction. "To get reservation updates, enter your phone number" is stronger than the reverse — the benefit is front-loaded where it has the most impact.
把界面想象成一场对话。在良好的对话中，有自然的互动——倾听、回应、预判对方接下来需要听到什么。
  • 告诉用户问题后，要告诉他们解决方法。
  • 要求用户执行操作后，要明确展示操作方式。
  • 用户完成操作后，要给予确认并指引下一步。
  • 先讲原因。把好处或原因放在指令前面。“为了获取预订更新，请输入你的手机号”比反过来的表述更有效——好处放在最前面，影响力最大。

3. Context

3. 场景

People use products in wildly different circumstances — on a busy train, mid-conversation, one-handed, in a crisis, at 2am. The usage context shapes the writing
  • Think outside the app. Consider the physical and emotional situation. Someone getting a health alert needs calm clarity; someone mid-exercise needs ultra-brief text they can read at a glance.
  • Match density to available attention. Mid-task text should be ultra-brief. Setup flows can afford a bit more. Bigger screens require brevity too, because text must be large for people to see it from a distance.
  • Timing matters. Show information when it's relevant, not before. Place instructions where the person is looking — if they're focused on a camera viewfinder, overlay the instruction near their focal point.
  • Write for the device. Screen size, input method, and usage patterns differ across devices and media. Describe gestures correctly — don't say "click" on a touch device. Consider that phones and watches offer personalisation but demand brevity; shared screens like TVs may be seen by multiple people.
用户使用产品的场景千差万别——在繁忙的火车上、交谈中、单手操作、危机时刻、凌晨2点。使用场景会影响文案写作。
  • 跳出应用本身思考。考虑物理和情绪场景。收到健康警报的用户需要冷静清晰的表述；运动中的用户需要能快速浏览的超短文本。
  • 匹配用户的注意力密度。任务进行中的文本应极其简洁。设置流程可以适当详细一些。大屏幕也需要简洁的文本，因为用户需要从远处看清，文本必须足够大。
  • 时机很重要。在信息相关时再展示，不要提前展示。把指令放在用户的视线焦点处——如果他们正专注于相机取景器，就将指令叠加在他们的焦点附近。
  • 针对设备撰写。不同设备和媒介的屏幕尺寸、输入方式和使用模式不同。正确描述操作手势——在触屏设备上不要说“点击”。考虑到手机和手表支持个性化但要求简洁；电视等共享屏幕可能被多人观看。

4. Empathy

4. 共情

You're writing for everyone who might use this product — different abilities, languages, cultures, levels of technical fluency, and emotional states.
  • Use plain, direct language. Avoid jargon, idioms, and culturally specific references that may not translate.
  • Design for accessibility from the start. Labels, descriptions, and alt text aren't afterthoughts — for some people, they're the entire experience. Every interactive element and every meaningful visual needs a thoughtful text label (see patterns reference for detailed guidance).
  • Avoid unnecessary references to gender, age, or ability. Use inclusive, neutral language.
  • Consider localisation. Text expands and contracts across languages. Some languages read right-to-left. Abbreviations work differently. Your UI needs to accommodate these changes — design short copy, not compressed long copy.
你是为所有可能使用该产品的人撰写文案——包括不同能力、语言、文化、技术水平和情绪状态的用户。
  • 使用平实、直接的语言。避免行话、习语和可能无法翻译的文化特定引用。
  • 从一开始就为可访问性设计。标签、描述和替代文本不是事后补充的——对某些用户来说，它们就是全部体验。每个交互元素和每个有意义的视觉元素都需要经过深思熟虑的文本标签（详见模式参考中的详细指导）。
  • 避免不必要的性别、年龄或能力相关表述。使用包容、中性的语言。
  • 考虑本地化。文本在不同语言中会有长短变化。有些语言是从右到左阅读的。缩写的用法也不同。你的UI需要适应这些变化——撰写简短的文案，而不是压缩长文案。

Writing craft

写作技巧

These are the practical editing moves that tighten copy. Apply them after you've confirmed the voice and tone are right.
这些是优化文案的实用编辑方法。在确认Voice和语气正确后再应用它们。

Remove filler words

删除冗余词汇

Interface text has no minimum word count. Every word must earn its place.
  • Adverbs and adjectives: "Simply enter your license plate" → "Enter your license plate." Words like "simply," "quickly," "easily," "just" promise something about the person's experience that you can't guarantee. However, a descriptive word that genuinely clarifies behaviour earns its place: "Feed your pets automatically" tells you something "Feed your pets" doesn't. The test: does the word add meaning, or is it filler?
  • Interjections: "Uh oh!", "Oops!", "Oh no!" in error messages can sound like you're not taking the problem seriously. Cut them.
  • Pleasantries: "Sorry" and "please" can sound insincere in automated messages. Use them only when they genuinely add warmth, not as padding.
  • Unnecessary punctuation: Exclamation marks should be rare. If everything is exciting, nothing is. Reserve them for genuinely celebratory moments.
The test: read the sentence without the word. If the meaning is unchanged, remove it.
界面文本没有最低字数要求。每个词都必须有存在的价值。
  • 副词和形容词：“Simply enter your license plate” → “Enter your license plate.” 像“simply”、“quickly”、“easily”、“just”这类词承诺了用户体验，但你无法保证。不过，能真正明确行为的描述性词汇是有价值的：“Feed your pets automatically”告诉了你“Feed your pets”没有的信息。判断标准：这个词是否增加了含义，还是只是冗余？
  • 感叹词：错误提示中的“Uh oh!”、“Oops!”、“Oh no!”会显得你没有认真对待问题。删除它们。
  • 客套语：自动消息中的“Sorry”和“please”可能显得不真诚。只有当它们能真正增添温暖感时才使用，不要作为填充。
  • 不必要的标点：感叹号应少用。如果所有内容都很“令人兴奋”，那就没有什么是真正令人兴奋的。只在真正的庆祝时刻使用感叹号。
判断方法：去掉这个词后读句子。如果意思不变，就删除它。

Avoid repetition

避免重复

Saying the same thing twice in different words is filler. Combine overlapping ideas into one clear statement.
"We're running late. Your delivery driver won't make it on time. They'll be there in 10 minutes." → "Delivery delayed 10 minutes. Check the app for your driver's location."
When headline and body say the same thing in different words, collapse them. Each element on screen should add new information.
用不同的词说同样的事情就是冗余。将重叠的想法合并成一个清晰的表述。
“We're running late. Your delivery driver won't make it on time. They'll be there in 10 minutes.” → “Delivery delayed 10 minutes. Check the app for your driver's location.”
如果标题和正文用不同的词表达同样的意思，就合并它们。屏幕上的每个元素都应提供新信息。

Be specific, not vague

具体明确，避免模糊

  • Name the thing: "Can't open 'Quarterly Report.pdf'" not "Can't open this file."
  • Name the action: "Cancel Subscription" / "Keep Subscription" not "Yes" / "No."
  • Give real information: "Your card ending in 4242 was declined" not "There was a payment error."
  • 明确指出事物：“无法打开‘Quarterly Report.pdf’”而非“无法打开此文件”。
  • 明确指出操作：“取消订阅”/“保留订阅”而非“是”/“否”。
  • 提供真实信息：“你尾号为4242的卡片支付失败”而非“支付出错”。

Lead with the why

先讲原因

Messaging is most effective when you tell people why the next step matters before telling them what it is. Structure as: "To [benefit], [instruction]."
  • "To keep your streak, solve today's crossword" beats the reverse.
  • "To get reservation updates, enter your phone number" beats the reverse.
This small reordering front-loads the motivation and makes the instruction feel like a reasonable ask instead of a demand.
当你在告诉用户下一步操作前先说明原因时，信息传递最有效。结构应为：“为了[好处]，请[操作]。”
  • “为了保持你的连续登录天数，请完成今日的填字游戏”比反过来的表述效果更好。
  • “为了获取预订更新，请输入你的手机号”比反过来的表述效果更好。
这种小小的语序调整将动机放在最前面，让指令看起来像是合理的请求而非要求。

Keep a word list

维护词汇表

Decide what you call things and stick to it. If you call it an "alias" on one screen, don't call it a "username" on another.
A word list is a simple table: Use / Don't use / Definition. It prevents terminology drift and helps anyone working on the product write consistently. Button labels are especially good word list entries — if "Next" advances through a flow, use "Next" everywhere, not "Continue" on one screen and "Proceed" on another.
Start small. Add a word at a time. As the list grows, it becomes a resource that defines how the product sounds. The list should be exist as part of the product's documentation and updated as the product evolves.
确定事物的命名并保持一致。如果在一个页面上称其为“alias”，不要在另一个页面上称其为“username”。
词汇表是一个简单的表格：使用 / 不使用 / 定义。它能防止术语偏差，并帮助所有参与产品工作的人保持文案一致。按钮标签是特别适合加入词汇表的内容——如果“Next”用于推进流程，那么所有地方都使用“Next”，不要在一个页面用“Continue”，另一个页面用“Proceed”。
从小规模开始，逐个添加词汇。随着列表的增长，它会成为定义产品语气风格的资源。词汇表应作为产品文档的一部分存在，并随产品的发展而更新。

Use possessive pronouns sparingly

谨慎使用所有格代词

"Favorites" conveys the same message as "Your Favorites" and is more succinct. If you do use possessive pronouns, be consistent and try not to switch perspectives. Avoid "we" — it's often unclear who "we" refers to, and in error messages ("We're having trouble loading this content") it obscures what actually happened. "Unable to load content" is clearer.
“Favorites”和“Your Favorites”传递的信息相同，但前者更简洁。如果使用所有格代词，要保持一致，不要切换视角。避免使用“we”——“we”通常指代不明，在错误提示中（“We're having trouble loading this content”）会掩盖实际发生的情况。“Unable to load content”更清晰。

Sweat the details

注重细节

Correct spelling, grammar, and punctuation make a product feel polished and trustworthy. Inconsistent capitalisation, stray punctuation, or typos erode confidence — especially in moments where trust matters (payments, permissions, health data).
Adopt capitalisation rules that align with the voice, then apply them consistently. Title case reads as formal; sentence case reads as casual. Choose a style for each UI element type and use it throughout.
Write for the space available. Buttons, notification titles, tooltips, and labels all have limited screen real estate. If copy needs to be short, write a short sentence — don't compress a long one.
正确的拼写、语法和标点能让产品显得精致可靠。不一致的大小写、多余的标点或拼写错误会削弱用户的信心——尤其是在信任至关重要的场景（支付、权限、健康数据）。
采用与Voice相符的大小写规则，并保持一致。标题大小写显得正式；句子大小写显得随意。为每种UI元素类型选择一种风格，并在整个产品中统一使用。
根据可用空间撰写文案。按钮、通知标题、工具提示和标签的屏幕空间都有限。如果文案需要简短，就写一个短句——不要压缩长句子。

Build language patterns

建立语言模式

Consistency builds familiarity. When the same type of situation always uses the same structure, the product feels cohesive and intuitive. Define patterns for common moments — how flows begin ("Get Started"), how they advance ("Next" or "Continue" — pick one), how they end ("Done"). Return to these patterns every time.
一致性能培养熟悉感。当相同类型的场景始终使用相同的结构时，产品会显得连贯且直观。为常见场景定义模式——流程如何开始（“Get Started”）、如何推进（“Next”或“Continue”——选一个）、如何结束（“Done”）。每次遇到相同场景都回归这些模式。

The simplest test

最简单的测试

Read your writing out loud. If it sounds like how you'd explain something to a friend — clear, natural, no filler — it's probably good. If it sounds like a robot, verbose, inconsistant, a legal document, or an essay, keep editing.
把你的文案大声读出来。如果它听起来像你向朋友解释事情的方式——清晰、自然、没有冗余——那它大概率是好的。如果它听起来像机器人说话、冗长、不一致、法律文件或散文，那就继续修改。

Patterns reference

模式参考

For detailed guidance on specific interface patterns — alerts, errors, empty states, onboarding flows, notifications, accessibility labels, destructive actions, buttons, and instructional copy — see 
references/patterns.md
.
如需针对特定界面模式的详细指导——警告、错误、空状态、引导流程、通知、可访问性标签、破坏性操作、按钮和说明文案——请查阅
references/patterns.md
。

Sources and further reading

参考资料与延伸阅读

This skill draws on:
本技能参考了以下资源：