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 repository's actual design contract (tokens, component registry, screen archetypes, conventions) into a versioned .uxproof/ directory so every subsequent UX review is grounded in this codebase'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 override surface: Preserves a fenced manual section in conventions.md where team judgment calls survive every regeneration and outrank generated rules. - Honest degradation: When a repository has no declared tokens, it records that fact and proposes a palette derived from colors already in the code as a first draft, never as an enforced rule. - Use Case: A team adopting AI-assisted UX reviews runs this once per repository so that pull request reviews and module audits cite the project's own tokens and components instead of generic heuristics. ## Quick Start Ask the agent to extract this repository's design system into a .uxproof/ contract and report what was found.
