$npx -y skills add rlaope/oh-my-hermes --skill design-quality-gate[omh] Hermes Design Quality Gate workflow: enforce superior content, design, layout, publishing, and visual QA gates.
| 1 | # Design Quality Gate |
| 2 | |
| 3 | This is a Hermes-native `design-quality-gate` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `design-quality-gate` makes high-stakes visual deliverables premium and trustworthy by treating taste, content, layout, accessibility, and render QA as first-class evidence. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - Basic image prompt card only; use `img-summary`. |
| 12 | - Ordinary file packaging/export plan only; use `materials-package` or `deliverable-package`. |
| 13 | - Pure backend, CLI, data, or text-only research with no visual surface. |
| 14 | - The user asks to claim deployment, export, publication, or visual QA without evidence. |
| 15 | |
| 16 | ## Examples |
| 17 | |
| 18 | Good example: |
| 19 | |
| 20 | - Prompt: design-quality-gate make this landing page and deck premium and verified. |
| 21 | - 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. |
| 22 | - Why: The request asks for superior visual quality and publishing readiness. |
| 23 | |
| 24 | Bad example: |
| 25 | |
| 26 | - Prompt: design-quality-gate say the PDF and website look amazing because the plan says so. |
| 27 | - Expected behavior: Require rendered PDF/page screenshots or mark visual QA as not_observed. |
| 28 | - Why: A quality brief is not render, visual QA, export, deployment, or delivery evidence. |
| 29 | |
| 30 | ## Completion Checklist |
| 31 | |
| 32 | - The surface, audience, source content, baseline/reference bar, and artifact type are named. |
| 33 | - The comparative_quality_rubric/v1 explains how the result must beat ordinary output. |
| 34 | - The surface_quality_matrix/v1 covers web, deck/PPT, PDF/poster, accessibility, and CJK-relevant checks as applicable. |
| 35 | - Prepared quality gates, generated artifacts, visual QA, export, publication, approval, and delivery remain separate states. |
| 36 | - The next action names whether to revise content, prepare implementation/export handoff, gather render evidence, or report blocked QA. |
| 37 | |
| 38 | ## Recovery Notes |
| 39 | |
| 40 | - If the baseline or references are missing, prepare the gate with an explicit comparative-quality gap instead of calling the result premium. |
| 41 | - If render QA is unavailable, keep PASS unavailable and ask for the smallest screenshot, deck/PDF render, or operator observation that proves the target surface. |
| 42 | |
| 43 | ## OMH Context Rail |
| 44 | |
| 45 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 46 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 47 | - Current lane: **Materials and visual summaries** (`design-orchestration`, `design-quality-gate`, `frontend`, `accessibility-audit`, `visual-qa`, `content-operator`, `media-input-operator`, `materials-package`, `+3 more`) - web, accessibility, visual QA, files, and packages. |
| 48 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 49 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 50 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 51 | - Coverage: Every generated workflow skill carries this rail. |
| 52 | - Normal users talk to Hermes; OMH CLI is infra. |
| 53 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 54 | |
| 55 | ## Use When |
| 56 | |
| 57 | Use when web UI, decks, PDFs, posters, or visual packages must beat ordinary output on content, taste, layout, accessibility, and render QA. |
| 58 | |
| 59 | Strong routing signals: `design-quality-gate`, `design quality gate`, `ui ux pro max`, `design pro max`, `frontend pro max`, `visual qa pro`, `premium design`, `high quality design`, `beautiful website`, `frontend publishing`, `publishing quality`, `layout validation`, `ppt design quality`, `pdf design quality`, `웹사이트 디자인`, `프론트엔드 퍼블리싱`, `레이아웃 검증`, `더 뛰어나게`, `고퀄` |
| 60 | |
| 61 | ## Catalog Metadata |
| 62 | |
| 63 | Category: `materials` |
| 64 | Phase: `design-quality-gate` |
| 65 | Hermes role: `operator` |
| 66 | Quality tier: `design-pro-gated` |
| 67 | |
| 68 | Quality bar: |
| 69 | |
| 70 | - Define superior design quality with references, audience, hierarchy, style, and measurable QA gates. |
| 71 | - State why the result should be better than ordinary output, including content depth, visual hierarchy, spacing, typography, and interaction or export polish. |
| 72 | - Review content accuracy and hierarchy before visual polish. |
| 73 | - Use design-system/reference rules for we |