oma-design

Scheduling

Goal

Resolve project design intent, select the applicable external design skill, and retain the project's visual contract and verification evidence. DESIGN.md records the design system when the task creates or materially changes it.

Intent signature

• Design system, DESIGN.md, visual direction, redesign, or UI design review.
• Typography, color, layout, motion, accessibility, or component decisions before implementation.

When to use

• Define or revise a visual system or substantial design direction.
• Review an existing UI or refine a chosen visual direction.
• Extract design decisions from existing UI, screenshots, or supplied references.

When NOT to use

• Implement application UI or export framework-specific tokens -> oma-frontend or oma-mobile.
• Plan product scope -> oma-pm; generate an image -> oma-image.
• Review general correctness or security -> oma-qa or oma-security.

Expected inputs

• Requested surface and outcome, existing brand and project facts, and change scope.
• Available DESIGN.md, .design-context.md, UI, screenshots, and references.
• Platform, incumbent stack, content languages, accessibility, and responsive constraints.

Expected outputs

• Requested design decision, findings, or implementation handoff with observed evidence.
• Selected supplier, operation, resolved source, and capability or verification limits.

outputs:
  - name: design-doc
    description: Updated visual contract when the design system materially changes
    artifact: "DESIGN.md"
    required: false
  - name: design-context
    description: Existing context refreshed after substantive discovery
    artifact: ".design-context.md"
    required: false