<EXTREMELY-IMPORTANT>
This skill exists to keep Filament work aligned with v5, not to duplicate the entire reference library.
Non-negotiable rules:
- Read first.
- Then load only the reference files the task actually needs.
- Keep business logic out of Resources.
- Use the v5 action and table APIs, not old v3 patterns.
- Keep the heavy Filament cookbook in , not inline here.
</EXTREMELY-IMPORTANT>
laravel-filament
Inputs
- : The Filament admin task or component to modify
Goal
Route Filament work through the correct v5 conventions so the implementation uses the right namespaces, table APIs, and admin-panel composition patterns.
Step 0: Read the v5 namespace contract
Always start with:
That establishes the namespace and API changes that commonly break Filament work.
Success criteria: The task is grounded in the correct Filament v5 surface before editing.
Step 1: Load only the relevant admin references
Use the routing table to pick reference files. Do not bulk-load everything.
| Task | Read |
|---|
| v5 namespace and API changes | |
| Creating or editing a Resource (CRUD) | |
| Form fields, sections, layout | |
| Table columns, sorting, searching | |
| Bulk actions, row actions, header actions | |
| Table filters, filter forms | |
| Relation managers, BelongsToMany, HasMany | references/relationships.md
|
| Dashboard widgets, stats, charts | |
| Multi-panel setup, navigation, tenancy | |
| Flash messages, database notifications | references/notifications.md
|
| Infolist entries, read-only views | |
| Testing resources, pages, actions | |
Multiple tasks? Read multiple files.
Success criteria: Only the task-relevant Filament conventions are in the active context.
Step 2: Implement with the core Filament guardrails
Keep these rules active:
- actions come from
- tables use the v5 record/toolbar/header action methods
- badge presentation uses
- layout components come from the Schemas package
- Resource classes delegate real business work to application Actions
Success criteria: The change uses valid v5 APIs and stays maintainable.
Step 3: Verify the admin surface
Use the narrowest relevant verification:
- focused feature tests
- Filament page/resource tests
- lightweight UI smoke coverage if the repo already has it
Success criteria: The Filament surface still behaves correctly after the change.
Guardrails
- Do not inline the whole Filament handbook in .
- Do not skip .
- Do not use v3 action namespaces or deprecated table methods.
- Do not put business logic directly in Resource classes.
When To Load References
-
-
then only the task-relevant files under
Output Contract
Report:
- which Filament references were loaded
- the v5 pattern applied
- the change made
- the verification run