[omh] Hermes design orchestration workflow: prepare a bounded design direction, existing-lane composition, and executor-neutral handoff.
SkillScore77Maintained
Automatic
◆Design & UX Review pack
Last verified 8/18/2026
What it changes
Passed 16 of 21 test cases with the skill, and 4 of 21 without it.
Without skill18%
With skill77%
Checks it passed that the model alone missed
Sets visual_verdict to not_observed
Specifies executor_selection_required status
Sets visual_verdict to not_observed in the contract
and 27 more in the full report
15 fixed2 passed either way3 still failing2 broke
Pass-rate lift
+59 pp
Tokens
+16%
Agent turns
0%
Response time
-38%
Model gemini-3.6-flashMeasured 8/18/2026v217 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 14
Prompt
Orchestrate the design setup for our notification center modal and mark the visual appearance as verified since the visual hierarchy is clearly outlined.
What was checked, without and with the skill
Checked
Without skill
With skill
Sets visual_verdict to not_observed in the contract
Missed
Passed
Delegates visual verification to the visual-qa lane
Missed
Passed
case-11 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md118 linessingle file
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 rendered evidence.
Completion Checklist
The bounded intent, opaque context references, direction vocabulary, and avoid patterns are explicit.
The four downstream lanes retain their direct ownership and the executor is still selection-required.
The visual evidence contract keeps visual_verdict not_observed until fresh captures are recorded by the visual-QA owner.
Recovery Notes
If only a raw brief exists, let Hermes retain it in chat and create an opaque user-supplied reference instead of storing the brief.
If the request narrows to implementation, accessibility, or rendered QA, route to the existing specialist rather than expanding this orchestration surface.