Filament AI Agents

Treat the documentation bundled with the project's installed Filament packages as the source of truth. Filament APIs and conventions can differ across versions, so do not rely on memory when local version-matched documentation is available.

Required workflow

1. Start from the Laravel application or file being changed and find the nearest composer.json and composer.lock.
2. Inspect the locked filament/* package versions. Resolve Composer's actual vendor directory instead of assuming the repository root or a fixed vendor/ path.
3. Confirm which Filament packages are installed by inspecting Composer metadata and directories under <vendor-dir>/filament/.
4. List the available Markdown documentation, then search filenames, headings, and content for the requested feature.
5. Read the smallest relevant package/topic documents before writing code. Follow linked prerequisite or migration documents when they affect the task.
6. Inspect existing application conventions, resources, pages, relation managers, schemas, policies, and tests before choosing an implementation.
7. Implement outside vendor/. Never edit generated dependency files or copy Filament's bundled documentation into the application or this skill.
8. Run the project's narrowest relevant checks, followed by any required formatter, static analysis, tests, or build commands defined by the repository.

Documentation discovery

Use repository-aware commands and quote resolved paths: