From nickcrew-claude-ctx-plugin
Crafts production-ready UI microcopy: button labels, error messages, tooltips, empty states, onboarding flows, and confirmation dialogs. For in-product text only.
npx claudepluginhub nickcrew/claude-cortexThis skill uses the workspace's default tool permissions.
This skill helps you craft clear, helpful, and human UI text that guides users through your product without friction. UX writing is not marketing copy—it lives inside the product and its job is to reduce confusion, build trust, and move users toward success. Good microcopy is invisible when it works and painfully obvious when it doesn't. This skill covers the full spectrum of in-product text: b...
Writes clear UI copy for microcopy, error messages, empty states, CTAs, onboarding, and confirmations with voice, tone, and best practices.
Writes and reviews UX copy for microcopy, error messages, empty states, CTAs, confirmations, tooltips, loading states, and onboarding. Use /ux-copy with context or auto-triggers on copy queries.
Generates UX microcopy in StyleSeed's Toss-inspired voice for buttons, empty states, errors, toasts, confirmations, and form guidance. Useful for consistent, casual-polite UI text.
Share bugs, ideas, or general feedback.
This skill helps you craft clear, helpful, and human UI text that guides users through your product without friction. UX writing is not marketing copy—it lives inside the product and its job is to reduce confusion, build trust, and move users toward success. Good microcopy is invisible when it works and painfully obvious when it doesn't. This skill covers the full spectrum of in-product text: button labels, error messages, empty states, tooltips, onboarding flows, confirmation dialogs, form helper text, and success messages. The output is production-ready copy, not placeholder text.
copywriter skill instead)technical-writer skill instead)| Task | Approach |
|---|---|
| Button labels | Verb + noun: "Save draft", "Delete account". Never "OK" or "Click here" |
| Error messages | What happened + why + how to fix: "Password too short — use at least 8 characters" |
| Empty states | Explain the blank, then invite action: "No projects yet. Start your first one." |
| Tooltips | One sentence max. Answer "what does this do?" not "why does this exist?" |
| Onboarding | Progressive disclosure: show the next step, not every step at once |
| Destructive actions | Name the consequence explicitly: "Delete project" not "Confirm" |
| Success messages | Confirm the action, optionally suggest the next step |
| Tone | Match the product voice; default to warm, direct, and plain English |
Identify the UI element and context. Determine exactly what element needs copy (button, error, tooltip, etc.), where it appears in the user journey, and who the user is at that moment. A user mid-checkout needs different language than a new signup exploring features.
Define the job of the text. Every piece of microcopy does exactly one job: inform, instruct, reassure, warn, or motivate. Name the job before you write a single word. Copy that tries to do two jobs usually does neither well.
Write in plain language. Use the simplest word that does the job. "Start" over "Initiate". "Delete" over "Remove permanently". Aim for a reading level your least technical user can parse at a glance—UI text is read in seconds, not minutes.
Apply the error message formula for all error states. Structure: (1) what happened in plain terms, (2) why it happened if helpful, (3) what the user can do next. Never blame the user ("You entered an invalid email") — be neutral or take system responsibility ("That email address isn't valid — check for typos and try again").
Shorten ruthlessly. Count your words, then cut 30%. Every word costs attention. Button labels should be 1–3 words. Tooltips: one sentence. Error messages: two sentences max. If a concept needs more than that, the UI probably needs redesign, not more copy.
Check consistency. Use the same verb for the same action throughout the product. If the nav says "Sign in", the button must not say "Log in". Inconsistency erodes trust faster than bad copy does.
Test against your voice and tone guide. If the brand is warm and conversational, "Oops, something went wrong" fits. If it's enterprise and formal, it doesn't. When in doubt, default to neutral and direct.
Write variants and compare. Generate 3 options for any important piece of copy, then evaluate against: clarity, brevity, brand tone, and whether it reduces or increases user anxiety.
Input: "Write error messages for a sign-up form. Fields: email, password (min 8 chars, must include a number), username (3–20 chars, letters and numbers only). Tone: friendly, modern SaaS."
Output:
| Trigger | Message |
|---|---|
| Empty on submit | Enter your email address to continue. |
| Invalid format | That doesn't look like an email address — check for typos. |
| Already registered | An account with this email already exists. [Sign in instead?] |
| Trigger | Message |
|---|---|
| Empty on submit | Choose a password to secure your account. |
| Too short | Password must be at least 8 characters. |
| No number | Add at least one number to strengthen your password. |
| Confirmed password mismatch | These passwords don't match — give it another try. |
| Trigger | Message |
|---|---|
| Too short | Username must be at least 3 characters. |
| Too long | Keep your username under 20 characters. |
| Invalid characters | Usernames can only contain letters and numbers. |
| Already taken | That username is taken — try adding a number or your initial. |
You're all set, [Name]! Your account is ready. Let's get started. → Go to dashboard
Input: "Write empty state copy for a project management app. States needed: no projects, no tasks in a project, no team members. Tone: encouraging, startup-friendly."
Output:
Heading: Your workspace is ready. Body: Projects live here. Create your first one to start organizing work, tracking tasks, and collaborating with your team. Button: Create project
Heading: Nothing here yet — that's about to change. Body: Add your first task to kick things off. Break your project into steps and start making progress. Button: Add task
Heading: You're working solo — for now. Body: Invite your team to collaborate, assign tasks, and move faster together. Button: Invite people Secondary link: Learn how sharing works →
Input: "Write a confirmation dialog for permanently deleting a user account. The action cannot be undone. Tone: serious but not alarming."
Output:
Delete your account?
This will permanently delete your account, all your projects, and your data. This can't be undone.
Design note: The cancel action should be the visually prominent button. The destructive action should be secondary in visual weight but clearly labeled.