ux-copy
FeaturedGenerate UX microcopy in StyleSeed's Toss-inspired voice for buttons, empty states, errors, toasts, confirmations, and form guidance.
Install
Quality Score: 99/100
Skill Content
Details
- Author
- sickn33
- Repository
- sickn33/antigravity-awesome-skills
- Created
- 4 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
ux-copy
Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.
ux-microcopy
This skill provides senior UX writing expertise for crafting user-facing microcopy. It should be used when writing or reviewing UI text such as blank states, error messages, success messages, confirmation dialogs, tooltips, form labels, validation messages, loading states, onboarding text, CTAs, or any frontend component that communicates intention to the user. Also triggers when writing CLI output messages (progress feedback, errors, success confirmations, usage hints). Triggers on user-facing string literals in frontend code, empty state components, error boundaries, toast/notification text, modal copy, placeholder text, and CLI console.log/chalk/ora output messages.
microcopy
Use when writing or reviewing functional UI text: button labels, empty states, tooltips, dialogs, placeholders, loading/progress messages, toasts, inline validation, permission copy, or onboarding steps. Covers interface-copy patterns such as verb-first action labels, acknowledge-explain-guide empty states, one-sentence tooltips, consequence-first confirmations, progressive loading language, and blur/fix validation messages. Do NOT use for marketing persuasion, documentation prose/guide structure, feedback-state staging, or general linguistic rationale behind wording.
ux-writing
Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.
ux-copywriter
Generates bilingual (CZ + EN) UX + conversion copy — runs a structured voice intake, picks the right framework (PAS / AIDA / JTBD / SB7 / Wiebe / Dunford / FAB / BAB), produces hero copy / landing-page sequences / CTAs / microcopy / error messages / onboarding / empty states with hard length budgets, AI-slop blocklist, and CZ-localization linting (tykání-vykání tree, EN→CZ +30% expansion, Smazat/Vymazat/Submit traps, Mozilla CZ typography). Auto-invokes on copy intent — triggers (CZ+EN) "napiš mi text/headline/hero/slogany", "potřebuju copy", "přepiš tlačítka", "lokalizuj UI do CZ", "write copy for", "draft a landing page", "rewrite my hero", "fix my microcopy", or explicit `/copywriter` / `/ux-copywriter`. Grounded in May 2026 research across conversion frameworks, content-design canon (Microsoft / GOV.UK / Apple / Material / Mailchimp / Atlassian / Shopify / Carbon), Podmajersky Voice Chart, and Mozilla CZ Style Guide.