review-copy

# Review copy Score a piece of user-facing copy against `VOICE.md`, fix what fails, then verify the fixes actually landed. The loop exists because a single pass reliably misses things and reliably claims fixes it didn't make. **Target**: `$ARGUMENTS` — a file, a directory of Swift views, a docs page, a PR body, or pasted text. ## Before anything Read `VOICE.md` at the repo root. It is the standard; this skill is only the loop that applies it. If the two ever disagree, `VOICE.md` wins. **Never calibrate against neighbouring strings in this repo.** Most of them were written with AI assistance, so "it matches the file around it" is evidence of nothing. For UI copy, the reference is the macOS System Settings pane that does the same job — read Apple's wording, then write termio's. ## The loop ``` score → fix the failures → re-score to verify → repeat until it holds ``` State lives in a tracker file under the scratchpad so a second pass doesn't re-discover the same issues or trust an unverified claim: **Path**: `<scratchpad>/copy-review-<name>.md` ```markdown # Copy review: [target] | ID | String / line | Issue | Status | Round | | --- | -------------------- | ---------------- | -------------- | ----- | | 1 | Settings.swift:214 | subject is "you" | pending | 1 | | 2 | page.tsx:80 | "seamlessly" | verified-fixed | 1 | | 3 | FileNode.swift:31 | mechanism copy | wont-fix | 2 | ## Rounds ### Round...