UX Setup
Every UX skill in this collection judges against the repository's own design system, never against a built-in one. This skill extracts that design system into an executable contract, committed like code.
It works with any stack that has a design system, and degrades honestly when a repository has none: the contract records that, reviews fall back to universal evidence tiers, and the team gets a proposed de-facto palette derived from the colors its code already uses as the first draft of a design system.
Input — none; the skill reads the working tree.
Output — .uxproof/ written or refreshed, plus the handover report from
references/report-templates.md.
Where this skill stops. It produces a contract and hands it over. It does
not review anything: no findings, no verdicts, no lists of what is wrong with
the code, the screens, or the mockups, however tempting that is once the
contract is fresh. When the user wants judgment, name the skill that owns it
and stop: om-ux-review-pr for a pull request's running UI, om-ux-shape in
Review mode for a whole module or flow. Reviewing design files against the
contract is not covered by any skill in this collection yet; say so plainly
rather than improvising it here.