ship-quality-gate

Ship Quality Gate

Design advice is cheap and unfalsifiable. The gate is the other half of the job: ten auditors that hand back findings with a rule id, a severity, the document the rule comes from, and — where the finding belongs to a place — a file and a line. Run them before anyone argues about anything.

Two qualifications on that sentence, because they change how you read the output. Seven of the ten read a real repository; design_lint, audit_ux_copy and audit_ethical_design read one snippet you paste in and have no notion of a project at all — the table below says so per tool. (Two separate corrections sit behind that sentence, and the first was not caused by the second: this file's opening once counted design_lint among the auditors that read a repository, which was fixed on the round that wrote up its snippet-only scope; audit_ux_copy joined the same camp later, on the round that gave it a notVisible list of its own. audit_android_ui later joined the directory-only camp beside audit_apple_ui. audit_ethical_design joined the snippet-only camp in 0.29.0.) And not every finding carries a file:line. design_lint, audit_ux_copy and audit_ethical_design findings carry a line and no file, because there is no file — audit_ux_copy's line marks a position in the pasted text, not a path. More importantly, an absence rule — no llms.txt, no sitemap referenced in robots.txt, no title, no canonical, no entitlements file among the surfaces read, no values-night/ beside a day theme — is a fact about a file that does not exist and so was never read; it names no file by construction. Some project-scope findings in audit_security, audit_apple_ui and audit_android_ui are the same shape.

The trade they make is the whole thing to understand. Each one reports what was authored, not what was measured. They load no page, render nothing, time nothing, and make no request to your site. Every finding is a fact about text — text that was read, or, for an absence rule, text that was looked for across the surfaces named in the finding and not found. That is why they are deterministic, offline and fast — and it is exactly what bounds them.

These ship in the SaglitzDesign MCP (npx saglitzdesign-mcp). The rules behind them live in the base: get_design_doc("web-security-headers"), get_design_doc("frontend-attack-surface"), seo_geo_guide, get_design_doc("ai-default-aesthetic"), get_design_doc("ethical-design"), get_design_doc("apple-shipping-readiness"), get_design_doc("android-app-design"), get_design_doc("material-3"), get_design_doc("ux-writing"). For what these tools structurally cannot reach, pair them with measure_screenshot (the render), audit_accessibility (contrast ratios and target sizes) and the /saglitzdesign:design_review workflow.