render-sanity
Render Sanity
Why this exists: "Tests pass, dev server boots, console is clean" is a process bar. It's not the same as "the app works." This skill is the missing semantic check between those two — it catches failure modes that render plausibly but are quietly broken.
This skill is not subjective. It does not evaluate visual hierarchy, typography, or polish — those are ux-review's job. It hunts four specific, objectively-verifiable failure modes that ship past every other gate.
Announce at start: "Using render-sanity to click through [N routes] and check for stale data, placeholder text, dead links, and auth dead-ends."
The Four Checks
Each produces concrete file/route/text evidence — not "feels off."
Check 1 — Visible-text smell scan
The app may render. The text it renders may be garbage. For every page in the sitemap, grab document.body.innerText and grep for known smell patterns (lone ?, persistent Loading…, undefined, Couldn't load, repeated generic fallbacks, leaked mock IDs).
The full pattern table — universal smells plus how to derive project-specific patterns from the project's mocks/fixtures/seed files — lives in references/smell-patterns.md. Read it before running this check.