Laravel Filament v5 — Version-Matched, Official Components First

Use the project's installed Filament version as the compatibility target. Prefer the documented component for the current surface before creating custom markup, and use a documented escape hatch when no official equivalent fits.

Preflight — run before proposing or writing code

1. Honor the requested mode. Review or diagnose without editing unless the user asked for a change. For implementation, preserve unrelated work and inspect the current diff before modifying files.
2. Read project guidance and nearby code. Follow repository instructions, naming, architecture, localization, formatter, static-analysis, and testing conventions already in use.
3. Resolve the installed stack. Inspect composer.json and composer.lock for the exact filament/*, Laravel, Livewire, PHP, and plugin versions. Inspect package.json when theme or frontend assets matter. Prefer installed code in vendor/filament/ when an exact signature depends on a minor or patch release.
4. Map the operating context. Identify the panel, Resource/page/widget host, model relationships and casts, policies, tenant boundaries, custom theme, and relevant tests before choosing an API.
5. Separate facts from preferences. Treat official APIs and security boundaries as constraints. Treat composition recipes as starting heuristics that may yield to the domain, user workflow, or established project design.

If no project is available, state the assumed Filament 5.x context and keep examples focused rather than inventing surrounding architecture.

Mandatory component gate — run before writing markup

Before writing <div>, <span>, <pre>, @foreach, Tailwind classes, or a custom Blade view inside a Filament context: