Your team keeps its own bar without forking the rules. Add an override file under .vois/teams and the editor hook checks animation timing, start and press scale, the spacing grid, selector nesting, and icon stroke and size against your numbers, and an override can only tighten a rule.
Some problems only show up in a browser, like a missing focus ring or an animation that ignores reduced motion. Turn on the opt-in rendered pass and list your screens in vois-render.json: it opens them in Chromium, reports what it found and what it couldn't check, and never edits your project.
You can tell a rule a tool enforces from one that needs your eyes. Each rule is marked detector, spec, rendered or judgment. Focus visibility and text contrast are marked rendered, because they depend on a real page.
You see what a redesign has to cover before it begins. The router lists each route and which of its default, empty, loading and error states exist, and says what it couldn't find. It only reads, it doesn't change anything.
Buttons, labels and icons now change state the same way everywhere. A twelve-step test says when a change should morph, travel or stay still. Five new motion rules keep morphs inside one duration token, and righter approves a label pair before a label morphs.
Hand-built stand-ins are easy to miss in review. Nine advisory checks flag markup that does a component's job without the component, like a raw button with its own focus ring, window.confirm, or title used as a tooltip.
Copy won't quietly commit you to something nobody approved. Times, guarantees, prices, legal terms and compliance claims only appear if your team supplied them. Where one is missing, righter writes copy that makes no promise and flags the gap.
Landing pages stop borrowing app rules that don't fit them. Eight new rules cover display type and section spacing, righter caps each slot (a hero headline is 7 words), and the router has a Marketing work type.
Sticky headers that don't stick are a common bug, and now there's a check for the usual cause. Nineteen rules cover who owns the scroll, sticky headers and columns, scrollbars and accessibility. A check flags overflow settings that stop a header from sticking.
Picking the right chart is now a decision tree, not a guess. It has 114 rules, 48 chart forms and six dashboard templates, and the router sends any chart or dashboard request to it.
Every read and write now runs through row-level security enforced directly in Postgres — one less way a scoping bug could ever leak data across projects.
Pulling a token like color/brand/primary into Figma no longer flattens it into one name — nested groups come through intact.
Syncing components from a connected repo no longer leaves the preview empty — synced components show up right away.
Fixed layout and contrast issues across the dashboard in both themes, so numbers and charts stay readable no matter which theme you're in.
Everyone still gets the full standard set for patterns, components, tokens, and copy. Pro plans additionally unlock orchestration skills that route work across the whole chain automatically.