with the skill
## UX Copy: Delete Workspace Confirmation
### Recommended Copy
**Title**: Delete "Northwind Ops"?
**Body**: This will permanently delete all 14 projects and their files for all 6 members. This can't be undone.
**Confirmation input** (optional, recommended for this level of severity): Type the workspace name to confirm: `Northwind Ops`
**Buttons**: [Delete workspace] [Keep workspace]
- "Delete workspace" is styled as a destructive action (e.g., red) and stays disabled until the name is typed, if you use the input.
- "Keep workspace" is the default/safe option.
### Alternatives
| Option | Copy | Tone | Best For |
|--------|------|------|----------|
| A | **Delete "Northwind Ops"?** This permanently deletes 14 projects and all files for 6 members. This can't be undone. [Delete workspace] [Keep workspace] | Direct, neutral | Default; clear and brief |
Show the rest (25 more lines)
| B | **Delete "Northwind Ops" for everyone?** All 14 projects and their files will be permanently removed for you and 5 other members. You can't recover them. [Delete workspace] [Cancel] | Serious, emphasizes shared impact | Teams where members often don't realize deletion affects others |
| C | **This will permanently delete "Northwind Ops"** Everything inside, including 14 projects and all files, will be erased for all 6 members. Consider exporting anything you need first. [Export data] [Delete workspace] [Keep workspace] | Cautious, helpful | If you offer export; gives users an alternative path before they commit |
### Rationale
- **Names the target.** "Are you sure?" doesn't say what's being deleted. Including the workspace name helps people who manage several workspaces avoid deleting the wrong one.
- **States the real scope.** The original copy leaves out that 14 projects, their files, and 6 people are affected. Concrete numbers make the consequences easier to grasp than a generic warning.
- **Says "for everyone."** Deleting affects other members, not just the owner. This is the fact most easily overlooked, so it's in the body.
- **Uses action-labeled buttons.** "OK / Cancel" is ambiguous, especially when "Cancel" could be read as canceling the deletion or canceling the dialog. "Delete workspace / Keep workspace" makes each outcome explicit.
- **Adds friction in proportion to severity.** Typing the name is a common pattern for irreversible, high-impact actions. If it feels heavy for your product, Option A works without it.
- **Plain language.** "Can't be undone" is more conversational than "cannot be reversed."
### Additional Notes
- **Owner-only permission:** Non-owners shouldn't see this dialog. If they try to delete, show a separate message, e.g., *"Only workspace owners can delete a workspace. Contact an owner to make this change."*
- **Pluralization:** Handle singular cases ("1 project", "1 member"). If the owner is the only member, drop "for all members": *"This will permanently delete all 14 projects and their files."*
- **Notification:** If members aren't warned beforehand, consider noting that, or telling the owner whether members will be notified.
### Localization Notes
- Keep the workspace name in quotes and as a variable. Some languages need different quote styles or word order around it.
- Use ICU or plural-aware strings for "{count} projects" and "{count} members." Many languages have more than two plural forms.
- "Keep workspace" and "Delete workspace" may expand 30-40% in German or French. Allow button width to flex or wrap.
- Avoid translating "can't be undone" word-for-word in languages where it sounds overly technical. Use the natural phrase for "this is permanent."
- The type-to-confirm input should match the name exactly as entered, regardless of the interface language.