Laravel Blade components you install and own.
A free Laravel UI kit of Blade and Tailwind components, MIT licensed. One command copies only the ones you need into your app, to edit like your own code. No Livewire or Alpine needed, and they work inside Livewire too.
Build a hotel booking form with Bladewell components (https://www.bladewellui.com/llms.txt): guest name, the stay as a date range, a guest count with − and + buttons, a room select, and a total that updates when the dates or room change.
More prompts, and connecting your agent: For AI agents.
composer require --dev bladewell/bladewell && php artisan bladewell:add text-input date-range-picker number select price-roll button
Every step, and updating later: Installation.
Source on GitHub · MIT licensed · Laravel 12 and 13, PHP 8.3+, Tailwind CSS 4.1+ · Changelog
Install in three steps
For Laravel 12 and 13 with Vite and Tailwind CSS 4.1 or later, which new Laravel apps have out of the box.
Requirements and the full installation guide →Starting a new app?
Use the starter kit
- Laravel 13 with Bladewell installed
- Light and dark theme, error pages, strict CSP
- Laravel Boost and the MCP server set up for agents
- Plain Blade: no React, Vue or Alpine to remove
Needs PHP 8.3+, Composer and Node.js 20.19+.
composer create-project bladewell/starter-kit my-app
cd my-app
npm install && npm run build
-
Require the package
It only does the copying, so it can stay a dev dependency. Your app never needs it at runtime.
Terminalcomposer require --dev bladewell/bladewell -
Add the components you need
Name the components, or run it with no names to pick from a list. It copies each one with what it depends on into your app, and adds the JS and CSS imports. Later, the same command updates them and leaves your own edits alone. How updates work.
Terminalphp artisan bladewell:add datepicker table -
Build your assets and use them
Then write the tag like any other Blade component.
Terminal, then Bladenpm run build <x-widget.datepicker name="start_date" label="Start date" />
Works with Livewire
Not needed, but supported: every component is checked in a browser inside Livewire 3 and 4 components.
- Form controls bind with
wire:model, no name needed, and show the property's value and its validation errors after every render. - What someone did stays as they left it through a render: an open modal or menu, a panel they opened, a running stopwatch, files they picked.
- The component shows toasts and opens or closes modals with
$this->dispatch(). - Components added by a render or by
wire:navigateset themselves up, with nothing to call. Each one's page has a Livewire example under Usage.
<form wire:submit="save">
<x-widget.text-input label="Email" type="email" wire:model="email" />
<x-widget.datepicker label="Start date" wire:model.live="start" />
<x-widget.button type="submit">Save</x-widget.button>
</form>
// In the component, once it's saved
$this->dispatch('toast', type: 'success', message: 'Saved.');
Ready for AI agents
Agents get the same catalogue in a form they can read. Each component's entry has its install command, props, working examples and full source, so an agent can add a component or write it in by hand.
- /llms.txt
- An index of every component, for agents that follow the llms.txt convention.
- /r/index.json
- Every component, with a link to its full entry.
- /r/datepicker.json
- One component's full entry: install command, props, examples and source.
- php artisan bladewell:list --json
- The same catalogue offline, from the installed package.
- php artisan bladewell:mcp
- An MCP server in your app: the catalogue, what this app has installed and edited, and installing with a dry run first.
Components
51 components, each bringing what it depends on, server side included. Adding the date picker also adds the field frame and icon it's built from, plus validation rules such as MinimumAge in App\Rules.
Forms (26)
Everything else (23)
Layouts (2)
Questions
- Is Bladewell the same as laravel/ui?
- No. laravel/ui is the Laravel team's older package that scaffolds Bootstrap, Vue or React login pages. Bladewell is a separate, independent project: a catalogue of Blade and Tailwind CSS v4 components that one Artisan command copies into your app.
- How is it different from a starter kit or a component package?
- A starter kit sets up a new app once. A component package stays installed and you call its components. Bladewell copies each component's Blade, JavaScript and CSS into your existing app, so you can edit them like your own code, and it needs no Livewire or Alpine.
- Does wire:model work on Bladewell components?
- Yes, directly on the component, with no events or listeners to write: <x-widget.select wire:model.live="country" />. The form controls (inputs, select, date and time pickers, tags, file upload and the rest) show the property's value after every render, a value set in PHP included, and its validation errors. A component opens a modal or shows a toast with $this->dispatch(). Every component is checked in a browser inside Livewire 3 and 4.
- Do I need wire:ignore to use Bladewell in Livewire?
- No. The components already shield the parts their scripts build, so they keep what the person did through every render: an open modal, a sorted table, a running timer. Wrapping a form control in wire:ignore would stop it showing values set in PHP and validation errors. The one exception is a progress bar you drive from JavaScript with progress.set().
- What are the limits of Bladewell in Livewire?
- A few: files you have edited are merged by hand from bladewell:diff; the pickers, select and similar controls take their value from PHP or wire:model, not from Alpine or your own script; a captcha should be sent with wire:submit; and it needs Blade with Tailwind CSS v4. The Livewire guide at https://www.bladewellui.com/guides/livewire-blade-components lists them with examples.
- Do copied components still get updates?
- Yes. After composer update, php artisan bladewell:add --installed puts the new version into every file you haven't edited and lists the ones you have; bladewell:diff shows what those would miss. bladewell.lock keeps track of which is which, so your edits are only overwritten if you pass --force.
- Does my app need Bladewell at runtime?
- No. The package only does the copying, so it can stay a dev dependency. Once a component is copied in, it runs without it.
- Is it free?
- Yes. Bladewell is open source and MIT licensed.
Free, and staying free
Bladewell is MIT licensed and built in spare time. If a component saved you an afternoon, or it's in an app your company runs, sponsoring it on GitHub pays for new components, fixes and keeping up with Laravel and Tailwind releases. A one-off coffee helps too.