UX copy reviewer that audits interface text against your content guidelines and suggests rewrites
A Claude Project for designers, PMs and content designers: paste UI strings or describe a screen and it reviews buttons, errors, empty states and onboarding text for clarity, consistency and tone, citing your own content guidelines.
Agent in Design by AISkillHub Library
What it does
Interface copy is often written last, by whoever is closest to the code. Small inconsistencies add up: "Remove" on one screen and "Delete" on another, error messages that blame the user, buttons that say "OK" when they should say what happens. This project reviews UI text the way a content designer would, using your guidelines and terminology.
**What it does**
- Accepts UI strings in any form: a list, a JSON or YAML locale file excerpt, a screenshot description, or a pasted flow. - Reviews each string against a checklist: clarity, action-oriented buttons, error messages that say what happened and what to do, consistent terminology, sentence case and punctuation rules, length limits, and inclusive language. - Uses your content guidelines and word list from project knowledge when present, and cites the rule it applies. - Returns a table: original, issue, suggested rewrite, rule. Includes character counts so you can check fit. - Highlights terminology conflicts across the whole set (the same thing called two names).
**When to use it**
- Before handing designs to engineering - Reviewing a pull request that adds new strings - Building or tightening a glossary for a product
**What it will not do**
- It does not test copy with users or predict conversion lift. It applies guidelines; for high-stakes changes, run a test. - It does not rewrite legal, privacy or regulated text (consent wording, terms, medical or financial disclosures). It flags readability issues and sends those to the owner. - It does not translate. It can flag strings that will be hard to localize.
**Example**
| Original | Issue | Rewrite | |---|---|---| | Error: Invalid input | Does not say what is wrong or how to fix it | Enter a date in the format DD/MM/YYYY | | Submit | Generic; does not say what happens | Send invoice | | Are you sure? [OK] [Cancel] | Unclear consequence; OK is ambiguous | Delete this project? This removes all 12 files. [Delete project] [Keep project] |
How to use it
**Set up as a Claude Project** (Projects are available on claude.ai; limits depend on your plan).
1. In Claude, open **Projects** and create a new project named `UX Copy Review`. 2. Open the project's instructions setting (the panel for custom instructions that apply to every chat in the project) and paste the full contents of `assistants/ux-copy-reviewer/instructions.md`. 3. Replace the variables in the pasted text: `{{product_name}}` and `{{case_style}}` (`sentence case` or `title case` for buttons and headings). 4. Add reference material to the project's knowledge area (upload files or paste text): your content style guide, product glossary or word list, and voice and tone notes. If you have none, start with `assistants/ux-copy-reviewer/content-guidelines-template.md`. 5. Start a new chat inside the project. Every chat there uses these instructions and can read the project knowledge.
**Using it:** paste strings and add the context: which screen, what triggers it, and any character limit (for example `button, max 20 characters`). For locale files, paste the key-value pairs; it keeps the keys in its output.
Files
Save each file at the path shown, relative to your project root.