Design Quality Gate

This is an OMH design-quality-gate workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

Why This Exists

design-quality-gate makes high-stakes visual deliverables premium and trustworthy by treating taste, content, layout, accessibility, and render QA as first-class evidence.

Do Not Use When

• Basic image prompt card only; use omh-image-cards.
• The artifact is a throwaway probe whose quality is irrelevant to the decision it answers; use omh-decision-prototype.
• Ordinary file packaging/export plan only; use omh-materials-package or omh-deliverable-package.
• Pure backend, CLI, data, or text-only research with no visual surface.
• The user asks to claim deployment, export, publication, or visual QA without evidence.

Examples

Good example:

• Prompt: design-quality-gate make this landing page and deck premium and verified.
• Expected behavior: Prepare design_quality_gate/v1 with references, comparative_quality_rubric/v1, surface_quality_matrix/v1, hierarchy, layout plan, visual QA checklist, route, and evidence boundaries.
• Why: The request asks for superior visual quality and publishing readiness.

Bad example:

• Prompt: design-quality-gate say the PDF and website look amazing because the plan says so.
• Expected behavior: Require rendered PDF/page screenshots or mark visual QA as not_observed.
• Why: A quality brief is not render, visual QA, export, deployment, or delivery evidence.

Completion Checklist