SkillsAdd

ulpi-io/browse · Archived

laravel-filament

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.

First seen Jun 24, 2026

Installation

$ npx skills add ulpi-io/browse --skill laravel-filament
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

update-claude-learnings Same source
ulpi-io/browse

Extract learnings about Claude Code behavior from a session and add them to the project's CLAUD…

1 installs
git-merge-expert Same source
ulpi-io/browse

Expert in merging branches, resolving Git conflicts, worktree management, PR readiness checks, …

1 installs
find-bugs Same source
ulpi-io/browse

Use when the user asks to find bugs, review changes, security audit, or check code quality on t…

1 installs
cost-estimate Same source
ulpi-io/browse

Estimate development cost of a codebase (full repo, branch diff, or single commit). Invoke via …

1 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

filament-resource Similar name
mwguerra/claude-code-plugins

Generate FilamentPHP v4 resources with form, table, relation managers, and actions

1.2K installs
filament-pro Similar name
marcelorodrigo/agent-skills

Build Laravel admin panels with Filament v5. Use for creating resources, forms, tables, widgets…

1.1K installs
laravel-filament Similar name
ulpi-io/skills

Build Filament admin panels on the v5 API surface THIS project targets, not deprecated v3 patte…

406 installs
olakunlevpn-filament-skills Similar name
olakunlevpn/olakunlevpn-filament-skills

Use when writing, reviewing, or refactoring Filament PHP v5 code -- resources, forms, tables, i…

289 installs

Also in this package

Other skills from ulpi-io/browse.

npx skills add ulpi-io/browse
update-claude-learnings 1 git-merge-expert 1 find-bugs 1 cost-estimate 1

Browse all from ulpi-io/browse

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 1
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
Allowed toolsBash, Read

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,204 B
  • docs SUMMARY.md 255 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

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

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:

  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)

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