What problem does it solve? Building reusable design system components often leads to inconsistent styling, hardcoded colors, duplicated button variants, and primitives that break when composed with Base UI render props. This Skill enforces a single, consistent way to author primitives so every Button, Card, Input, or Dialog follows the same rules across the React console and the Astro landing app. ## Core Features & Use Cases - Platform routing: Detects the working directory and routes to the React variant (Base UI + Tailwind + CVA) or the Astro variant (static .astro components with optional React islands). - Pattern registry enforcement: Ships registry.yaml files with structural patterns (CVA variants, forwardRef, data-slot, named exports) and mechanical bad-practice detectors for hardcoded colors, missing forwardRef, and closed props interfaces. - Reference-driven implementation: Guides lookup of shadcn/ui and Base UI reference implementations before coding, then adapts them to project conventions. - Use Case: You need a new Pill component for both the landing page and the console. The Skill picks the right platform guide, scaffolds a CVA-driven primitive using design tokens, and checks it against the registry's bad practices. ## Quick Start Ask the agent to create a new primitive component such as a Badge or Card in the current package, and it will route to the correct React or Astro guide and enforce the design system rules.