plugin87 / gate
Run the one-command quality gate and report the real N/N result. Use before claiming any build/review is done.
Step 0 — is the kit here? This skill reads files from the kit. Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING
OnKIT_MISSINGonly the skill folders were installed, which is whatnpx skills adddoes. Say so plainly, point the user atnpx ux-ui-agent-skills initor the plugin install, and stop. Do not guess the
contents of a file you could not open.
Run the full quality gate and report the ACTUAL output — never a remembered or
reasoned number.
Run:
node ${CLAUDE_SKILL_DIR}/../../../scripts/accuracy_report.mjs
(tokens + contrast + spec + no-hardcode + theme-refs + no-emoji +
real-render WCAG + state-aware, light and dark — all-or-nothing).- Report the exact
N/Nline it prints. If it is not fully green:
- List each failing check verbatim.
- Fix the cause (do not suppress the check).
- Re-run until green. Do not announce success between failures.
For any rendered HTML touched this session, also run the pixel-truth checks
the gate cannot prove:node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_states.mjs <file> [--dark]node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_responsive.mjs <file>RENDER-AND-LOOK: screenshot the harness, park the pointer off it, inspect
every state, click each control to confirm the state changed.
Honest scope: these gates prove objective correctness (tokens, a11y, no drift).
They do not prove taste. Pair with node ${CLAUDE_SKILL_DIR}/../../../scripts/taste_audit.mjs + human review;
never claim auto-100% on aesthetics.