Oh My Hermes

Design orchestration

Give Hermes the design job. Keep every owner and proof boundary visible.

OMH turns a broad design request into a prepared direction, the relevant specialist lanes, an executor-neutral handoff, and the evidence still required before any visual verdict.

prepared design_orchestration/v1 Implementation and rendered proof remain separate.
Hermes design request local contract prepared_not_observed

01 / Intent

Operator workflow screen for managing a high-risk release.

Audience
Operator
Primary task
Manage
Platform
Web
Mode
Redesign

02 / Direction

Deliberate choices, not “make it premium.”

HierarchyTask first
PaletteRestrained neutral
TypeSystem sans
LayoutSplit panel
SignatureEvidence rail
AvoidGlass, card wall

03 / Compose the right lanes

OMH coordinates specialists. It does not blur them.

Each lane has a narrow responsibility. Hermes retains the brief and narration; the selected executor implements; observed visual evidence remains with visual QA.

  1. 01
    Design quality gate

    Comparative quality bar, content hierarchy, and baseline.

    prepared
  2. 02
    Frontend

    Design system, route/state matrix, and implementation handoff.

    prepared
  3. 03
    Accessibility audit

    WCAG, keyboard, focus, and semantic review conditions.

    required
  4. 04
    Visual QA

    Fresh desktop/mobile captures and a recorded verdict.

    not observed

04 / Handoff and evidence

Ready to guide the work. Not allowed to claim the work is done.

The contract gives a selected executor clear context without selecting, dispatching, or impersonating one. The evidence rail keeps the remaining proof visible after implementation begins.

preparedExecutor-neutral handoff

Executor selection required.

not observedFresh render capture

After the last UI change.

not observedVisual verdict

Desktop, mobile, default, empty, error, focus.