AGENT SKILL

ux-copy

Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone

License 许可
MIT
所属仓库
MHassan0000/Skills
最近更新
2026-08-07
Stars
★ 1
Forks
0

01 前言 Front Matter

name
ux-copy
risk
critical
source
https://github.com/bitjaru/styleseed/tree/main/engine/.claude/skills/ss-copy
license
MIT
date_added
1782864000000
description
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone
source_repo
bitjaru/styleseed
source_type
community
license_source
https://github.com/bitjaru/styleseed/blob/main/LICENSE

03 SKILL.md 正文

UX Microcopy Generator

When to Use

Use this skill when you need generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone.

When NOT to use

  • For long-form content (blog posts, docs, marketing pages) — out of scope
  • For full feedback state design (not just text) → use /ss-feedback
  • For brand voice/tone definition itself — this skill consumes a voice spec, doesn't create it
  • For translations to non-English languages — single-language only

Context: $0 Description: $ARGUMENTS

Read engine/UX-WRITING.md first — it's the rule set this skill applies: buttons name the action (not "Submit"), errors help instead of blame, empty states invite, money copy stays calm, one term per concept. Korean/CJK projects: see §W8 for the clear-calm-human "Toss feel" (존댓말 일관성, 사용자 관점 "내 계좌", 군더더기 빼기).

Instructions

  1. Read the design language reference:

    • DESIGN-LANGUAGE.md sections on Microcopy Tone Guide and UX Writing
  2. Apply the voice principles:

Tone Rules

  • Casual but polite: Friendly, not robotic. Like talking to a helpful friend.
  • Active voice: "We saved your changes" not "Your changes have been saved"
  • Positive framing: "Free shipping on orders over $30" not "Orders under $30 have shipping fees"
  • Plain language: "Send money" not "Initiate transfer"
  • Concise: Every word must earn its place

Copy Patterns by Context

Button Labels (CTA)

Format: [Action verb] + [Object] (optional)
Good: "Place order", "Get started", "Save changes", "Try again"
Bad:  "Submit", "OK", "Click here", "Proceed to next step"
  • One primary CTA per screen
  • Label must clearly describe what happens next
  • Max 3 words for primary CTA

Empty States

Format: [Friendly observation] + [Suggested action]
Good: "No activity yet. Create your first project to get started."
Bad:  "No data found."
  • Always suggest a next action
  • Use a relevant icon (32px, text-text-tertiary)
  • Tone: encouraging, not blaming

Error Messages

Format: [What happened] + [What to do]
Good: "Couldn't load the data. Please try again."
Bad:  "Error 500: Internal Server Error"
  • Never show technical errors to users
  • Blame the system, not the user
  • Always provide a recovery action

Toast Notifications

Format: [Confirmation of what happened]
Good: "Saved!", "Changes applied", "Item deleted · Undo"
Bad:  "Operation completed successfully"
  • Max 2 lines
  • Include "Undo" link for reversible destructive actions
  • Info toasts: 3 seconds. Action toasts: 5 seconds.

Form Labels & Helpers

Label: Noun phrase ("Email address", "Password")
Placeholder: Example or hint ("name@example.com")
Helper: Format guidance ("Must be at least 8 characters")
Error: Specific issue ("This email is already registered")

Confirmation Dialogs

Title: [Question about the action]
Body: [Consequence explanation]
Primary: [Action verb] ("Delete", "Confirm")
Secondary: "Close" (not "Cancel" — avoids confusion)
  1. Generate copy for the requested context, providing:
    • Primary copy (what to display)
    • Variants (if context varies)
    • Do's and Don'ts for the specific context

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

04 同仓库更多 Skills

MHassan0000
MHassan0000/Skills

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

★ 1
MHassan0000
MHassan0000/Skills

stop-slop

Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.

★ 1
MHassan0000
MHassan0000/Skills

ogilvy-copywriting

Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.

★ 1
MHassan0000
MHassan0000/Skills

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

★ 1
MHassan0000
MHassan0000/Skills

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

★ 1
MHassan0000
MHassan0000/Skills

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

★ 1