agentleFS
ulpi-ioulpi-io/browse/.agents/skills/laravel-filament/SKILL.md

laravel-filament

Skill15 starsChanged 8 months agoApache-2.0View on GitHub

Filament v5 admin panel — resources, schemas, tables, actions, relation managers, widgets, navigation, and panels. Use when working on any Filament resource, form, table, action, filter, widget, page, or panel configuration task.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Unified action namespace: ALL actions import from Filament\Actions\* — never Filament\Tables\Actions\* or Filament\Forms\Actions\*.

    line 16
  2. Very specific:

    Table methods changed: Use ->recordActions() not ->actions().

    line 17
  3. Very specific:

    No BadgeColumn: Use TextColumn::make('status')->badge()->color(...).

    line 18
  4. Distinctive:

    Before writing ANY Filament code, you MUST complete this checklist:

    line 29
  5. Very specific:

    Read references/namespaces.md to understand the v5 import map

    line 31
  6. Distinctive:

    Read the matching reference file(s)

    line 33
  7. Distinctive:

    Only then begin implementation

    line 34
  8. Very specific:

    ALL actions: use Filament\Actions\{Action, EditAction, DeleteAction, BulkAction, BulkActionGroup, ...} — one namespace.

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<EXTREMELY-IMPORTANT> These rules apply to ALL Filament code you write. Violating any produces broken admin panels.
  1. Unified action namespace. ALL actions import from Filament\Actions\* — never Filament\Tables\Actions\* or Filament\Forms\Actions\*. These old namespaces DO NOT EXIST in v5.
  2. Table methods changed. Use ->recordActions() not ->actions(). Use ->toolbarActions() not ->bulkActions(). The v3 method names DO NOT EXIST in v5.
  3. No BadgeColumn. Use TextColumn::make('status')->badge()->color(...). BadgeColumn was removed.
  4. Schemas package. Layout components come from Filament\Schemas\Components\* (Section, Grid, Tabs, Wizard). Form fields stay in Filament\Forms\Components\*. Infolist entries stay in Filament\Infolists\Components\*.
  5. No business logic in Resources. Custom actions delegate to project Action classes: ->action(fn ($record) => app(SomeAction::class)->execute($record)).
  6. Schema/Table class extraction. Resources delegate to separate schema and table classes for maintainability. Keep form() and table() methods as one-liners that call SomeForm::configure($schema).
  7. Filters stay in Tables namespace. Filament\Tables\Filters\* is correct. Only actions moved to the unified namespace.</EXTREMELY-IMPORTANT>

Filament v5 Admin Panel

MANDATORY FIRST RESPONSE PROTOCOL

Before writing ANY Filament code, you MUST complete this checklist:

  1. Read references/namespaces.md to understand the v5 import map
  2. Identify the task type from the routing table below
  3. Read the matching reference file(s)
  4. Only then begin implementation

Writing Filament code without reading the reference = wrong namespaces, wrong methods, rework.

Routing Table

TaskRead
Understanding v5 namespace changes from v3references/namespaces.md
Creating or editing a Resourcereferences/resources.md
Form fields, validation, layoutreferences/forms.md
Table columns, sorting, searchingreferences/tables.md
Table/page/bulk actions, modals, confirmationsreferences/actions.md
Filters (select, ternary, custom)references/filters.md
Relation managers, relationships in formsreferences/relationships.md
Widgets (stats, charts)references/widgets.md
Navigation, panels, themingreferences/panels.md
Notifications (flash, database, broadcast)references/notifications.md
Testing Filament resources and pagesreferences/testing.md
Infolists (read-only detail views)references/infolists.md

Multiple tasks? Read multiple files.

Quick Rules

These repeat the critical guardrails for context-window resilience:

  1. ALL actions: use Filament\Actions\{Action, EditAction, DeleteAction, BulkAction, BulkActionGroup, ...} — one namespace.
  2. Table methods: ->recordActions([...]), ->toolbarActions([...]), ->headerActions([...]) — never ->actions() or ->bulkActions().
  3. Badge columns: TextColumn::make('field')->badge()->color(fn ($state) => ...) — no BadgeColumn class.
  4. Layout: Filament\Schemas\Components\{Section, Grid, Tabs, Wizard}.
  5. Form fields: Filament\Forms\Components\{TextInput, Select, Toggle, ...}.
  6. Infolist entries: Filament\Infolists\Components\{TextEntry, IconEntry, ...}.
  7. Table columns: Filament\Tables\Columns\{TextColumn, IconColumn, ImageColumn, ...}.
  8. Filters: Filament\Tables\Filters\{Filter, SelectFilter, TernaryFilter}.
  9. Custom actions delegate to Action classes — no business logic in Resources.
  10. Policies are auto-detected — no manual authorization wiring needed.

v5 Breaking Changes from v3 (Quick Summary)

v3v5Notes
Tables\Actions\EditActionFilament\Actions\EditActionUnified action namespace
Tables\Actions\ActionFilament\Actions\ActionSame class, different namespace
Tables\Actions\BulkActionGroupFilament\Actions\BulkActionGroupUnified
Tables\Actions\DeleteBulkActionFilament\Actions\DeleteBulkActionUnified
->actions([...])->recordActions([...])Table method renamed
->bulkActions([...])->toolbarActions([BulkActionGroup::make([...])])Bulk actions live in toolbar
->headerActions([...])->headerActions([...])Unchanged
Tables\Columns\BadgeColumnTextColumn::make()->badge()BadgeColumn removed
Forms\Components\SectionFilament\Schemas\Components\SectionLayout → Schemas package
Forms\Components\GridFilament\Schemas\Components\GridLayout → Schemas package
Forms\Components\TabsFilament\Schemas\Components\TabsLayout → Schemas package
Form $form (in resource)Schema $schemaType hint changed
$form->schema([...])$schema->components([...])Method renamed

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.