tastecheck-passlisted

# TasteCheck Pass Give finished frontend work an honest **SHIP** or **HOLD** decision. Check the real artifact, put verdict first, and turn failures into actions. Checkmarks are not execution evidence. ## User-facing answer Lead with **SHIP** or **HOLD**, blockers, passed scope, fastest path, and evidence links. Use **SHIP** only when every applicable row passes. Use **HOLD** when a required check fails, could not run, lacks artifact, or lacks evidence; never hide verdict in a table. ## Evidence Create one authoritative row per applicable check with `skill`, `check_id`, `status`, `reason`, `remediation`, `evidence`, and `provenance`. `n/a` means absent subject, never “not tested.” Keep measurements/skip reasons in rows; link them from the brief. ## Pipeline 1. Direction — `design-system-interview` (new) or `improve-existing-website` (existing). 2. Foundations — `color-system`, `web-typography`, `spacing-system`, `theming`. 3. Structure/behavior — `responsive-layout`, `component-states`, `form-ux`, `empty-states`. 4. Surface — `micro-motion`, `data-viz`, `art-direction` where applicable. 5. Verification/audit — `a11y-pass`, `cognitive-a11y`, `i18n-ready` if multilingual, `deslop-ui` against spec, `humanize-copy`. 6. Gate — this skill. Only absent subjects skip; direction, foundations, structure, accessibility, and against-spec `deslop-ui` remain required. ## Gate run 1. Confirm `DESIGN-SYSTEM.md` (or approved inferred-system statement) and built-to-spec status;