coss

Implements coss UI components with correct imports, composition, and accessibility patterns.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill coss-sethdavis512
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coss
Source: https://github.com/sethdavis512/iridium/tree/main/.agents/skills/coss
Command: npx skills add https://github.com/sethdavis512/iridium --skill coss-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @base-ui/react, and includes references (resource) components.

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.

Frequently Asked Questions about coss

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install coss UI components in a React project?▼

Install coss components with the shadcn CLI by running npx shadcn@latest add @coss/<component>, such as @coss/dialog or @coss/select. For new projects, npx shadcn@latest init @coss/style sets up fonts and the full theme automatically.

How do I migrate from shadcn or Radix to coss and Base UI?▼

Migrate by replacing Radix-style APIs with coss equivalents, such as render-based trigger composition instead of asChild, and array values with the multiple prop on Accordion instead of type="single". The migration rules reference documents these patterns per primitive.

Does coss UI require Tailwind CSS v4 and Base UI?▼

Yes, coss components are built on @base-ui/react and assume Tailwind CSS v4 conventions for styling and theme tokens. Manual installs must include the documented dependencies and additional theme tokens like destructive-foreground and info.

What is the difference between coss Select, Combobox, and Autocomplete?▼

Select handles single-choice from a predefined list without search, Combobox adds searchable filtering over a strict option set, and Autocomplete allows free-text input with suggestions. Choose based on whether search and free text are required.

Why does my coss dialog form layout break?▼

Dialog layout breaks when DialogHeader, DialogPanel, and DialogFooter are wrapped in extra containers. Keep the header outside the form and wrap only the panel and footer in Form with className="contents" so the popup flex layout treats them as direct sections.

When should I not use coss primitives?▼

Avoid inventing custom markup when a primitive exists, and do not use trigger-based overlays for simple inline content. The Skill also excludes maintaining coss monorepo internals and editing registry internals unless explicitly requested.