C✳CODEZ.WIN
🌐 English

Localized reading guide

ux-copyPurpose, usage and source

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
design/skills/ux-copy/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Design
Last collected

License: Apache-2.0

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

How the upstream workflow works

/ux-copy

> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Write or review UX copy for any interface context.

Upstream passage · L7 ↗

What I Need From You

Context: What screen, flow, or feature? User state: What is the user trying to do? How are they feeling?

Upstream passage · L19 ↗

Principles

Clear: Say exactly what you mean. No jargon, no ambiguity. Concise: Use the fewest words that convey the full meaning.

Upstream passage · L26 ↗
Upstream passage · ↗
/ux-copy $ARGUMENTS

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
d46a00a62ec637e9ca9d5f7823ea3e0a4ec26dffc53bb5035f59b48ebfcdcde7
Back to the full Skill catalog