microcopy

UI copy and microcopy guidelines. Use for user-facing copy, buttons, errors, empty states, onboarding, i18n wording, translation, or copy improvements in Chinese or English.

lobehub/lobehub2.6k installsApache-2.0Synced Aug 23

Works with

Claude CodeCursorCodex CLIGitHub CopilotGemini CLI
---
name: microcopy
description: UI copy and microcopy guidelines. Use for user-facing copy, buttons, errors, empty states, onboarding, i18n wording, translation, or copy improvements in Chinese or English.
license: Apache-2.0
---

# LobeHub UI Microcopy Guidelines

This file is the quick-reference summary. For full prompt-style guidelines with extensive examples (anti-patterns, tone matrices, scenario walk-throughs), load the language-specific reference:

- **中文文案** — [`references/zh.md`](./references/zh.md)
- **English copy** — [`references/en.md`](./references/en.md)

Brand: **Where Agents Collaborate** - Focus on collaborative agent system, not just "generation".

## Fixed Terminology

| Chinese    | English       |
| ---------- | ------------- |
| 空间       | Workspace     |
| 助理       | Agent         |
| 群组       | Group         |
| 上下文     | Context       |
| 记忆       | Memory        |
| 连接器     | Integration   |
| 技能       | Skill         |
| 助理档案   | Agent Profile |
| 话题       | Topic         |
| 文稿       | Page          |
| 社区       | Community     |
| 资源       | Resource      |
| 库         | Library       |
| 模型服务商 | Provider      |
| 评测       | Evaluation    |
| 基准       | Benchmark     |
| 数据集     | Dataset       |
| 用例       | Test Case     |

## Brand Principles

1. **Create**: One sentence → usable Agent; clear next step
2. **Collaborate**: Multi-agent; shared Context; controlled
3. **Evolve**: Remember with consent; explainable; replayable

## Writing Rules

1. **Clarity first**: Short sentences, strong verbs, minimal adjectives
2. **Layered**: Main line (simple) + optional detail (precise)
3. **Consistent verbs**: Create / Connect / Run / Pause / Retry / View details
4. **Actionable**: Every message tells next step; avoid generic "OK/Cancel"

## Human Warmth (Balanced)

Default: **80% information, 20% warmth**
Key moments: **70/30** (first-time, empty state, failures, long waits)

**Hard cap**: At most half sentence of warmth, followed by clear next step.

**Order**:

1. Acknowledge situation (no judgment)
2. Restore control (pause/replay/edit/undo/clear Memory)
3. Provide next action

**Avoid**: Preachy encouragement, grand narratives, over-anthropomorphizing

## Patterns

**Getting started**:

- "Starting with one sentence is enough. Describe your goal."
- "Not sure where to begin? Tell me the outcome."

**Long wait**:

- "Running… You can switch tasks—I'll notify you when done."
- "This may take a few minutes. To speed up: reduce Context / switch model."

**Failure**:

- "That didn't run through. Retry, or view details to fix."
- "Connection failed. Re-authorize in Settings, or try again later."

**Collaboration**:

- "Align everyone to the same Context."
- "Different opinions are fine. Write the goal first."

## Errors/Exceptions

Must include:

1. **What happened**
2. (Optional) **Why**
3. **What user can do next**

Provide: Retry / View details / Go to Settings / Contact support / Copy logs

Never blame user. Put error codes in "Details".

More Project Management skills

← All Project Management skills

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY