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 - `data/rhetorical-devices.json` — literary/rhetorical devices (metaphor, personification, epithet, anaphora, etc.) for copy that's allowed to have personality — marketing surfaces, taglines, empty states, feature names. Not for error messages or system copy. - `scripts/ari.mjs` — computes ARI, grade level, and word/character/sentence counts exactly. Run it instead of calculating Reading Metrics by hand when Node is available: `node scripts/ari.mjs "copy text"` or `node scripts/ari.mjs --before "..." --after "..."`. Every numbered principle below and every rule in Error...