microcopy

Enforce LobeHub brand voice and fixed terminology in Chinese and English UI microcopy.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kingheu0818-sketch/lobehub_yu --skill microcopy-kingheu0818-sketch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microcopy
Source: https://github.com/kingheu0818-sketch/lobehub_yu/tree/main/.agents/skills/microcopy
Command: npx skills add https://github.com/kingheu0818-sketch/lobehub_yu --skill microcopy-kingheu0818-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you produce user-facing UI microcopy that matches LobeHub’s brand, terminology, and interaction principles—so interfaces feel trustworthy, consistent, and easy to act on.

Core Features & Use Cases

  • UI copy guidance: Standardizes tone, structure, and phrasing for buttons, errors, empty states, onboarding, and prompts.
  • Terminology consistency: Enforces fixed product terms (e.g., Workspace, Agent, Context, Memory) to avoid confusing or mixed wording.
  • EN/CN handling: Supports writing and translating copy for both Chinese and English with length- and intent-aware localization.

Quick Start

Use the microcopy Skill to rewrite or improve a specific UI string (for example, an empty-state message or an error toast) to match LobeHub’s terminology and provide a clear next step.

Frequently Asked Questions about microcopy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write clear and actionable UI microcopy for error messages and empty states?

UI microcopy for error messages and empty states should enforce brand voice, use fixed terminology, and provide a clear next step. This ensures interfaces feel trustworthy, consistent, and easy to act on.

How do I maintain terminology consistency across onboarding copy and UI text?

Maintain terminology consistency in onboarding copy by enforcing fixed product terms like Workspace, Agent, Context, and Memory. This prevents confusing or mixed wording across different UI components and user touchpoints.

What is the best way to handle UI copy localization for Chinese and English interfaces?

UI copy localization for Chinese and English requires length-aware and intent-aware translation. Apply language guidelines to produce consistent copy that matches the brand voice and interaction principles across both languages.

Can I use this approach to standardize tone and phrasing for buttons and failure messages?

Yes, you can standardize tone, structure, and phrasing for buttons, failure messages, and permission prompts. Apply reference-based language guidelines to rewrite specific UI strings to match fixed product terminology and interaction principles.

How does human-in-the-loop localization improve i18n translation tasks?

Human-in-the-loop localization improves i18n translation by applying length-aware language guidelines to produce consistent copy. It ensures translations match brand voice and fixed terminology while remaining actionable across Chinese and English interfaces.