ux-writing-content-design
Use when writing, critiquing, or implementing product UX copy, microcopy, labels, CTAs, empty states, onboarding, errors, or notifications.
hueyexe · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add hueyexe/frontend-agent-skills --skill ux-writing-content-design技能说明
name: ux-writing-content-design description: "Use when writing, critiquing, or implementing product UX copy, microcopy, labels, CTAs, empty states, onboarding, errors, or notifications." license: MIT metadata: author: hueyexe
UX Writing & Content Design
Purpose
Help an AI agent write and evaluate product copy that helps people understand an interface, take action, recover from problems, and trust the product. Treat words as part of the design system and interaction model, not as decoration added after the interface is finished.
This skill covers product UX copy: microcopy, button labels, links, labels, hints, descriptions, empty states, onboarding, validation, errors, success messages, loading/progress states, notifications, terminology, voice, tone, and content strategy. It does not cover long-form marketing copy except when that copy directly affects product comprehension, action, trust, onboarding, or conversion inside a product experience.
When to use this skill
Use this skill when the user asks you to:
- Write, rewrite, or critique UI text, product copy, UX copy, microcopy, form copy, navigation labels, CTAs, onboarding, empty states, errors, confirmations, loading states, notifications, help text, or design-system content guidance.
- Review a UI, mockup, screenshot, frontend component, flow, prototype, or design system for clarity, tone, usability, trust, recovery, or accessibility.
- Design or implement frontend states where copy affects user understanding or behavior.
- Create content rules, voice and tone guidance, terminology, content patterns, or a UX writing checklist.
When not to use this skill
Do not use this skill as the primary skill for:
- Long-form marketing pages, ads, brand campaigns, PR, SEO articles, or sales copy unless they affect an in-product UX flow.
- Pure visual styling, layout, illustration, or animation tasks where no interface text, state, or comprehension issue is involved.
- Legal, medical, financial, or compliance wording that requires a licensed professional. You may improve clarity, but flag the need for expert review.
- Translation/localization itself. Use this skill to make source copy localizable and context-safe, then use translation/localization expertise separately.
Core principles
- Words are design material. Do not merely choose “nice words.” Use words to solve user problems and shape interaction behavior.
- Start with the user task and product purpose. Copy is effective only when it supports what the user is trying to do and what the product legitimately needs.
- Prefer useful over clever. Personality and delight are secondary to comprehension, action, trust, and recovery.
- Design the conversation, not isolated strings. Inspect the entry point, action, system response, next step, inverse action, and failure path.
- Use the right pattern for the state. A label, hint, tooltip, inline error, banner, empty state, notification, or confirmation each has a different job.
- Write in context. Draft and evaluate text where it appears, with surrounding UI, component constraints, state, platform, and device.
- Make actions consequence-revealing. Buttons and links should say what happens, not describe the input method.
- Errors are stress cases. Avoid the error when possible, explain clearly when it happens, and help the user resolve it.
- Respect people on the margins. Sensitive questions, forced choices, default suggestions, and “harmless” quick replies can exclude or hurt people.
- Be concise, not cryptic. Short copy is valuable only when users can still understand it immediately.
- Measure when the stakes justify it. Use usability testing, behavioral metrics, support data, and A/B tests when copy changes affect activation, conversion, retention, recovery, or trust.
- Make copy implementable. Content should work with semantic HTML, accessibility APIs, localization, design tokens, component states, and design-system patterns.
See references/principle-cards.md for each principle as a reusable card.
Default recommendations
Use these defaults unless the user provides stronger product-specific context.
| Area | Default recommendation | Why it is usually best | Override when | Ask before overriding |
|---|---|---|---|---|
| Product goal | Help the user complete the immediate task with minimal uncertainty. | Most product copy is functional and users are not there to read. | The flow intentionally teaches, warns, or changes a high-stakes decision. | Ask what outcome matters most: comprehension, conversion, completion, retention, safety, or support reduction. |
| Audience | Write for a broad, busy, mixed-ability audience using plain language. | It reduces cognitive load and improves accessibility/localization. | The product serves a specialized expert audience with necessary domain terms. | Ask whether the audience expects domain-specific terminology. |
| Voice | Professional, warm, direct, and human. | Works for most SaaS, productivity, commerce, and public-service products. | A documented brand voice or regulated tone exists. | Ask for the brand personality or voice chart. |
| Tone | Calm and helpful. Match emotional stakes. | Users often encounter copy during uncertainty or interruption. | Success/delight states can support more warmth; severe or sensitive states require restraint. | Ask how stressful or sensitive the moment is. |
| CTA labels | Verb-led, specific, 1–3 words where possible; include object or consequence when needed. | Users make decisions at buttons and links. | Legal, destructive, paid, or irreversible actions need more specificity. | Ask what exactly happens after the action. |
| Form labels | Persistent visible labels above or beside fields; hints only for extra guidance. | Labels remain available after entry and support accessibility. | Very constrained UI already has a tested accessible pattern. | A |