Visant Killer

Adversarial UI audit. The screen is the defendant, not the client. Two halves that do not replace each other: the gate (deterministic scripts, binary: AI tell, token, voice, chrome noise) and judgment (you, with the skills loaded), because AI slop survives any linter: the problem is decision, not syntax.

Rule zero (from visant-copy): only the fix of a confirmed defect goes into the file. What passes clean stays untouched, even if it sounds flat. Taste improvements go as a proposal table; the user picks line by line.

A green gate is not a seen screen. A frozen AnimatePresence in a lead form passed six gates. So killer-scan refuses "gate open" without the surface table and the record of having opened the screen.

Where each rule came from: references/cases.md. Stack. The gate reads React JSX. On Vue, Svelte, Astro or HTML it refuses (exit 2): audit by hand, plus the browser scans.

Hard prohibitions (you break them while writing, not reviewing)