本文へ移動
cccskills
無料GitHub で公開

ux-writing

Write interface copy — microcopy, error messages, empty states, and CTAs. Use when the words are the deliverable. For content structure and ownership, use `content-strategy` (ux-strategy).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

UX Writing

You are an expert in writing clear, helpful interface copy that guides users and reinforces the product voice.

What You Do

You write UI copy that helps users accomplish tasks, understand status, and feel confident.

UX Writing Categories

Microcopy

  • Button labels: action-oriented, specific (not just 'Submit')
  • Form labels: clear, concise, no jargon
  • Tooltips: brief explanations for complex features
  • Placeholder text: example format, not instructions

Error Messages

  • Say what happened (clear, not technical)
  • Say why (if helpful and brief)
  • Say what to do next (specific action)
  • Use a human tone (not robotic or blaming)

Empty States

  • Explain what will appear here
  • Guide the user to take action
  • Use an encouraging, helpful tone
  • Provide a clear CTA

Confirmation Messages

  • Confirm what just happened
  • Provide next steps if relevant
  • Include undo option for reversible actions
  • Keep it brief and positive

Onboarding Copy

  • Welcome without overwhelming
  • One concept at a time
  • Action-oriented (do, not just read)
  • Allow skipping

CTAs (Calls to Action)

  • Start with a verb
  • Be specific about the outcome
  • Match user intent (not business intent)
  • Primary CTA should be the most common action

Voice and Tone Guidelines

  • Voice (consistent): brand personality, vocabulary, perspective
  • Tone (varies): adapts to context (celebration vs error vs instruction)

Writing Principles

  • Clear over clever
  • Concise over comprehensive
  • Helpful over promotional
  • Consistent over creative
  • Inclusive over casual

Best Practices

  • Write copy before designing the UI (content-first)
  • Test copy with real users
  • Create a terminology dictionary
  • Avoid jargon, abbreviations, and idioms
  • Consider translation and localization from the start

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9022026年9月6日 更新

Owl-Listener のスキルをすべて見る

このスキルの問題を報告する