ss-copy

Featured

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

Web & Frontend 852 stars 75 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
98
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# UX Microcopy Generator ## 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...

Details

Author
bitjaru
Repository
bitjaru/styleseed
Created
3 months ago
Last Updated
5 days ago
Language
TypeScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

ux-copy

Use when writing or reviewing UI text — buttons, error messages, empty states, onboarding, confirmation dialogs, notifications, tooltips, labels, and any user-facing copy in React/Next.js components. Covers voice and tone calibration, microcopy patterns, copy auditing, and refactoring existing copy for consistency and clarity.

3 Updated today
LeahyCC
Web & Frontend Listed

ux-copy-writer

You are an expert UX copywriter specializing in microcopy — the small bits of text that guide users through interfaces. Your copy is clear, human, concise, and helpful. ## Process 1. Identify the UI element needing copy (button, error, tooltip, empty state, etc.) 2. Understand the context and user's mental state 3. Write 3-5 variations of the copy 4. Select the best option based on clarity, tone, and brevity 5. Explain why the chosen copy works ## Output Format ### UI Element: \[type\] Variations: 1. 'Option 1' 2. 'Option 2' 3. 'Option 3' ✅ Recommended: 'Best option' Why this works: Explanation Tone: \[friendly/professional/playful/etc.\] Character count: \[X\] ## Microcopy Principles - Answers the user's next question before they ask it - Uses active voice: 'Save changes' not 'Changes will be saved' - Matches emotional context: error states should feel supportive, not blaming -...

0 Updated 1 weeks ago
prvthmpcypher
AI & Automation Listed

sota-ux-writing

State-of-the-art UX writing and product-copy guidance (2026) covering voice and tone systems, plain language (ISO 24495-1), microcopy (buttons, labels, empty states, onboarding, notifications), error and feedback message craft, and the accessibility and localization of interface language (WCAG 2.2 language criteria, alt text, ICU pluralization, i18n-safe strings). Use when writing or reviewing ANY user-facing interface text — web, mobile, desktop, or CLI products — AND when auditing existing product copy for clarity, consistency, tone, accessibility, and localization readiness. Trigger keywords: UX writing, microcopy, product copy, content design, error message, empty state, button label, tooltip, onboarding copy, form label, placeholder, notification, toast, confirmation dialog, tone of voice, terminology, plain language, readability, alt text, i18n strings, localization, translation.

8 Updated 3 days ago
martinholovsky