F
Filament•4d ago
bouly

Rules for Laravel Boost (MCP)

Hello, I use Windsurf IDE with Claude Sonnet to generate my Filament code. The problem is that it generally follows version v3 and not v4 (file structure, use of Form instead of Schema, etc.). Do you know where I could find an effective rules file to help the AI undxerstand the Filament v4 documentation? I found that, but it is not sufficient 
- Validation rule `unique()` has `ignoreRecord: true` by default, no need to specify it.
- Don't use full namespaces when referencing Filament classes like `Filament\Forms\Components\DatePicker`. Always put the namespaces in `use` section on top and use only classname instead of full path.
- If you create custom Blade files with Tailwind classes, you need to create a custom theme and specify the folder of those Blade files in theme.css.
- Table Filters have `->schema()` instead of `->form()`
- `Action::make()` has `->schema()` instead of `->form()`
- Table has `->toolbarActions()` instead of `->bulkActions()`
- `$navigationGroup` in ressources must be of type UnitEnum|string|null.
- Validation rule `unique()` has `ignoreRecord: true` by default, no need to specify it.
- Don't use full namespaces when referencing Filament classes like `Filament\Forms\Components\DatePicker`. Always put the namespaces in `use` section on top and use only classname instead of full path.
- If you create custom Blade files with Tailwind classes, you need to create a custom theme and specify the folder of those Blade files in theme.css.
- Table Filters have `->schema()` instead of `->form()`
- `Action::make()` has `->schema()` instead of `->form()`
- Table has `->toolbarActions()` instead of `->bulkActions()`
- `$navigationGroup` in ressources must be of type UnitEnum|string|null.
Thank you!
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?