What problem does it solve? UX reviews often judge code against generic design rules instead of the repository's own design system. This Skill extracts the repo's actual design contract — tokens, component registry, screen archetypes, and conventions — into .uxproof/ so every subsequent UX review is grounded in this project's real design system. ## Core Features & Use Cases - Design contract extraction: Runs the pinned uxproof extractor to generate contract.json, tokens.json, components.json, and conventions.md from the working tree. - Manual section preservation: Team judgment calls written into the fenced manual section of conventions.md survive every regeneration and outrank generated rules. - Honest degradation: Repositories without a declared design system get a proposed palette derived from colors already in the code, clearly marked as suggestions rather than enforced tokens. - Use Case: Before running automated UX reviews on pull requests, run this once per repository so reviewers judge against your Tailwind tokens and component roots instead of generic heuristics; re-run after design-system changes to refresh the contract. ## Quick Start Ask the agent to extract this repository's design system into a .uxproof contract using the ot-ux-setup skill. ## Quick Start Run the ot-ux-setup skill to extract this repository's design tokens, components, and screen archetypes into a committed .uxproof contract.
