microcopy_skill

This skill helps you craft clear, user-friendly UI copy and microcopy that aligns with brand guidelines and improves onboarding and error messaging.

TypeScript

70.5k

GitHub Stars

1

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill lobehub/lobe-chat --skill microcopy

SKILL.md2.5 KB

Overview

This skill provides UI copy and microcopy guidelines tailored for collaborative agent interfaces. It helps authors write clear, actionable, and consistent UI text for buttons, errors, empty states, onboarding, and translations. The guidance supports both English and Chinese terminology and emphasizes collaboration-focused language and user control.

How this skill works

The skill inspects UI copy requests and suggests concise main lines plus optional detail lines, consistent verbs, and human-warmth levels. It flags terminology mismatches, offers localized equivalents (Chinese ↔ English), and produces ready-to-use microcopy for common patterns like onboarding, failures, long waits, and empty states. It also supplies next-step actions and error remediation text with structured details.

When to use it

Writing or refining UI text for buttons, menus, labels, and tooltips
Drafting error messages, retry flows, or diagnostic details
Creating empty states, onboarding prompts, and first-time user tips
Preparing i18n translation pairs or ensuring consistent terminology
Designing multi-agent collaboration prompts, shared Context copy

Best practices

Put clarity first: short sentences, strong verbs, minimal adjectives
Use layered copy: main line (simple) plus optional detail (precise)
Prefer consistent verbs: Create, Connect, Run, Pause, Retry, View details
Make every message actionable: show the next step or control
Keep human warmth minimal: ~20% warmth in tone, more only for key moments
Errors must state what happened, why (if known), and clear next actions

Example use cases

A button label: 'Create agent' with tooltip: 'One sentence → usable Agent; describe the goal.'
Error prompt: 'Connection failed. Re-authorize in Settings, or try again later.' with 'View details' option
Long-wait notice: 'Running… You can switch tasks — I’ll notify you when done.' plus speed-up tips
Empty state: 'Starting with one sentence is enough. Describe your goal.' with a clear CTA
i18n check: convert '空间' → 'Workspace' and ensure consistent use across screens

FAQ

Yes. It provides preferred terminology pairs and guidance to keep terms consistent across languages.

How should errors be formatted?

State what happened, optionally why, and present clear next actions like Retry, View details, or Go to Settings.