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
- majdghithan/agent-skillstheir own version, first seen Jul 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- majdghithan/agent-skills★ 7same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- ast-grepSkill
- branch-review-before-prSkill
- browse-qaSkill
- browser-useSkill
- browseSkill
- bugfixSkill
- build-dmgSkill
- claude-reviewSkill
- codemapSkill
- code-simplifySkill
- codex-reviewSkill
- commitSkill
- cost-estimateSkill
- create-prSkill
- find-agentsSkill
- find-bugsSkill
- frontend-design-ui-uxSkill
- git-merge-expertSkill
- git-merge-expert-worktreeSkill
- kiro-reviewSkill
- laravelSkill
- lokeiSkill
- map-project-monorepoSkill
- map-projectSkill
- nextjsSkill
- plan-founder-reviewSkill
- plan-to-task-list-with-dagSkill
- pr-retroSkill
- run-parallel-agents-feature-buildSkill
- run-parallel-agents-feature-debugSkill
- rustSkill
- secretsSkill
- startSkill
- update-agent-learningsSkill
- update-claude-learningsSkill
- update-claude-settingsSkill
- update-skill-learningsSkill
- ast-grepSkill
- branch-review-before-prSkill
- codemapSkill
- code-simplifySkill
- commitSkill
- cost-estimateSkill
- create-prSkill
- find-bugsSkill
- frontend-design-ui-uxSkill
- git-merge-expertSkill
- git-merge-expert-worktreeSkill
- map-project-monorepoSkill
- map-projectSkill
- plan-founder-reviewSkill
- plan-to-task-list-with-dagSkill
- pr-retroSkill
- run-parallel-agents-feature-buildSkill
- run-parallel-agents-feature-debugSkill
- startSkill
- update-agent-learningsSkill
- The first 60 shown.
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
- Very specific: line 16
Unified action namespace: ALL actions import from Filament\Actions\* — never Filament\Tables\Actions\* or Filament\Forms\Actions\*.
- Very specific: line 17
Table methods changed: Use ->recordActions() not ->actions().
- Very specific: line 18
No BadgeColumn: Use TextColumn::make('status')->badge()->color(...).
- Distinctive: line 29
Before writing ANY Filament code, you MUST complete this checklist:
- Very specific: line 31
Read references/namespaces.md to understand the v5 import map
- Distinctive: line 33
Read the matching reference file(s)
- Distinctive: line 34
Only then begin implementation
- Very specific: line 61
ALL actions: use Filament\Actions\{Action, EditAction, DeleteAction, BulkAction, BulkActionGroup, ...} — one namespace.
≈ “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.
Files
<EXTREMELY-IMPORTANT>
These rules apply to ALL Filament code you write. Violating any produces broken admin panels.- Unified action namespace. ALL actions import from
Filament\Actions\*— neverFilament\Tables\Actions\*orFilament\Forms\Actions\*. These old namespaces DO NOT EXIST in v5. - Table methods changed. Use
->recordActions()not->actions(). Use->toolbarActions()not->bulkActions(). The v3 method names DO NOT EXIST in v5. - No BadgeColumn. Use
TextColumn::make('status')->badge()->color(...).BadgeColumnwas removed. - Schemas package. Layout components come from
Filament\Schemas\Components\*(Section, Grid, Tabs, Wizard). Form fields stay inFilament\Forms\Components\*. Infolist entries stay inFilament\Infolists\Components\*. - No business logic in Resources. Custom actions delegate to project Action classes:
->action(fn ($record) => app(SomeAction::class)->execute($record)). - Schema/Table class extraction. Resources delegate to separate schema and table classes for maintainability. Keep
form()andtable()methods as one-liners that callSomeForm::configure($schema). - 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:
- Read
references/namespaces.mdto understand the v5 import map - Identify the task type from the routing table below
- Read the matching reference file(s)
- Only then begin implementation
Writing Filament code without reading the reference = wrong namespaces, wrong methods, rework.
Routing Table
| Task | Read |
| Understanding v5 namespace changes from v3 | references/namespaces.md |
| Creating or editing a Resource | references/resources.md |
| Form fields, validation, layout | references/forms.md |
| Table columns, sorting, searching | references/tables.md |
| Table/page/bulk actions, modals, confirmations | references/actions.md |
| Filters (select, ternary, custom) | references/filters.md |
| Relation managers, relationships in forms | references/relationships.md |
| Widgets (stats, charts) | references/widgets.md |
| Navigation, panels, theming | references/panels.md |
| Notifications (flash, database, broadcast) | references/notifications.md |
| Testing Filament resources and pages | references/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:
- ALL actions:
use Filament\Actions\{Action, EditAction, DeleteAction, BulkAction, BulkActionGroup, ...}— one namespace. - Table methods:
->recordActions([...]),->toolbarActions([...]),->headerActions([...])— never->actions()or->bulkActions(). - Badge columns:
TextColumn::make('field')->badge()->color(fn ($state) => ...)— noBadgeColumnclass. - Layout:
Filament\Schemas\Components\{Section, Grid, Tabs, Wizard}. - Form fields:
Filament\Forms\Components\{TextInput, Select, Toggle, ...}. - Infolist entries:
Filament\Infolists\Components\{TextEntry, IconEntry, ...}. - Table columns:
Filament\Tables\Columns\{TextColumn, IconColumn, ImageColumn, ...}. - Filters:
Filament\Tables\Filters\{Filter, SelectFilter, TernaryFilter}. - Custom actions delegate to Action classes — no business logic in Resources.
- Policies are auto-detected — no manual authorization wiring needed.
v5 Breaking Changes from v3 (Quick Summary)
| v3 | v5 | Notes |
Tables\Actions\EditAction | Filament\Actions\EditAction | Unified action namespace |
Tables\Actions\Action | Filament\Actions\Action | Same class, different namespace |
Tables\Actions\BulkActionGroup | Filament\Actions\BulkActionGroup | Unified |
Tables\Actions\DeleteBulkAction | Filament\Actions\DeleteBulkAction | Unified |
->actions([...]) | ->recordActions([...]) | Table method renamed |
->bulkActions([...]) | ->toolbarActions([BulkActionGroup::make([...])]) | Bulk actions live in toolbar |
->headerActions([...]) | ->headerActions([...]) | Unchanged |
Tables\Columns\BadgeColumn | TextColumn::make()->badge() | BadgeColumn removed |
Forms\Components\Section | Filament\Schemas\Components\Section | Layout → Schemas package |
Forms\Components\Grid | Filament\Schemas\Components\Grid | Layout → Schemas package |
Forms\Components\Tabs | Filament\Schemas\Components\Tabs | Layout → Schemas package |
Form $form (in resource) | Schema $schema | Type hint changed |
$form->schema([...]) | $schema->components([...]) | Method renamed |
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
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.

