create-component

To create reusable UI components with CVA and DaisyUI, you scaffold elements like buttons, inputs, and alerts using CVA variants, ensuring proper imports from the CVA config and className handling with cx() for consistency across your app/components directory.

Structuring frontend component patterns involves placing CVA-based components under specific app/components categories, such as actions for buttons. This enforces Iridium design conventions, reduces boilerplate, and maintains UI consistency across the application.

Yes, you can use this CVA component scaffolding for modals and alerts. It provides templates and integration notes for building reusable UI elements, ensuring they follow Iridium patterns and maintain proper className composition with cx().

Yes, you need to import from the CVA config when building DaisyUI components. The skill enforces proper imports from the CVA config to standardize variant definitions and ensure correct className handling using the cx() utility.

ClassName composition with CVA variants works by using the cx() utility to merge classes. This approach ensures that reusable DaisyUI components handle conditional styling and variant overrides correctly without conflicts, following Iridium design conventions.

Scaffolding CVA-based components for frontend UI is limited to predefined elements like buttons, inputs, cards, modals, and alerts. It focuses strictly on Iridium patterns and DaisyUI integration, meaning custom non-CVA design systems are not supported by these templates.