Weave Code
Ui Kernel Laravel Package
symfinity/ui-kernel
Symfinity UI Kernel gives Laravel apps a reusable UI foundation: Blade components, layouts, form controls, and design tokens for consistent admin and front-end interfaces. Configure themes and responsive primitives quickly, with less boilerplate.
Design tokens, themes, and slim CSS generation for Symfony
Frequently asked questions about Ui Kernel
- What is symfinity/ui-kernel and what problem does it solve in a Laravel app?
- It is a lightweight UI foundation package for Laravel that bundles reusable Blade components, layout primitives, form controls, and presentation utilities. The goal is to stop teams from copy-pasting the same markup across views and instead centralize UI patterns in one place. It deliberately keeps UI concerns separate from domain logic, so your application code stays focused on business behavior while the kernel handles presentation consistency.
- How do I install symfinity/ui-kernel with Composer?
- Install it like any Laravel package with composer require symfinity/ui-kernel from your project root. Because it is Laravel-native, it is designed to work with minimal configuration once the service provider is registered. After installing, check the repository README for any publishable config or view assets you may want to expose so you can override defaults.
- Which Laravel versions does symfinity/ui-kernel support?
- The package is built specifically for Laravel and relies on Blade, so it targets modern Laravel releases. The exact supported version range is declared in the package's composer.json constraints, which is the authoritative source to check before upgrading Laravel. If your application is on an older Laravel release, verify the constraint in the repository before adding it to your dependency list.
- Do I need to publish configuration or views to use the UI kernel?
- No, the package is intended to work out of the box with minimal configuration, which is part of its appeal for existing Laravel stacks. Publishing is only useful when you want to customize design tokens, layouts, or component markup in your own application. Refer to the repository documentation for the specific publish tags and config keys available in your installed version.
- Does symfinity/ui-kernel work with Tailwind CSS or an existing design system?
- The kernel focuses on centralized design tokens and styling conventions rather than forcing a specific CSS framework, so it can sit alongside an existing setup. In practice you will map the token conventions to whatever utility or component classes your app already uses. If your project has a strict design system, plan a short review of the provided components to align class names and spacing scales before rolling it out broadly.
- How do design tokens and theming work in symfinity/ui-kernel?
- Design tokens are centralized so that spacing, color, and typographic conventions live in one place instead of being repeated across templates. That makes theme changes and responsive adjustments far less error-prone than editing markup file by file. Teams typically override the token defaults to match their brand and then rely on the shared Blade components to consume them consistently.
- Can I extend the UI kernel with my own app-specific components?
- Yes. The kernel is described as extensible specifically so applications can layer their own Blade components and layouts on top of the shared foundation. The usual pattern is to keep generic primitives in the package and put domain-specific components in your app, reusing the kernel's tokens and layout scaffolding. That separation keeps upgrades predictable while still letting you build bespoke UI.
- Will symfinity/ui-kernel slow down my Laravel application?
- It is positioned as a lightweight UI foundation, so it adds Blade components and presentation utilities rather than heavy runtime services or large front-end bundles. Blade components compile to plain PHP views, which keeps rendering overhead minimal in production. As with any dependency, run your normal caching and opcache setup, and review the package's assets if you care about front-end payload size.
- How do I test Blade components built with symfinity/ui-kernel?
- Blade components can be rendered in isolation inside Laravel feature or component tests, which is the simplest way to assert markup, slots, and conditional states. Because the kernel is Laravel-native, standard testing helpers and view assertions apply without extra wiring. Test your own wrapper components too, since those are where app-specific props and token overrides are most likely to break.
- Is symfinity/ui-kernel an alternative to Laravel Breeze, Jetstream, or a full component library?
- Not exactly. Breeze and Jetstream are starter kits with authentication scaffolding, while this package is a presentation layer of Blade components, layouts, and design tokens. It is closer to a lightweight internal component library you would otherwise build yourself, and it can complement a starter kit rather than replace it. Before adopting it, confirm that its component inventory and Laravel version constraints match your project's needs and maintenance expectations.
Weaver
How can I help you explore Laravel packages today?