Flux UI Development
When to Apply
Activate this skill when:
- Creating new UI components or pages
- Working with forms, modals, or interactive elements
- Styling components with Flux UI patterns
- Checking available Flux components
Documentation
Use search-docs for detailed Flux UI patterns and documentation.
Basic Usage
This project uses the Pro version of Flux UI, which includes all free and Pro components and variants.
Flux UI is a component library for Livewire built with Tailwind CSS. It provides components that are easy to use and customize.
Use Flux UI components when available. Fall back to standard Blade components when no Flux component exists for your needs.
<!-- Basic Button --><flux:button variant="primary">Click me</flux:button>
Available Components (Pro Edition)
Available: accordion, autocomplete, avatar, badge, brand, breadcrumbs, button, calendar, callout, card, chart, checkbox, command, composer, context, date-picker, dropdown, editor, field, file-upload, heading, icon, input, kanban, modal, navbar, otp-input, pagination, pillbox, popover, profile, radio, select, separator, skeleton, slider, switch, table, tabs, text, textarea, time-picker, toast, tooltip
Icons
Flux includes Heroicons as its default icon set. Search for exact icon names on the Heroicons site - do not guess or invent icon names.
<!-- Icon Button --><flux:button icon="arrow-down-tray">Export</flux:button>
For icons not available in Heroicons, use Lucide. Import the icons you need with the Artisan command:
php artisan flux:icon crown grip-vertical github
Common Patterns
Form Fields
<!-- Form Field --><flux:field>
<flux:label>Email</flux:label>
<flux:input type="email" wire:model="email" />
<flux:error name="email" />
</flux:field>
Tables
<!-- Table --><flux:table>
<flux:table.head>
<flux:table.row>
<flux:table.cell>Name</flux:table.cell>
</flux:table.row>
</flux:table.head>
</flux:table>
Verification
- Check component renders correctly
- Test interactive states
- Verify mobile responsiveness
Common Pitfalls
- Not checking if a Flux component exists before creating custom implementations
- Forgetting to use the
search-docstool for component-specific documentation - Not following existing project patterns for Flux usage