ss-copy
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone
By bitjaru · 711 installs
npx skills add bitjaru/styleseed --skill ss-copy
Source repository · Upstream listing
UX Microcopy Generator
Registry first artifact boundary
When .styleseed/project.json and .styleseed/artifacts/index.json exist, resolve the requested artifact ID first, then read only .styleseed/bundles/<artifact id .md and .styleseed/manifests/<artifact id .json . Never fall back to the global legacy bundle for a registry project. Legacy projects may use .styleseed/effective rules.md only when no registry exists.
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)
One primary CTA per screen
Label must clearly describe what happens next
Max 3 words for primary CTA
Empty States
Always suggest a next action
Use a relevant icon (32px, text text tertiary)
Tone: encouraging, not blaming
Error Messages
Never show technical errors to users
Blame the system, not the user
Always provide a recovery action
Toast Notifications
Max 2 lines
Include "Undo" link for reversible destructive actions
Info toasts: 3 seconds. Action toasts: 5 seconds.
Form Labels & Helpers
Confirmation Dialogs
3. 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