microcopy

Provide structured UI copy guidelines for English and Chinese content.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Staysr/lobe-windos-build --skill microcopy-staysr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: microcopy
Source: https://github.com/Staysr/lobe-windos-build/tree/main/.agents/skills/microcopy
Command: npx skills add https://github.com/Staysr/lobe-windos-build --skill microcopy-staysr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI copy and microcopy guidelines tackle inconsistency and translation challenges across interfaces, helping teams write clear, user-friendly text in multiple languages.

Core Features & Use Cases

  • Fixed Terminology: Establishes consistent terms across products to reduce confusion.
  • Brand Principles & Writing Rules: Defines the voice, tone, and actionable writing patterns to guide every user-facing message.
  • Patterns & Errors/Exceptions: Provides common messaging patterns for getting started, latency, and failure states; includes error handling guidance.
  • Multilingual Support: Triggers on i18n translation for English and Chinese content, ensuring bilingual clarity.

Quick Start

Follow these guidelines when drafting any UI text to ensure consistency, clarity, and a user-centered voice.

Frequently Asked Questions about microcopy

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

FAQPage Schema
What are UI microcopy guidelines and why do I need them for my interface?

UI microcopy guidelines establish consistent terminology, brand voice, and actionable writing patterns to ensure user-facing text is clear and reduces translation confusion across digital products.

How do I write bilingual UI copy for English and Chinese interfaces?

Writing bilingual UI copy requires triggering i18n translation rules that map fixed terminology and brand voice patterns, ensuring your English and Chinese interface text maintains clarity and consistency.

What's the best way to standardize UX writing for error messages and onboarding flows?

Standardizing UX writing involves applying predefined messaging patterns for getting started, latency, and failure states, paired with error handling guidance to drive consistent onboarding and error messages.

Does this microcopy approach support both UI text and button label formatting?

Yes, structured microcopy guidelines apply directly to UI text and button labels, providing terminology mappings and actionable writing patterns to keep interface copy consistent across user journeys.

Can I use these UX writing rules for internationalization and translation workflows?

Yes, these guidelines trigger on i18n translation workflows for English and Chinese content, mapping terminology and applying brand voice rules to ensure bilingual clarity during interface localization.

Why does my interface copy feel inconsistent across different products and screens?

Interface copy feels inconsistent when lacking fixed terminology and defined brand voice rules; establishing terminology mappings and actionable writing patterns across products reduces user confusion.