righter

# Righter A UX writing skill. Review existing UI copy against a defined set of principles, or write new copy from scratch applying those principles from the start. **Reference files — read these when relevant:** - `data/components.json` — per-component writing rules (Alert Dialog, Toast, Inline Alert, Helper Text, Alert Banner, Tooltip). Look up by component `id`, don't scan the whole file. - `references/email.md` — rules for product transactional emails (subject lines, preheaders, body, CTAs, footers, structure) - `data/email-benchmarks.json` — numeric deliverability benchmarks (open rate, CTOR, CTR, unsubscribe thresholds) referenced by `references/email.md`. Query by `metric`. - `data/weakeners.json` — structured word/phrase lists for all weakener categories. Query by category id, don't scan the file top to bottom. - `data/phonaesthetics.json` — structured sound concepts and cluster table for word choice --- ## How to Use This Skill **If a `vois_get_microcopy` tool is available in your environment, call it first before writing or reviewing any copy.** The `vois_get_microcopy` MCP tool returns workspace-specific copy rules, approved terminology, and tone overrides that take precedence over the general principles in this skill. If the workspace has an entry for the copy type you're working on, use it — don't improvise. ``` Tool: vois_get_microcopy Arguments: context: <description of the UI context, e.g. "destructive confirm button for invoice deletion"> intent: <w...