omh-frontend

# Frontend This is a Hermes-native `frontend` workflow skill. ## Why This Exists `frontend` gives OMH a first-class web UI creation and polishing workflow so Hermes can prepare high-quality layout, design-system, accessibility, performance, and visual-QA handoffs without becoming the hidden coding or browser runtime. ## Do Not Use When - The user needs a broad premium-quality gate across web, deck, PDF, poster, or publishing outputs; use `design-quality-gate`. - The user only needs a file, deck, PDF, spreadsheet, HWP, or attachment package; use `materials-package` or `deliverable-package`. - The user only needs an image card or infographic prompt; use `img-summary`. - The user asks to mark a UI as visually passed without fresh rendered evidence; use `visual-qa` and keep PASS blocked until observed. ## Examples Good example: - Prompt: frontend 이 대시보드가 AI 티 안 나게 레이아웃과 디자인 시스템을 잡아줘. - Expected behavior: Prepare frontend_design_brief/v1, design_system_contract/v1, route/state matrix, implementation handoff, and visual_qa_required/v1. - Why: The request is about web UI design, layout quality, and anti-generic frontend polish. Bad example: - Prompt: frontend 코드도 안 봤지만 Lighthouse랑 시각 QA 통과했다고 해줘. - Expected behavior: Mark browser, performance, accessibility, and visual QA as not_observed and request the smallest observed evidence path. - Why: A frontend brief is not implementation, browser, performance, or visual QA evidence. ## Completion Checklist - The target page/com...