HomeCasa Empty, error and loading state microcopy and design
Build an inventory of empty, error, loading and success states for one screen, each with a headline, body text, primary action and accessibility notes ready for your product team. Designed for ChatGPT, Claude, Gemini and Microsoft Copilot. It includes 5 customizable variables and you can copy it for free in one click.
Beginner · Text · Pending editorial review
Prompt
Act as a UX writer and product designer with experience in SaaS interfaces.
Context:
- Product: {{product}}
- Screen or feature: {{screen}}
- User type: {{user}}
- Tone of voice: {{tone}}
- Real errors that can occur: {{errors}}
Deliverables:
1. An inventory of states for the screen: first use (initial empty), no search or filter results, empty after deleting everything, loading, slow loading, connection error, permission error, validation error, server error, success and partial data. Add any others the context requires.
2. For each state: when it appears, headline (max 40 characters), supporting text (max 120), primary action, secondary action if relevant and a visual suggestion (illustration, icon, skeleton).
3. Microcopy rules for this product: say what happened, why and what the user can do; never blame the user; never show only technical codes.
4. Accessibility notes per state: announce content changes with aria-live, manage focus after an error, do not rely on color alone and give illustrations proper alt text.
5. Three variants of the first-use empty state to test with users.
Constraints:
- Do not invent features or product limits; use [FILL IN] when data is missing.
- Keep a consistent {{tone}} tone across all states.
- If it is unclear what the user can do after an error, ask me before writing it.
Format: a table with columns State, Trigger, Headline, Body, Primary action, Secondary action, Visual, Accessibility; then the rules and variants.How to use it
- Name the specific screen and the real errors your system logs. 2. Review the table with engineering to confirm each trigger exists. 3. Copy the strings into your design file or localization system.
Usage example
Product: project management app · Screen: task list · User: team lead · Tone: friendly · Errors: offline, no edit permission.
Sample output
Task list states
| State | Trigger | Headline | Body | Primary action | Secondary | Visual | Accessibility |
|---|---|---|---|---|---|---|---|
| First use | New project | Your tasks will live here | Add the first one and share the work with your team. | Create task | Import list | Empty-list illustration | Empty alt (decorative) |
| No results | Filters match nothing | Nothing matches these filters | Try another status or assignee. | Clear filters | — | Search icon | Announce with aria-live="polite" |
| Offline | Network drops | You're offline | We've saved your changes and will sync them when you're back online. | Try again | — | Cloud-off icon | Don't rely on color alone |
| Session expired | Token expires | Your session timed out | Sign in again to keep going; you won't lose what you were typing. | Sign in | — | Lock icon | Move focus to the button |
| No permission | Read-only user | You can view this project | Ask the project owner for edit access. | Request access | — | Eye icon | Explain why, don't just disable |
| File too large | Attachment over limit | That file is too big | The limit is [FILL IN: real limit]. Try compressing it. | Choose another file | — | Document icon | Tie error to field with aria-describedby |
Microcopy rules
- Say what happened, why, and what the user can do next.
- Never blame the user: "We couldn't…", not "You failed to…"…
Key facts
- Category
- UI/UX design · SaaS apps
- Output type
- Text
- Level
- Beginner
- Designed for
- ChatGPT, Claude, Gemini and Microsoft Copilot
- Verified in
- Pending editorial verification
- Variables
- Product, Screen or feature, User type, Tone of voice and Real errors
- Language
- English
- Price
- Free, no sign-up
- Updated
- Nov 7, 2026
Frequently asked questions
What is the difference between a first-use empty state and a no-results state?
A first-use state should explain the value of the feature and invite the user to create their first item. A no-results state should help them change or clear their search or filters.
Should the error code be shown to the user?
Only as secondary information for support. The main message should be in plain language and say what to do next.
What is this prompt for?
Build an inventory of empty, error, loading and success states for one screen, each with a headline, body text, primary action and accessibility notes ready for your product team.
Which AI tools does it work with?
It is designed for ChatGPT, Claude, Gemini and Microsoft Copilot. We have not verified it in these tools yet, so results may vary between them.
How do I customize the prompt?
Click “Customize” and fill in the variables (Product, Screen or feature, User type, Tone of voice and Real errors). The text updates instantly and you can then copy it in one click. Values are stored only in your browser.
Do I need experience to use it?
No. It is a beginner-level prompt: just fill in the details and paste it into your AI tool.
Is this prompt free?
Yes. Every HomeCasa Prompts prompt is free, with no sign-up or subscription. You can also use them in professional projects.
Can I trust the AI output?
Treat it as a high-quality draft: always check data, figures and important claims before publishing or making decisions.