ux-writing

Write or review UI copy — buttons, errors, empty states, microcopy, notifications, labels — using the voice & tone system (clear, concise, useful, human, honest) with the what→why→how error formula and inclusive-language rules. Use when the user needs interface copy, error messages, empty-state text, or a copy review.

跳到安装

仓库: plugin87/ux-ui-agent-skills
最近来源活动: 2026年6月8日 07:22
检测到的 SKILL.md 语言: 英语
星标: 502
分支: 43

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill ux-writing

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

design-component

Design a UI component spec to the house quality bar — anatomy, variants, sizes, the 8 states, token mapping, and accessibility. Use when the user wants to design or document a component (button, input, tabs, toast, combobox, date picker, modal, etc.) at the spec level before or alongside code. For generating framework code, use design-code.

2026-06-10

a11y-audit

Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and specific fixes. Use when the user wants an accessibility check, contrast verification, keyboard/screen-reader review, or wants to confirm a component meets POUR.

2026-06-08

design-code

Generate production-ready, accessible, token-driven component code for ANY framework — React+Tailwind, Next.js, SwiftUI, Vue, Svelte, Angular, Solid, Web Components/Lit, React Native, Flutter, Jetpack Compose, vanilla CSS, or CSS-in-JS. Use when the user wants working UI code for a component or screen in a specific stack.

2026-06-08

查看这个仓库的全部 Skills

Skill: UX Writing

Produce or critique interface copy in the project's voice.

Steps

Read content/voice-tone.md (voice principles, tone spectrum, formulas, microcopy patterns, inclusive language, pre-ship checklist).

Match tone to the user's emotional state (onboarding/success/routine/error/destructive). Higher stress → plainer language.

Apply the formulas:

Buttons: frontload the verb, name the outcome.
Confirmation dialogs: the confirm button restates the action and object — "Delete account", not "Delete"/"OK"/"Yes"/"Confirm". The title asks ("Delete account?"), the button answers in matching words. Cancel stays "Cancel". For irreversible/high-stakes actions, require a type-to-confirm step (WCAG 3.3.4/3.3.6).
Errors: what happened → why → how to fix (no dead ends, no codes/stack traces).
Empty states: value → first action.

Enforce mechanics: sentence case, no ALL CAPS, numerals, no blame on the user, labels (not placeholders), no directional/color-only instructions.

Run the 10-item pre-ship copy checklist.

Output

Final copy (or a redline review) that reads naturally aloud and passes the checklist. Keep within any character limits for tight UI.

Verification (mandatory before declaring done)

Run every line through the 10-item pre-ship checklist in content/voice-tone.md — do not skip it:

Reads naturally aloud; frontloaded verb on actions; no jargon/blame/dead-ends.

Errors follow what→why→how; empty states give value→action; no bare "No data"/"Error".

Mechanics: sentence case, numerals, labels (not placeholders), no color/direction-only cues, inclusive language.

Within character limits; translatable (no concatenation — see accessibility/i18n-rtl.md).

Skill: UX Writing

Produce or critique interface copy in the project's voice.

Steps

Read content/voice-tone.md (voice principles, tone spectrum, formulas, microcopy patterns, inclusive language, pre-ship checklist).

Match tone to the user's emotional state (onboarding/success/routine/error/destructive). Higher stress → plainer language.

Apply the formulas:

Buttons: frontload the verb, name the outcome.
Confirmation dialogs: the confirm button restates the action and object — "Delete account", not "Delete"/"OK"/"Yes"/"Confirm". The title asks ("Delete account?"), the button answers in matching words. Cancel stays "Cancel". For irreversible/high-stakes actions, require a type-to-confirm step (WCAG 3.3.4/3.3.6).
Errors: what happened → why → how to fix (no dead ends, no codes/stack traces).
Empty states: value → first action.

Enforce mechanics: sentence case, no ALL CAPS, numerals, no blame on the user, labels (not placeholders), no directional/color-only instructions.

Run the 10-item pre-ship copy checklist.

Output

Final copy (or a redline review) that reads naturally aloud and passes the checklist. Keep within any character limits for tight UI.

Verification (mandatory before declaring done)

Run every line through the 10-item pre-ship checklist in content/voice-tone.md — do not skip it:

Reads naturally aloud; frontloaded verb on actions; no jargon/blame/dead-ends.

Errors follow what→why→how; empty states give value→action; no bare "No data"/"Error".

Mechanics: sentence case, numerals, labels (not placeholders), no color/direction-only cues, inclusive language.

Within character limits; translatable (no concatenation — see accessibility/i18n-rtl.md).

name	ux-writing
description	Write or review UI copy — buttons, errors, empty states, microcopy, notifications, labels — using the voice & tone system (clear, concise, useful, human, honest) with the what→why→how error formula and inclusive-language rules. Use when the user needs interface copy, error messages, empty-state text, or a copy review.

ux-writing

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Skill: UX Writing

Steps

Output

Verification (mandatory before declaring done)

Skill: UX Writing

Steps

Output

Verification (mandatory before declaring done)