制定用户界面内容风格指南
统一产品界面的用词、语气、组件文案和本地化规则,输出可供设计与开发使用的规范。
完整提示词
<context>
Brand voice guides describe how a company sounds; they rarely settle the mechanical questions that cause most UI inconsistency. Which case for buttons and headings (sentence case is easier to read and translate), whether labels end with periods, "Sign in" or "Log in", "Delete" or "Remove" (removing usually means it still exists elsewhere), "my" or "your" in navigation. Strong UI text patterns are specific: buttons say what will happen ("Delete project", not "OK"), destructive confirmations repeat the action in the button, and error messages say what happened, why if known, and what to do next, without blame and without an error code as the only content. Dates like 03/04/2026 are read differently by country, so formats should come from locale-aware formatting, not hard-coded strings, and relative times need an absolute time on hover or nearby. One term per concept matters more than any rule: a product that says "workspace", "team" and "organisation" for the same thing confuses users and translators. Placeholder text is not a label, "click here" is not a link, and English text grows by a third or more in many languages, so layouts must allow it.
</context>
<task>
Write the UI content style guide for this product.
<product>
{{product}}
</product>
<samples>
{{samples}}
</samples>
{{#locales}}Locales: {{locales}}.
{{/locales}}
1. **Principles.** Three to five principles for UI text derived from the voice, each with a short before and after from the samples.
2. **Mechanics.** Capitalisation, punctuation in labels, headings and tooltips, contractions, pronouns, abbreviations, symbols such as ampersands, and emoji, each with a rule and an example.
3. **Component patterns.** Rules and examples for buttons and links, form labels and helper text, placeholders, tooltips, empty states, toasts, dialogs and confirmation dialogs, and navigation labels.
4. **Messages.** Patterns for errors (validation, system, permission, offline), warnings, success and destructive confirmations, with templates and rewrites of real samples.
5. **Numbers dates and units.** Numerals, thousands and decimals, currency, percentages, ranges, dates, times, time zones and relative time, all through locale-aware formatting.
6. **Terminology list.** A table of preferred terms, terms to avoid and definitions, built from inconsistencies in the samples. Flag conflicts the team must decide.
7. **Accessibility and localisation.** Link and button text that makes sense out of context, alt text, no meaning by colour or position words alone, avoiding idioms, string expansion, no concatenated sentences in code, and plural handling.
8. **Review checklist.** Ten to fifteen checks a designer or engineer can run before shipping a screen.
</task>
<constraints>
- Base rules on the samples and voice given; where you choose between valid conventions, say which and why.
- Do not invent product features, legal wording or terms not supported by the samples; mark gaps as open questions.
- Keep examples in the product's domain, not generic.
{{> output/uncertainty}}
</constraints>
<output_format>
Markdown with the sections from the contract, in order. Rules as short bullets with examples, terminology as a table, checklist as checkboxes. End with Open questions.
</output_format>可替换内容
- {{product}}
- {{samples}}
- {{#locales}}
- {{locales}}
- {{/locales}}
- {{> output/uncertainty}}
分类与标签
设计创意、UI文案、内容设计、设计系统、本地化规范