- How do I install Aura UI in a Laravel application?
- Install the package with Composer using composer require bluestarsystem/aura-ui. You then pull individual components into your app with php artisan aura:add button, which copies that component's Blade source into your templates. Aura UI assumes a stack of Laravel 12 or 13, Livewire 3 or 4, Alpine.js and Tailwind CSS 4.
- Which Laravel and Livewire versions does Aura UI support?
- Aura UI targets Laravel 12 and 13 and works with both Livewire 3 and Livewire 4. It requires PHP 8.3 or newer and Tailwind CSS 4 on the front end. Alpine.js provides the client-side interactivity behind components such as the command palette and date picker.
- Is Aura UI free for commercial projects?
- Yes. Aura UI ships 127 production-ready Blade components under the MIT licence, so commercial use is permitted. There is no account, no licence key and no paid tier required to use the components. The calendar, command palette, date picker and chart components are all included in the free package.
- Do I have to keep Aura UI as a dependency, or can I own the component code?
- Either approach works. The aura:add command copies the source of a component directly into your application, so you can modify it freely. You can keep Aura UI installed as a Composer dependency or remove it and walk away with the copied files, with no lock-in.
- What components are included in Aura UI?
- The package contains 127 Blade components covering forms, navigation, overlays and data display. Notable ones include date and time pickers, file upload, autocomplete, multiselect, calendar, command palette, QR code, a rich editor, a Chart.js-backed chart component (line, bar, pie, doughnut, area) and European business fields such as an IBAN field and currency input. A machine-readable index of every component is available at aura-ui.com/r/registry.json.
- Does Aura UI require Tailwind CSS 4 and Alpine.js?
- Yes. Aura UI is built on Tailwind CSS 4 for styling and Alpine.js for lightweight interactivity, alongside Livewire for server-driven behaviour. The components share a single design system based on gradients, glow, micro-animations, glass morphism and dark mode. Attempting to use the components without Tailwind 4 will break the intended styling.
- How does Aura UI handle accessibility?
- Accessibility is verified in continuous integration rather than just claimed: 111 colour pairs are checked against WCAG contrast thresholds on every build. You can run the same checks against your own Blade templates with php artisan aura:doctor --a11y. This lets you catch contrast regressions introduced by your own customisations.
- Does Aura UI support dark mode and design customisation?
- Every component supports full dark mode as part of the shared Vibrant Depth design system. Styling uses Tailwind CSS 4 utilities, so you can override colours, gradients and spacing with your own Tailwind configuration or by editing copied component files. Because aura:add copies source into your app, deeper customisation does not require patching vendor code.
- How is Aura UI different from flat, minimal Laravel UI kits?
- Aura UI deliberately leans into a Vibrant Depth aesthetic with gradients, glow, glass morphism and micro-animations, rather than the flat minimal look most libraries use. The bigger differentiator is licensing breadth: components that are usually paywalled, such as the calendar, command palette, date picker and chart, are MIT here. The project also runs its test suite and contrast checks through GitHub Actions.
- Can AI coding assistants read the Aura UI documentation?
- Yes. Every documentation page is available as raw Markdown by appending .md to its URL, and the full set is indexed in llms.txt. Aura UI also publishes an MCP server and a machine-readable component registry at /r/registry.json, so assistants can look up component APIs directly. This makes it practical to generate or refactor Aura UI components inside an AI-assisted workflow.