laravel-filament

This skill exists to keep Filament work aligned with v5, not to duplicate the entire reference library.

Non-negotiable rules:

1. Read references/namespaces.md first.
2. Then load only the reference files the task actually needs.
3. Keep business logic out of Resources.
4. Use the v5 action and table APIs, not old v3 patterns.
5. 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:

• references/namespaces.md

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.

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

• references/namespaces.md Always.

• then only the task-relevant files under references/

Output Contract

Report:

1. which Filament references were loaded
2. the v5 pattern applied
3. the change made
4. the verification run