ui-copy

Writes and reviews UI copy, microcopy, and user-facing product wording.

553|70|Updated Feb 28, 2023

Search Tags:#microcopy #ux writing #empty states #error messages #button labels #ui copy #product wording

One-click install

npx skills add https://github.com/operately/operately --skill ui-copy-operately

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: ui-copy
Source: https://github.com/operately/operately/tree/main/.agents/skills/ui-copy
Command: npx skills add https://github.com/operately/operately --skill ui-copy-operately

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface text is often written as an afterthought, resulting in vague buttons, confusing errors, and inconsistent terminology that block users from completing tasks. This Skill provides a structured workflow and principles for writing clear, task-oriented UI copy. ## Core Features & Use Cases - Copywriting Workflow: A six-step process covering user goal identification, vocabulary matching, drafting, tightening, expectation-setting, and consistency scanning. - Component-Specific Guidance: Concrete rules and examples for buttons, links, empty states, error messages, confirmations, and success messages. - Product Vocabulary Guardrails: Prevents internal code names (like "Resource Hub") from leaking into user-facing text. - Use Case: When designing a destructive action dialog, use this Skill to replace a vague "Are you sure?" with copy that names the object, consequence, and escape path, such as "Delete 'Q3 launch plan'? This removes the task for everyone." ## Quick Start Use the ui-copy skill to review and rewrite the button labels and error messages on this settings screen.

Frequently Asked Questions about ui-copy

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

FAQPage Schema

How to write good error messages in UX writing?▼

Error messages should explain what happened in user terms and provide a recovery path. Replace "System error #2234" with something like "The password is incorrect. Try again or reset your password."

What should an empty state message include?▼

An empty state should say what is missing and offer the next useful action. For example, "No matching tasks. Try a different filter or create a task." is more helpful than a bare "No results."

When should I avoid humor in UI copy?▼

Avoid humor in repetitive, high-friction, high-risk, error, payment, privacy, or destructive flows. Clarity and honesty take priority over personality in any situation where the user faces risk or frustration.

Should internal feature names appear in user-facing text?▼

No. Internal names that exist only in code or schemas, such as "Resource Hub", should never appear in UI copy. Use the user-facing terms already established in the product, like "Documents & Files" or specific item types.