Filament Command Palette Laravel Package

Product Decisions This Supports

• Fund or defer an “admin speed” roadmap item. This package turns Cmd/Ctrl+K navigation into a one-line experiment on an existing Filament panel, so the decision becomes “run a time-boxed pilot and measure” rather than “commit a sprint to build a palette.”
• Build vs. buy for the baseline. Adopt the palette shell—MIT licensed, no migrations, no new JS build, inherits Filament styling—and build only the thin custom-command layer that encodes your team’s repeated workflows. Do not rebuild keyboard navigation, modal behavior, filtering, or dark-mode support.
• Prioritize features against navigation friction. If admins lose time hunting through a deep sidebar, this is a cheap countermeasure. If they need record-level search across large datasets or cross-resource actions, this package does not replace Filament’s global search or a real search backend.
• Define the target user. Internal ops, support, and admin power users—not customer-facing users. Use it to validate demand for keyboard-first workflows before investing in a broader command surface.
• Set rollout boundaries. Pilot on one internal panel; disable the topbar button where UI clutter matters; disable the developer-facing “publish views” command in production; choose standard unless you will maintain description/preview metadata for every command.
• Make permissions UX an explicit product decision. The palette lists commands; destination policies authorize. Product must decide whether to filter command visibility at generation time to avoid 403 dead-ends and information leakage. This is product behavior, not just an engineering detail.
• Evaluate dependency risk honestly. Nineteen stars, zero dependents, a single-maintainer community package, and Filament v5 coupling support a “time-boxed experiment with a removal path” decision—not platform standardization.
• Measure before expanding. Instrument palette opens, command selections, time-to-navigate on top admin tasks, and weekly active admin usage. Set kill criteria—for example, less than 10% of target admins using it in 30 days—before investing in a curated command set.

Representative use cases: deep admin sidebars, repetitive ops actions (“Create Invoice,” “Open Overdue Orders,” “Switch Tenant”), support triage shortcuts, and internal tooling where speed matters. Avoid positioning it as customer-facing discoverability.

When to Consider This Package

• You run a Filament v5 admin panel on Laravel 11/12—verify the Laravel 13 claim in release notes against the README’s stated requirements—and have a deep sidebar or many resources.
• Your users are internal/power users who live in the admin daily and would benefit from keyboard-first navigation.
• You want a low-cost, reversible experiment: one Composer require, one plugin registration, optional config; no database changes and no front-end pipeline changes.
• You have engineering capacity to own the integration: custom commands injected in a service provider rather than config closures (closures break config:cache), permission filtering, tests for command providers, and a documented removal path.
• You need baseline navigation plus a few workflow commands, not full record search. The README documents pages, resources, and navigation items; record and action search are not documented out of the box, and custom commands are URL-based.
• You will keep the default template or accept that published views are a fork that diverges from upstream template updates—1.4 explicitly reworked templates.

Look elsewhere or defer if:

• The surface is customer-facing with accessibility, design-system, or brand-polish requirements.
• You need record-level fuzzy search across large datasets, multi-tenant permission complexity beyond simple command gating, or enterprise vendor support/SLA.
• Your team cannot absorb single-maintainer dependency risk or Filament major-version churn.
• You need per-panel template configuration; the template setting is global, not per panel.
• Your panel’s built-in global search already solves discovery and users are mouse-first—the palette may add UI clutter without changing behavior.
• Cmd/Ctrl+K conflicts with existing shortcuts and remapping does not resolve it.

How to Pitch It (Stakeholders)

Executives: “A cheap, reversible experiment to make our internal admin faster. It adds Cmd/Ctrl+K navigation to our existing Filament panel with one line of configuration—no database work, no new infrastructure, MIT licensed. We pilot it on one internal panel for 30 days and measure whether admins actually use it. It is not a platform bet: low adoption, zero dependents, and a single maintainer mean we treat it as a time-boxed trial with a one-line removal path, not a strategic dependency.”

Engineering: “A small, Filament-native plugin that rides the existing Alpine/Livewire bundle and inherits panel styling and dark mode. Integration surface is one plugin registration plus CommandItem definitions. No migrations, no new JS build. Two real costs: custom commands must be injected at runtime in a service provider because config:cache cannot serialize closures, and permissions must be filtered at command-generation time because the palette is a launcher, not an authorizer. Pin the version, wrap command generation in a testable class, disable the production publish-views command, and keep removal to deleting one plugin line plus our command class.”

Product stakeholders: “Use it to validate demand for keyboard-first admin workflows. Success metrics: palette opens per weekly active admin, selection-to-completion rate, reduced time-to-navigate on top tasks, and support feedback. Kill criteria: low repeat usage or permission/UX issues that require more custom work than the baseline is worth. If it wins, invest in a curated command set for the top 5–10 repeated workflows; if it loses, remove it without architectural debt.”