filament

Plugin filament from marketplace laravel-filament-claude in professor93/laravel-filament-claude. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• actions

  Use when adding or editing Filament actions — row/header/bulk buttons, confirmation dialogs, modal forms inside actions, custom business operations (approve, publish, ship), CSV import/export, or sending notifications — or when an action doesn't show, isn't authorized, runs out of memory on bulk sel

• core

  Use when doing ANY Filament work — creating or editing resources, forms, tables, actions, infolists, widgets, panels, admin pages — or when composer.json contains filament/*, or when debugging Filament errors ("Class not found" for Filament components, wrong imports like Filament\Tables\Actions, ->r

• custom-components

  Use when Filament's built-in components cannot express a UI — building a custom form field, table column, infolist entry or schema component, dropping a Blade view or Livewire component into a schema, injecting HTML into Filament's own views with render hooks, registering CSS/JS assets, or using Fil

• panels

  Use when configuring a Filament panel — panel providers, extra panels, paths/domains, middleware, login/registration/password-reset/profile pages, multi-factor auth, navigation groups, badges, clusters, user menu, SPA mode, theming or deployment — or when debugging "nobody can log in in production",

• performance

  Use when a Filament panel is slow — slow tables, slow dashboards/widgets, slow search or sort, high query counts (N+1), slow pagination on big tables, memory blowups on bulk actions or exports — or when asked to optimize SQL/Eloquent queries, add database indexes, cache widget data, or profile a Lar

• planning

  Use when the user asks to plan, spec, or design a Filament feature before building it — "plan an order management system", "write a spec for the customer panel", "create an implementation plan" — or before any multi-resource implementation, or when an implementing agent will work from the plan in a

• plugin-dev

  Use when building a redistributable Filament package rather than app code — a plugin class registering resources/pages/widgets into someone else's panel, a standalone package shipping custom form fields or table columns, a whole panel distributed via Composer, per-panel plugin configuration, plugin

• resources

  Use when building or editing a Filament resource — CRUD scaffolding, List/Create/Edit/View pages, save lifecycle hooks, list tabs, relation managers, nested or singular resources, global search, soft-delete restore/force-delete — or when a resource is missing from navigation, a record 404s, a lifecy

• review

  Use when auditing or reviewing existing Filament code — pre-deploy checks, PR review of app/Filament changes, "is this admin panel secure/fast", after an upgrade, or when asked to find bugs, N+1 queries, security holes, or convention violations in Filament resources, panels, or forms.

• schemas

  Use when building or editing Filament forms, infolists, or layouts — form fields, field validation, reactive/dependent fields (Get/Set, live), sections, tabs, grids, wizards, view-page infolists — or when fields are too narrow, a form saves wrong data, dependent selects don't update, or Get/Set impo

• tables

  Use when building or editing Filament tables — columns, filters, sorting, searching, grouping, summaries, row/bulk/header actions placement, pagination, reordering, or when a table is slow (N+1 queries), search doesn't find relationship values, filters don't apply, or bulk actions are missing. Also

• tenancy

  Use when a Filament panel serves multiple teams, organizations or workspaces — configuring ->tenant(), the HasTenants contract, tenant registration or profile pages, tenant-scoped resources — or when one tenant's records leak into another, a user reaches another tenant's data by editing the URL, uni

• testing

  Use when writing or fixing tests for Filament code — resources, pages, forms, tables, actions, notifications, relation managers, widgets — or when Filament tests fail with method-not-found on helpers like assertFormSet/callTableAction (v3 names), authorization always failing in tests, multi-panel/te

• upgrade

  Use when a project runs Filament v2/v3 (or when upgrading any Filament major — v3→v4, v4→v5), when legacy code uses Filament\Tables\Actions, BadgeColumn, ->reactive(), form(Form $form), Filament\Forms\Get, or when tests fail after an upgrade with method-not-found on assertFormSet/callTableAction. Pr

• ux

  Use when a Filament form, page, or dashboard must look and feel professional — CRM/ERP-grade UI, "make it beautiful", redesigning ugly or flat generated forms, improving UX, layout polish, dashboard composition — or whenever creating any non-trivial form/dashboard so it never ships with the raw gene

• widgets

  Use when building or debugging Filament dashboard widgets — stats overviews, Chart.js charts, table widgets, custom Blade widgets — or widgets on resource pages, dashboard grid columns and column spans, widget polling and lazy loading, chart filters, or dashboard-wide filter forms. Also for "my widg

Slash commands (10)

• /filament:audit

  Audit Filament code for security, version correctness, performance, UX, and test gaps

• /filament:diagnose

  Diagnose a Filament error or misbehavior (component not found, changes not appearing, 403s, upload issues, slow tables) from symptom to verified fix

• /filament:docs

  Look up official Filament documentation (vendored v5 docs, Boost search-docs, or live site) and answer with citations

• /filament:init

  Scan the current Laravel project and generate its Filament spec file (versions, run commands, panels, resources, per-package usage docs, custom components) — into .filament.claude.md by default (auto-imported from CLAUDE.md) or any file you name; "sync" sets up composer auto-refresh

• /filament:make

  Build a Filament artifact (resource, form, table, action, widget, page, relation manager, importer/exporter) grounded in the real model + migrations

• /filament:plan

  Produce an implementation-ready Filament feature spec (models, resources, authorization, tests) before writing any code

• /filament:rescan

  Rescan the current project (new packages, new custom fields/columns/widgets, new resources/panels) and refresh the Filament spec block — documenting anything new, preserving existing package docs

• /filament:status

  Inspect the current Laravel app's Filament setup — versions, panels, resources, tooling, optimization signals — and report health + recommendations

• /filament:test

  Generate and run Pest tests for a Filament resource, page, action, or relation manager

• /filament:upgrade-app

  Upgrade the app across Filament majors (v2→v3→v4→v5) with the automated scripts, manual deltas, and post-upgrade verification

Subagents (3)

• filament-engineer

  Implements Filament features end-to-end — resources, forms, tables, actions, widgets, panels, relation managers — from a request or a written plan. Use PROACTIVELY for any multi-file Filament implementation task. Produces scaffolded, version-correct, tested, pint-formatted code.

• filament-planner

  Produces implementation-ready Filament feature specs (models, resources, schemas, authorization, tests) that another agent can build without making decisions. Use when the user wants a plan or spec before implementation, or before any multi-resource feature.

• filament-reviewer

  Read-only auditor for Filament code — security (policies, tenancy isolation, uploads, XSS), version correctness (v3 leftovers), performance (N+1, unbounded selects), UX and test coverage. Use PROACTIVELY after significant app/Filament changes, before deploys, and after upgrades. Reports findings; ne

Hooks (3)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/session-context.sh"

• UserPromptSubmit

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/response-style.sh"

• PostToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/scripts/namespace-guard.sh"

Similar plugins