Non-negotiable rules:
- Read
references/namespaces.md 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
references/, not inline here.
laravel-filament
Inputs
$request: 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 |
references/namespaces.md |
| Creating or editing a Resource (CRUD) |
references/resources.md |
| Form fields, sections, layout |
references/forms.md |
| Table columns, sorting, searching |
references/tables.md |
| Bulk actions, row actions, header actions |
references/actions.md |
| Table filters, filter forms |
references/filters.md |
| Relation managers, BelongsToMany, HasMany |
references/relationships.md |
| Dashboard widgets, stats, charts |
references/widgets.md |
| Multi-panel setup, navigation, tenancy |
references/panels.md |
| Flash messages, database notifications |
references/notifications.md |
| Infolist entries, read-only views |
references/infolists.md |
| Testing resources, pages, actions |
references/testing.md |
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
Filament\\Actions\\*
- tables use the v5 record/toolbar/header action methods
- badge presentation uses
TextColumn->badge()
- 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
SKILL.md.
- Do not skip
references/namespaces.md.
- Do not use v3 action namespaces or deprecated table methods.
- Do not put business logic directly in Resource classes.
When To Load References
Output Contract
Report:
- which Filament references were loaded
- the v5 pattern applied
- the change made
- the verification run
1---
2name: laravel-filament
3version: 2.1.0
4description: |
5 Build Filament admin panels on the v5 API surface THIS project targets, not deprecated v3
6 patterns — a reference carrying the current namespaces and conventions for Resources, forms,
7 tables, actions, filters, relation managers, widgets, infolists, panels, and testing, with
8 business logic kept in application Actions, so a change lands idiomatic and review-ready
9 instead of tripping over renamed APIs. Use when a task touches this project's Filament admin
10 panels and should target the v5 surface rather than deprecated patterns.
11allowed-tools:
12 - Bash
13 - Read
14 - Write
15 - Edit
16 - Grep
17argument-hint: "[Filament resource, form, table, widget, or panel task]"
18arguments:
19 - request
20when_to_use: |
21 Use when the task is specifically about Filament resources, forms, tables, actions, filters,
22 relation managers, widgets, navigation, or panel configuration. Examples: "fix this Filament
23 table action", "create a Resource", "update Filament filters", "add an admin widget". Do NOT
24 use for general Laravel application code — routes, APIs, Eloquent, queues (laravel); this is the
25 admin-panel surface only.
26effort: high
27metadata:
28 source: https://skillmd.com/skills/ulpi-io/laravel-filament
29---
30
31<EXTREMELY-IMPORTANT>
32This skill exists to keep Filament work aligned with v5, not to duplicate the entire reference library.
33
34Non-negotiable rules:
351. Read `references/namespaces.md` first.
362. Then load only the reference files the task actually needs.
373. Keep business logic out of Resources.
384. Use the v5 action and table APIs, not old v3 patterns.
395. Keep the heavy Filament cookbook in `references/`, not inline here.
40</EXTREMELY-IMPORTANT>
41
42# laravel-filament
43
44## Inputs
45
46- `$request`: The Filament admin task or component to modify
47
48## Goal
49
50Route Filament work through the correct v5 conventions so the implementation uses the right namespaces, table APIs, and admin-panel composition patterns.
51
52## Step 0: Read the v5 namespace contract
53
54Always start with:
55
56- `references/namespaces.md`
57
58That establishes the namespace and API changes that commonly break Filament work.
59
60**Success criteria**: The task is grounded in the correct Filament v5 surface before editing.
61
62## Step 1: Load only the relevant admin references
63
64Use the routing table to pick reference files. Do not bulk-load everything.
65
66| Task | Read |
67|------|------|
68| v5 namespace and API changes | `references/namespaces.md` |
69| Creating or editing a Resource (CRUD) | `references/resources.md` |
70| Form fields, sections, layout | `references/forms.md` |
71| Table columns, sorting, searching | `references/tables.md` |
72| Bulk actions, row actions, header actions | `references/actions.md` |
73| Table filters, filter forms | `references/filters.md` |
74| Relation managers, BelongsToMany, HasMany | `references/relationships.md` |
75| Dashboard widgets, stats, charts | `references/widgets.md` |
76| Multi-panel setup, navigation, tenancy | `references/panels.md` |
77| Flash messages, database notifications | `references/notifications.md` |
78| Infolist entries, read-only views | `references/infolists.md` |
79| Testing resources, pages, actions | `references/testing.md` |
80
81Multiple tasks? Read multiple files.
82
83**Success criteria**: Only the task-relevant Filament conventions are in the active context.
84
85## Step 2: Implement with the core Filament guardrails
86
87Keep these rules active:
88
89- actions come from `Filament\\Actions\\*`
90- tables use the v5 record/toolbar/header action methods
91- badge presentation uses `TextColumn->badge()`
92- layout components come from the Schemas package
93- Resource classes delegate real business work to application Actions
94
95**Success criteria**: The change uses valid v5 APIs and stays maintainable.
96
97## Step 3: Verify the admin surface
98
99Use the narrowest relevant verification:
100
101- focused feature tests
102- Filament page/resource tests
103- lightweight UI smoke coverage if the repo already has it
104
105**Success criteria**: The Filament surface still behaves correctly after the change.
106
107## Guardrails
108
109- Do not inline the whole Filament handbook in `SKILL.md`.
110- Do not skip `references/namespaces.md`.
111- Do not use v3 action namespaces or deprecated table methods.
112- Do not put business logic directly in Resource classes.
113
114## When To Load References
115
116- `references/namespaces.md`
117 Always.
118
119- then only the task-relevant files under `references/`
120
121## Output Contract
122
123Report:
124
1251. which Filament references were loaded
1262. the v5 pattern applied
1273. the change made
1284. the verification run