ss-copy
FeaturedGenerate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone
Install
Quality Score: 95/100
Skill Content
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
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.
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 -...
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.