
microcopy
PopulaireUI copy and microcopy guidelines. Use when writing UI text, buttons, error messages, empty states, onboarding, or any user-facing copy. Triggers on i18n translation, UI text writing, or copy improvement tasks. Supports both Chinese and English.
UI copy and microcopy guidelines. Use when writing UI text, buttons, error messages, empty states, onboarding, or any user-facing copy. Triggers on i18n translation, UI text writing, or copy improvement tasks. Supports both Chinese and English.
LobeHub UI Microcopy Guidelines
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 |
Brand Principles
- Create: One sentence → usable Agent; clear next step
- Collaborate: Multi-agent; shared Context; controlled
- Evolve: Remember with consent; explainable; replayable
Writing Rules
- Clarity first: Short sentences, strong verbs, minimal adjectives
- Layered: Main line (simple) + optional detail (precise)
- Consistent verbs: Create / Connect / Run / Pause / Retry / View details
- 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:
- Acknowledge situation (no judgment)
- Restore control (pause/replay/edit/undo/clear Memory)
- 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:
- What happened
- (Optional) Why
- What user can do next
Provide: Retry / View details / Go to Settings / Contact support / Copy logs
Never blame user. Put error codes in "Details".
You Might Also Like
Related Skills

verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
facebook
test
Use when you need to run tests for React core. Supports source, www, stable, and experimental channels.
facebook
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
facebook
extract-errors
Use when adding new error messages to React, or seeing "unknown error code" warnings.
facebook