Design with the design system
Bridge a product idea, or an existing design file, and the repository's design
system, so that what gets drawn can be built without drift. Every token,
component, layout, and state this skill names comes from the repository's
design contract (.uxproof/, written by om-ux-setup, including layers
imported from a design system a dependency ships) — never from memory and never
from a built-in palette.
Input — a screen to design, or a design-file reference (a link, a frame id, or an attached screenshot or export) to audit. — one of: a self-contained design brief, an audit with a remediation plan, or a ready-to-paste prompt for another design-capable agent; optionally, provider operations applied to the design file when the user explicitly asks.