Generate UX Copy for UI States

UX Copy is part of StyleSeed and generates concise product copy for common UI states, following a Toss-inspired tone: casual but polite, direct, active, and specific enough to help the user recover or proceed. Tone rules are explicit - casual but polite, active voice over passive, positive framing where it stays honest, plain language instead of internal jargon, and concise wording where every word earns its place.

Use it when you need button labels, helper text, toasts, empty states, or error messages, when a feature has functional UI but weak or robotic wording, when you want consistent product voice across a flow, or when confirmation dialogs and state feedback need better phrasing. It is a copywriting skill, not a UX-structure fix - if a flow itself is broken, better copy alone won't solve it, and the skill is expected to flag that distinction rather than paper over it.

Common patterns per UI surface: buttons use a short action verb plus object; empty states open with a friendly observation and then suggest the next action; errors explain what happened in user-facing language and what to do next, never surfacing raw internal error strings; toasts confirm the result quickly and add an undo action for reversible destructive behavior; forms use clear labels, useful placeholders, specific helper text, and corrective error messages; confirmation dialogs state the action in plain language and explain the consequence when the decision is risky or irreversible. Output is the requested microcopy grouped by UI surface, notes on tone or localization considerations where relevant, and a flag for any place where the UX likely needs a structural fix in addition to better copy.

Built for the StyleSeed design system's Toss seed (bitjaru/styleseed), applying its specific tone guidelines rather than generic UX-writing best practices - the voice is calibrated to that product's casual-but-polite register.

Product and frontend teams working in a StyleSeed Toss-based codebase who need consistent, purposeful microcopy across buttons, errors, empty states, and dialogs instead of robotic or generic labels like plain "Submit" or "OK" - best practice is to make the next action obvious, blame the system rather than the user when something fails, and keep error and empty states useful even without surrounding visual context.