Voice and tone
Write clear interface copy
Use words that help people make decisions and complete tasks. These guidelines cover labels, instructions, feedback, and the moments when something goes wrong.
Core principles
Write for the task at hand
State what happened or what the person can do, then give the next step.
Start with what matters
Lead with the outcome or problem, then the action the person can take.
Payment failed. Check your card details and try again.
We were unable to complete your request.
Use everyday language
Use familiar words and natural sentence structure. Skip jargon, slang, and forced friendliness.
Where should we send the receipt?
Specify receipt delivery destination.
Keep enough context
Use the fewest words that preserve meaning and courtesy.
Save changes before closing?
Unsaved changes detected. Confirm whether to proceed with closure.
Voice and tone
Keep the voice familiar and adapt the tone
Stardwst's voice is clear, calm, considerate, and practical. Keep routine actions brief, failures specific, and sensitive moments restrained. Do not use jokes or promotional language in errors, or promise behavior the product cannot support.
| Context | Aim | Example |
|---|---|---|
| Routine | Direct and neutral | Choose a delivery address. |
| In progress | Reassuring and factual | Your report is still processing. You can leave this page. |
| Success | Warm and brief | Your changes are saved. |
| Error | Calm and specific | That link has expired. Request a new one to continue. |
| Sensitive | Restrained and considerate | Your access has ended. Contact an administrator if this seems wrong. |
Writing mechanics
Use familiar, consistent mechanics
Speak to the user
Use "you" and "your" for guidance and ownership. Use "we" only when it is helpful to explain what the team or product is doing. Reserve "I" for a statement the user makes, such as consent.
Prefer active voice
Name who acts when it helps. Use passive voice when the actor is unknown, unimportant, or would unfairly blame the user.
Use sentence case
Capitalize the first word and proper nouns. Avoid turning ordinary features and actions into branded names.
Use natural contractions
"You'll" and "can't" often sound natural and save space. Avoid contractions that could be unfamiliar or ambiguous.
Punctuate short copy simply
Use periods for full sentences and question marks for questions. Leave periods off short button labels and headings. Use exclamation points sparingly.
Write for translation and assistive technology
Spell out uncommon acronyms, avoid idioms, and use a control's label instead of its position or color. Keep variables in complete messages instead of joining sentence fragments. Leave room for longer names, dates, and translated text.
Interface patterns
Give each message one clear job
Describe the result
Start with the result: "Save changes" or "Send invite". Repeat the label when the action has the same result.
Help the user recover
Name the problem, then give one next step. Explain the cause only when it is known and helps recovery: "That link has expired. Request a new one to continue."
Explain the absence
Say whether this is a first visit or an empty search. "No projects yet. Create a project to get started." "No results. Try a different search term."
Name the consequence
Name the item and consequence before the action: "Delete this project? You cannot undo this." Use "Delete project" for the confirming button.
Before publishing
Read it once as the user
- 01Is the user's goal or concern clear?
- 02Does the most important information come first?
- 03Is the next step clear, and does every promise match the product?
- 04Can any word be removed without losing meaning?
- 05Does the tone fit the situation?
- 06Will the message still work when translated, resized, or read aloud?