modul 5 — quality and anti-slop
your own quality gate
Five checks exist on your project now. The capstone wires them into one pipeline, ordered cheap to expensive, and proves it works by feeding it a planted bug.
~3 min read · ~10 min with the exercise · v1.1 · verified: 2026-07-15
from checks to a gate
The module handed you five checks: tests on the money paths, a design law, copy greps, axe, and Lighthouse budgets. Held in your head, they decay; the first deadline skips one, the second skips three. A quality gate is the same checks with the discretion removed: they run on every change, in a fixed order, and red means stop.
Order them by cost, cheapest first, so a five-second failure never waits behind a five-minute audit: lint and types, then tests, then the copy greps, then review, then the a11y and speed budgets in CI.