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 actual design contract (tokens, component registry, screen archetypes, conventions) from the working tree into .uxproof/, so every subsequent UX review is grounded in this repo's real design system. ## Core Features & Use Cases - Design contract extraction: Runs the pinned npx uxproof@0.3.1 init --no-skills extractor to produce contract.json, tokens.json, components.json, and conventions.md, with a manual by-hand fallback when npm or network access is unavailable. - Persistent team conventions: A fenced manual section in conventions.md captures judgment calls only the team knows (naming rules, forbidden patterns, tone) and survives every regeneration, outranking generated rules. - Honest degradation: When a repository has no declared design system, it records that fact and proposes a palette derived from colors already in the code, clearly marked as suggestions rather than enforced tokens. - Use Case: Before running UX reviews on a Next.js + Tailwind codebase, run this once to generate the .uxproof/ contract, commit it, and let review skills judge pull requests against the project's own tokens and components. ## Quick Start Ask the agent to run the UX setup skill to extract this repository's design system into a .uxproof/ contract and report what was found.
