Menu
Write effective UX microcopy for buttons, forms, error messages, tooltips, and onboarding flows. Use when improving user interface text.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Design, execute, and analyze A/B tests across marketing channels. Use when running experiments on landing pages, emails, ads, or features.
Marketing attribution modeling to understand channel contribution and optimize spend. Use when measuring marketing effectiveness or allocating budget.
Design marketing dashboards and reports for executives, teams, and campaigns. Use when building reporting systems or presenting data.
Perform cohort analysis to understand customer behavior, retention, and lifetime value over time. Use when analyzing retention, LTV, or user behavior patterns.
Create effective marketing reports and presentations that drive decisions. Use when preparing weekly, monthly, or quarterly marketing reports.
Design brand architecture for multi-product or multi-brand organizations. Use when managing brand portfolios or launching sub-brands.
Based on SOC occupation classification
| name | microcopy-ux |
| description | Write effective UX microcopy for buttons, forms, error messages, tooltips, and onboarding flows. Use when improving user interface text. |
| origin | ECM |
Use this skill when writing or reviewing interface text: button labels, form fields, error messages, success states, empty states, loading states, tooltips, onboarding flows, confirmation dialogs, notification copy, settings descriptions, or any text that helps users navigate and complete tasks within a product.
The user is trying to complete a task, not admire your writing. Every word should reduce friction.
When things go wrong, help the user fix the problem. Never imply it's their fault.
Tell users what will happen before, during, and after their action.
The tone should match how the user feels at that point in the experience.
Vague copy creates anxiety. Specific copy builds confidence.
Buttons are the primary way users take action. Every button label should answer: "What happens when I click this?"
| Context | Bad | Good |
|---|---|---|
| Signup form | Submit | Create My Account |
| File upload | OK | Upload File |
| Delete confirmation | Yes | Delete Project |
| Newsletter | Subscribe | Get Weekly Tips |
| Checkout | Continue | Place Order |
| Settings change | Save | Save Changes |
| Cancel subscription | Confirm | Cancel My Subscription |
| Search filter | Apply | Show Results |
Use for constraints, format requirements, or reassurance:
Full name
[ ]
Work email
[e.g., sarah@company.com]
We'll send your login details here.
Password
[ ]
At least 8 characters, one uppercase, one number.
Company name (optional)
[ ]
Error messages are the most important microcopy in your product. They occur at the user's most frustrated moment.
What happened + Why it happened + How to fix it
| Situation | Bad | Good |
|---|---|---|
| Invalid email | Error: Invalid input | Please enter a valid email address (e.g., name@company.com) |
| Password too short | Password error | Your password needs at least 8 characters. You're 2 short. |
| Server error | Error 500 | Something went wrong on our end. Please try again in a few minutes. If this persists, contact support@example.com. |
| File too large | Upload failed | This file is 25MB. The maximum size is 10MB. Try compressing it or choosing a smaller file. |
| Duplicate entry | Error: Duplicate | An account with this email already exists. Try signing in or use a different email. |
| Network error | Error | You appear to be offline. Check your connection and try again. |
| Permission denied | Access denied | You don't have permission to view this page. Ask your team admin to grant you access. |
| Rate limited | Error | You've made too many requests. Please wait 30 seconds and try again. |
Equally important as errors — success messages confirm the action and guide the next step.
Confirm what happened + What to expect next + [Next action]
Empty states appear when there's no content to display. They're an opportunity to guide the user, not a dead end.
Acknowledge the emptiness + Explain the value + Provide a clear action
No projects yet:
You don't have any projects yet. Projects help you organize your work and collaborate with your team. [Create Your First Project]
No search results:
No results for "marketing automation" Try a different search term or [browse all integrations].
Empty inbox:
You're all caught up. When you receive new messages, they'll appear here.
No data yet:
No data to display yet. Once your campaign has been running for 24 hours, you'll start seeing performance metrics here.
Welcome to [Product], [Name].
Let's get you set up in 3 quick steps:
1. Connect your [data source]
2. Set your [key preferences]
3. Invite your team
This takes about 5 minutes.
[Let's Go] [I'll do this later]
[Feature Name]
[One sentence explaining what it does and why you'd use it]
[Optional: "Try it now" link]
Example:
Smart Scheduling
Automatically find the best time to send emails based on when
your contacts are most active.
[Set up Smart Scheduling]
Confirmation dialogs protect users from destructive actions. They must be clear about consequences.
Delete confirmation:
Delete "Q4 Marketing Campaign"? This will permanently delete the campaign and all associated assets. This action cannot be undone. [Cancel] [Delete Campaign]
Unsaved changes:
You have unsaved changes If you leave this page, your changes will be lost. [Discard Changes] [Save and Leave] [Stay on Page]
Subscription cancellation:
Cancel your Pro subscription? Your subscription will remain active until March 31, 2026. After that, you'll lose access to advanced analytics, custom reports, and priority support. [Keep My Subscription] [Cancel Subscription]
All microcopy in a product should feel like it comes from the same person. Create a microcopy style guide:
| Dimension | Our Position | Example |
|---|---|---|
| Formal ←→ Casual | Slightly casual | "Got it!" not "Acknowledged." |
| Serious ←→ Playful | Mostly serious | Light touch in celebrations, serious in errors |
| Technical ←→ Simple | Simple first | "Your file is too large" not "413 Payload Too Large" |
| Detailed ←→ Minimal | Minimal with escape hatches | Short text + "Learn more" links for details |
| Use | Avoid |
|---|---|
| "Please try again" | "Error" (alone) |
| "Something went wrong" | "Fatal exception" |
| "We couldn't..." | "Failed to..." |
| "Learn more" | "Click here" |
| "Got it" | "OK" / "Dismiss" |
| "Undo" | "Revert changes" |