Read REFERENCE.md for tone, capitalization, budgets, and examples. State one useful point per sentence. Cut filler and repetition. Preserve safety, limits, uncertainty, and accessible labels. Use project glossary and canonical product names; GLOSSARY.md is product-specific.
Write
Draft the shortest accurate string per element. Check the whole view. Make only requested changes. Flag unverified facts; never invent behavior, permissions, causes, or recovery. Do not imply human approval.
Review
Read changed strings in context. Give location, exact quote, named pattern, rewrite/removal. Relocate useful facts. A clean review names files read and distinct UI strings checked. Report missing context; do not claim visual checks from source. Review does not edit.
Scope and checks
Include TSX/JSX, navigation, i18n, and UI around chat. Exclude prose documentation, generated reference descriptions, and conversational replies. Explicit project rules win.
scripts/ux-copy-context.sh injects this entrypoint for
UI source and translation paths through a configured PreToolUse hook.
Project instructions cover hosts without hooks. Setup is separate from writing;
change host configuration only when requested. Regex checks do not judge tone.
Escapes need reasons: // allow: ux-copy [reason], <!-- allow: prose-style [reason] -->.
Tone evals: evals/RUBRIC.md. Hook passes do not prove tone.
Copied from malinskibeniamin/skills.
