What problem does it solve? Building interfaces with the coss component library requires knowing the exact APIs, composition hierarchies, and migration differences from shadcn/Radix, and guessing leads to broken overlays, accessibility gaps, and invalid code. ## Core Features & Use Cases - Primitive selection and usage guidance: A component registry index maps UI intents (dialogs, selects, forms, toasts, menus, and 50+ more) to the correct coss primitive with a dedicated reference guide covering imports, minimal patterns, and pitfalls. - Migration support from shadcn/Radix: Documents API differences such as render-based trigger composition and array-valued Accordion state so migrated code behaves correctly. - Install and discovery workflow: Covers the shadcn CLI commands (npx shadcn@latest add @coss/<component>), preview modes, and manual install steps with required dependencies and theme tokens. - Use Case: When asked to build a settings dialog with a validated form, the Skill directs you to the Dialog and Form references, producing code with DialogPopup, DialogPanel, Field, and FieldError composed according to documented invariants. ## Quick Start Ask the assistant to build a UI element with coss, for example: create an accessible delete confirmation dialog using coss AlertDialog components.