Spotlight Laravel Package

Product Decisions This Supports

• Command palette / power-user navigation as a shippable feature, not a roadmap item. Spotlight gives you a Cmd+K (or custom hotkey) palette that searches commands, records, and routes in a Livewire app. That turns "we should make the app faster to navigate" into a day-two deliverable instead of a bespoke front-end project.
• Build vs. buy for internal tooling and admin surfaces. Any Laravel app with an internal back office, support console, or ops dashboard can register actions as spotlight commands (jump to a customer, open a settings page, trigger a workflow) without building search UI, keyboard handling, focus traps, debouncing, or async result loading from scratch.
• Onboarding and feature discoverability. Because commands are registered declaratively and surfaced by fuzzy search, you can ship a palette entry per feature and let new users find capabilities they'd otherwise never click through. Useful input to onboarding and activation metrics.
• Upgrade posture against the Laravel release train. 2.0.4 adds Laravel 13.x compatibility. This is a maintenance release, not a feature release — it de-risks staying on the latest Laravel and tells you the maintainer tracks framework releases. Relevant to any decision to build a hard dependency on it for a multi-year product.
• Not a search platform. It does not replace full-text search (Scout/Meilisearch/Algolia) or a site-wide search results page. Scope palette-level navigation and action dispatch here; scope content search elsewhere.

When to Consider This Package

Consider adopting when:

• The app is Livewire-based, or you are willing to introduce Livewire solely for the palette. This is the gating constraint — the package is a Livewire component, not a framework-agnostic JS library.
• You want a keyboard-driven command surface (navigation, actions, record jump-to) rather than a search-results page. The value proposition is action dispatch, not relevance-ranked content retrieval.
• Your team is small and the alternative is spending 1–3 weeks of engineer time on a palette component plus ongoing maintenance of keyboard/focus/accessibility edge cases.
• You want framework-version durability: the 2.0.4 release demonstrates the maintainer ships compatibility updates alongside new Laravel majors, which lowers the "abandoned package" risk for a dependency you'd otherwise build in-house.
• The palette is a secondary navigation affordance. Treat it as a power-user accelerator layered on top of a working UI — not the only path to critical functionality.

Look elsewhere when:

• The app is Vue/React/Inertia without Livewire, or a non-Laravel backend. Use a JS-native palette (kbar, cmdk, Ninja Keys) instead.
• You need rich content search across large datasets — that's Scout plus a search backend; Spotlight is not the layer for it.
• You require deep customization of result rendering, ranking, or accessibility conformance beyond what the component exposes. At that point you're fighting the abstraction; a bespoke component is cheaper.
• You need an enterprise support contract or SLA. This is a community package; budget for the possibility of forking.

How to Pitch It (Stakeholders)

For executives: This is a small, well-scoped open-source component that gives our Laravel app a professional-grade command palette — the Cmd+K quick-jump experience users now expect from tools like Linear, Notion, and GitHub. It converts a "nice to have" UX item into roughly a day of integration work instead of weeks of custom front-end engineering, and it's free. The newest release keeps it compatible with the current Laravel release line, so it won't become an upgrade blocker. Risk is low and contained: it's a presentation-layer component with no data model or vendor lock-in, and we can remove it if it doesn't land.

For engineering: Livewire component, registered commands, fuzzy search over those commands, keyboard shortcut and async result support. Integrate by installing the package, adding the component to your layout, and registering commands in a service provider. 2.0.4 is purely a Laravel 13.x compatibility bump — a non-breaking patch, no migration needed on our side. Caveats: it's Livewire-coupled, it's a navigation/action surface rather than a search backend, and we should decide up front whether palette commands are hand-registered or generated from a policy-aware registry so we don't leak authorization into a client-side search index. Recommend a timeboxed spike: register 5–10 high-value commands, measure usage, then decide whether to expand or drop it.