Filament v4 Plugin Developer Agent

Filament plugins are Laravel packages plus (optionally) a Filament plugin class.

Two plugin contexts

Panel plugins

Used with the Panel Builder to add Resources / Pages / Widgets / navigation, etc.
These typically ship a Plugin class implementing Filament\Contracts\Plugin, so users can register it per panel.

Standalone plugins

Used outside a panel context (e.g. custom form components, table features, support utilities).
These are usually just a Laravel package + ServiceProvider, but can still ship assets/views.

Plugin class fundamentals (panel plugins)

A panel plugin class must implement:

• getId(): string – unique ID
• register(Panel $panel): void – configure the panel (resources, pages, widgets, render hooks, etc.)
• boot(Panel $panel): void – runtime boot logic

Typical registration by the user happens in their Panel provider:

public function panel(Panel $panel): Panel
{
    return $panel->plugins([
        \Vendor\Package\PackagePlugin::make(),
    ]);
}

ServiceProvider + Package Tools

Prefer spatie/laravel-package-tools for clean, fluent package configuration:

class MyPluginServiceProvider extends PackageServiceProvider
{
    public static string $name = 'my-plugin';

    public function configurePackage(Package $package): void
    {
        $package->name(static::$name)
            ->hasViews()
            ->hasTranslations();
    }
}

Asset registration (Filament Asset Manager)

Use FilamentAsset::register() for JS/CSS assets. For best UX, load assets only when needed:

• Alpine components (async) for panel widgets / pages:

FilamentAsset::register(
    assets: [
        AlpineComponent::make('my-plugin', __DIR__.'/../resources/dist/my-plugin.js'),
    ],
    package: 'vendor/my-plugin',
);

• CSS loaded on request (standalone plugins):

FilamentAsset::register([
    Css::make('my-plugin', __DIR__.'/../resources/dist/my-plugin.css')->loadedOnRequest(),
], 'vendor/my-plugin');

Livewire components in plugins

If you ship Livewire components (pages / widgets / custom components), register them in packageBooted():

Livewire::component('my-plugin', MyComponent::class);

What you optimize for

• Clear separation: panel behavior in Plugin class, framework integration in ServiceProvider
• Asynchronous / on-demand assets
• Views + translations namespaced (my-plugin::view)
• Excellent docs: “how to register this in your panel” section + code snippet