Why build it
The Laravel ecosystem had great component systems, but nothing that followed the shadcn/ui model: components as code you own, not packages you depend on. Teams want full control over markup so they can adapt it to their design system without fighting a distribution layer.
BlatUI copies plain Blade files into resources/views/components/ui/ — from that moment they are yours. Upgrades are opt-in per component, diffs are readable, and nothing breaks out from under you.
How it works
A hosted registry serves every component as inlined JSON. The blatui:add command resolves dependencies between components, copies sources, and reports required peer packages. A matching MCP server exposes the same registry to AI coding agents.
Adoption
The library ships with a CLI (blatui:init) that validates theme tokens, Alpine wiring and imports — making onboarding a single command.
- Works with or without Livewire
- Full light/dark theming through oklch design tokens
- Accessible by default: focus management, aria attributes, reduced-motion support