oma-design

1# oma-design
2 
3## Scheduling
4 
5### Goal
6Resolve project design intent, select the applicable external design skill, and
7retain the project's visual contract and verification evidence. `DESIGN.md`
8records the design system when the task creates or materially changes it.
9 
10### Intent signature
11- Design system, `DESIGN.md`, visual direction, redesign, or UI design review.
12- Typography, color, layout, motion, accessibility, or component decisions before implementation.
13 
14### When to use
15- Define or revise a visual system or substantial design direction.
16- Review an existing UI or refine a chosen visual direction.
17- Extract design decisions from existing UI, screenshots, or supplied references.
18 
19### When NOT to use
20- Implement application UI or export framework-specific tokens -> `oma-frontend` or `oma-mobile`.
21- Plan product scope -> `oma-pm`; generate an image -> `oma-image`.
22- Review general correctness or security -> `oma-qa` or `oma-security`.
23 
24### Expected inputs
25- Requested surface and outcome, existing brand and project facts, and change scope.
26- Available `DESIGN.md`, `.design-context.md`, UI, screenshots, and references.
27- Platform, incumbent stack, content languages, accessibility, and responsive constraints.
28 
29### Expected outputs
30- Requested design decision, findings, or implementation handoff with observed evidence.
31- Selected supplier, operation, resolved source, and capability or verification limits.
32 
33```yaml
34outputs:
35  - name: design-doc
36…