Wirekit Laravel Package

Product Decisions This Supports

• Build vs. buy for the app-shell and dashboard layer. The most common hidden cost in a Livewire product is the in-house Blade component library — forms, tables, modals, dropdowns, sidebars — plus the perpetual tail of dark-mode, focus states, and ARIA fixes. WireKit is a direct line item against that budget: broad coverage across forms, display, data display, overlays, navigation, layout, typography, marketing, and specialized/reading components, all themeable through --color-wk-* tokens.
• Roadmap gating for greenfield surfaces. Because it requires PHP 8.4+, Laravel 12+/13+, Livewire 4+, and Tailwind v4, adopting it is effectively a decision to keep new work on the newest TALL stack. That's a fine roadmap constraint for a new admin panel or marketing site; it's a blocker if part of the estate is still on Livewire 3.
• Time-to-first-screen for new features. The <x-wirekit::*> surface (button, input, select, data-table, modal, sidebar, app-shell) lets a feature team compose a screen of real UI rather than either hand-rolling markup or shipping unstyled forms. This compresses the "ugly but functional" phase of internal tools and betas.
• Accessibility and dark mode as defaults, not backlog items. ARIA wiring on interactive components, skip-link, visually-hidden-label support (hideLabel), and dark-mode-aware tokens move a11y from a per-sprint tax to a baseline. Useful when you're answering enterprise security/accessibility questionnaires or facing VPAT/EAA-style questions.
• AI-assisted delivery velocity. The wirekit:list / wirekit:show / wirekit:icons / wirekit:export-json commands, .wirekit-schema.json, AGENTS.md, Cursor rules, Laravel Boost manifest, and a local read-only MCP server mean assistants read real prop signatures instead of hallucinating them. If AI pair-programming is part of your delivery model, this is a measurable quality lever, not a novelty.
• Selective feature bets, cheaply. Optimistic UI is opt-in at the component level with zero render cost otherwise — you can trial perceived-latency improvements on one workflow without a framework-wide commitment. Chart library is a config toggle, so you can standardize on Chart.js (MIT) and allow ApexCharts per-instance only where needed.
• Marketing and product in one stack. Hero, feature-grid, CTA, plus container/section/grid primitives let a small team ship landing pages in Blade instead of adding a second frontend toolchain.
• Where it does not help your decision: non-Livewire frontends (Inertia/React/Vue), heavily bespoke brand-led consumer UI, or teams already standardized on Filament or a paid library like Flux UI.

When to Consider This Package

Adopt when all of these hold:

• The surface is greenfield or willing to be on PHP 8.4, Laravel 12+, Livewire 4, Tailwind v4, and Alpine.
• The team is committed to Blade/Livewire and values "no utility-class soup" — i.e., you want semantic components (intent="danger") reviewed in PRs rather than long class strings.
• You need breadth quickly and would otherwise spend weeks on a private component kit with worse a11y.
• You accept the maturity profile: ~22 stars, 0 dependents, small maintainer footprint, low overall score signal. That is acceptable if you can vendor/fork it and pin a version.
• Your browser baseline matches Tailwind v4's (Chrome/Edge 111+, Safari 16.4+, Firefox 128+) and nobody needs polyfills.
• You can clear legal: Packagist reports the license as NOASSERTION while the README and badge claim MIT — get the actual LICENSE file reviewed before it ships in a commercial product. Separately confirm the ApexCharts Community License revenue threshold (<$2M USD) or budget the commercial license.

Look elsewhere when:

• You need a vendor relationship: SLAs, paid support, security response commitments, or procurement review that a low-star community package won't survive.
• You're pinned to older infrastructure — Laravel 10/11, Livewire 3, PHP 8.2/8.3. WireKit simply won't install, so this is a non-starter until you upgrade.
• Your frontend isn't Livewire — Inertia, Vue, React, or plain Blade with an existing design system.
• Design is a differentiator and tightly art-directed; you'll spend the savings fighting the token layer, and a bespoke system is the honest answer.
• You need legacy browser support or a no-JS/SSR-first fallback story beyond Alpine.
• Your realistic alternatives already win: Filament (admin panels, batteries included), Flux UI (paid, mature, same ecosystem), Blade UI Kit, Mary UI. Evaluate WireKit as one candidate in that set, on a real screen, not on the README.

Practical adoption caveat worth flagging to engineering: you must add the vendor Blade path to @source in app.css or components render unstyled. That's the single most common first-hour failure and it belongs in the spike checklist, not the retro.

How to Pitch It (Stakeholders)

For executives — one paragraph: WireKit is a free, MIT-licensed UI component library for our Laravel/Livewire stack that replaces a large chunk of the private component library we'd otherwise build and maintain. It gives us forms, tables, navigation, overlays, and layout primitives that are dark-mode aware and accessible by default, with a theming layer that keeps our brand tokens centralized. It also ships tooling that makes our AI coding assistants generate correct markup instead of guessing, which shortens the loop from ticket to working screen. The trade-off is maturity: it's a young open-source project pinned to our newest framework versions, so we'd adopt it behind our own thin wrapper components, pin the version, and keep the option to fork. The alternative is roughly X engineer-weeks of component work plus ongoing a11y and dark-mode maintenance.

For engineering leads:

• Bounded blast radius. Four-level customization (CSS-variable tokens → published views) means most divergence is a token change, not a fork. Wrap primitives in x-app::* components on day one so a future swap is a find-and-replace, not a rewrite.
• Explicit, discoverable API. Prop-driven components with dev-mode "did you mean" warnings and composition guards (card.body, prop typos) catch mistakes in development and are silent in production — low noise, real value.
• No tax for unused features. Optimistic UI and the chart adapters are opt-in; unused paths cost nothing in rendered bytes. Chart backend is a one-line config swap, with per-instance override for mixed-library pages.
• Modern-codebase alignment. Requiring Laravel 12+/Livewire 4+ is a forcing function that keeps new surfaces current — but it means this is a new-work decision, not a retrofit.
• Documented and versioned. Changelog, releases, and docs site with integration/troubleshooting guidance reduce onboarding risk; the version-matched CLI manifest can't drift from the installed package.

Recommended next steps (one sprint): time-boxed spike on one real internal screen; legal reads the actual LICENSE and confirms the ApexCharts threshold; confirm the PHP 8.4 / Laravel 12 / Livewire 4 / Tailwind v4 baseline is true for the target app; establish wrapper-component convention and version pinning before any second team touches it. Success criteria: screen shipped, zero custom ARIA patches needed, and a documented "what we'd have to rebuild if we abandoned this" list under one week of effort.