What problem does it solve? It prevents inconsistent, off-brand UI code in the ERP webapp by enforcing a single authoritative design contract: semantic tokens from design/tokens.json, the Fluent 2 palette, and the existing src/components/ui/ component library. ## Core Features & Use Cases - Token Enforcement: Blocks hardcoded hex colors, generic Tailwind color classes, and arbitrary spacing values; only semantic tokens generated from design/tokens.json are allowed. - Component Reuse Rules: Requires importing and extending existing base components (Button, Card, Input, Table, EnhancedModal, EmptyState, ErrorState) instead of creating duplicates. - State & i18n Coverage: Mandates loading/empty/error states, useI18n() for all UI text, and mono fonts for numbers, amounts, dates, and IDs. - Use Case: When asked to build a new orders table page, the Skill directs you to compose Table, PageHeader, and GenericSkeletonList with token-based classes, then validate with pnpm lint:design and pnpm tokens:check. ## Quick Start Ask the assistant to build or restyle any UI component in this repo while following the erp-design-contract rules and validating with the design lint tooling.