oma-design

# oma-design ## Scheduling ### Goal Design specialist that defines, creates, and validates project design systems. DESIGN.md is the central artifact; all design work revolves around it. ### Intent signature - User asks for design system, `DESIGN.md`, visual direction, typography, color, motion, accessibility, anti-pattern review, or component guidance. - User needs design decisions before frontend implementation or wants UI quality audited from a design perspective. ### When to use - Defining or revising a project design system - Creating or auditing `DESIGN.md` - Selecting typography, color, layout, motion, or component direction - Reviewing UI work for responsive behavior, accessibility, and visual quality - Using optional vendor inspiration from Stitch MCP or getdesign ### When NOT to use - Implementing frontend components or application UI -> use `oma-frontend` - Planning product scope or task breakdown -> use `oma-pm` - Backend, database, infrastructure, or mobile implementation -> use the relevant specialist skill - General quality/security review outside visual, interaction, and accessibility concerns -> use `oma-qa` ### Expected inputs - Product, brand, audience, platform, and UI/design problem - Existing `.design-context.md`, `DESIGN.md`, screenshots, references, or component constraints - Accessibility, responsive, language, and implementation constraints ### Expected outputs - Design direction, revised `DESIGN.md`, audit findings, component guidance, or hand...