What problem does it solve? Frontend teams often duplicate buttons, inputs, and modals across pages, causing inconsistent styling and painful maintenance. This Skill enforces a single source of truth for reusable React components so design changes propagate everywhere from one place. ## Core Features & Use Cases - DRY Component Enforcement: Prohibits inline interactive elements in pages and requires all reusable UI to live in src/components/. - Mandatory Folder Structure: Each component must include a .tsx file, a .types.ts file, and a barrel index.ts export. - CSS Variable Tokens: Bans hardcoded colors and requires global tokens like --color-primary and --color-bg-card defined in index.css. - Base Component Catalog: Defines required variants and features for Button, Input, Dropdown, Modal, Toast, Image, Badge, and Card. - Use Case: When building a new React page, the Skill ensures you compose it from the centralized library instead of hand-coding a one-off button with hardcoded hex colors. ## Quick Start Apply the ui-library rules to review my new React page in src/pages and refactor any inline buttons or hardcoded colors into shared components using CSS variables.