omh-design-orchestration

# Design Orchestration This is a Hermes-native `design-orchestration` workflow skill. ## Why This Exists `design-orchestration` lets Hermes users say that they want design handled without making them manually compose four specialist lanes or confusing preparation with completed visual work. ## Do Not Use When - The request is directly about premium multi-format quality or publishing; use `design-quality-gate`. - The request is directly about frontend implementation, layout, responsive behavior, or a design system; use `frontend`. - The request is directly about WCAG, keyboard, screen-reader, or semantic accessibility; use `accessibility-audit`. - The request is directly about screenshots, visual regression, pixel diff, rendered layout, or a verdict; use `visual-qa`. ## Examples Good example: - Prompt: 디자인 맡겨줘. 기존 프로젝트 맥락을 먼저 보고, 방향과 구현·검증의 다음 단계를 잡아줘. - Expected behavior: Prepare design_orchestration/v1 with opaque context references, deliberate direction, existing-lane composition, executor_selection_required, and not_observed visual evidence requirements. - Why: The request delegates broad design ownership while leaving implementation and observed QA to the appropriate owners. Bad example: - Prompt: design-orchestration already rendered and visually passed the new page. - Expected behavior: Keep rendering and visual PASS not_observed; route the required capture and verdict work to visual-qa. - Why: A prepared orchestration contract cannot create implementation or ...