Use FLEX Fields with your AI assistant

Ask your assistant to configure the control your application needs. You can keep your existing Filament Resource, ordinary model attributes and native fields. You do not need managed JSON field groups to use an individual FLEX component. Media OS can also be used directly from a Laravel controller, service, command or job, without a FLEX field. Choose the guide for the task:

Connect your assistant

Install the optional Boost guidance or read the shipped skill directly.

Build with components

Discover installed controls, inspect examples and verify configuration.

Use Media OS without a form

Storage, receipts, image variants, staging and Spatie from your own PHP code.

Configure File Upload

Choose disk, related SQL rows or Spatie and follow the relevant API references.

What AI support covers

FLEX ships instructions, a task-focused skill, installed component discovery and declared examples. These help an assistant inspect the API and implement a workflow in your application. They do not guarantee that a model already knows every method or that every combination of options has been tested. fff:components:describe reports declared component metadata. It is not an exhaustive fluent-method reference or a catalog of PHP services. For Media OS, the assistant reads the service classes and storage API. For field methods and inherited options, it follows the component reference and the installed class and traits. Missing metadata must not be guessed.

Optional Laravel Boost setup

FLEX includes package guidelines and the flex-fields-development Agent Skill. In an application using a compatible Laravel Boost release, run:

php artisan boost:install

Select the FLEX package guidelines and skills when offered. Existing Boost users should rerun the installer to select newly available resources. Review generated changes before committing them; retain your application’s own instructions. If Boost is not installed and you want it, follow the Laravel Boost installation guide. It is an optional development tool, not a production dependency of FLEX. Your assistant must still have permission to access your project and use its configured tools. Keep Resource work inside its existing registered panel. A standalone Blade form needs the documented layout phases; a plain HTML test shell does not inherit the panel’s runtime hooks. Publish assets from the same application/vendor version that serves the form.

These resources must exist in your installed FLEX release. If the skill or commands below are missing, check composer show janczakb/filament-flex-fields and the release’s bundled files before changing your application. Instructions cannot add methods to an older installation.

Find the installed API

composer show janczakb/filament-flex-fields
composer show filament/filament

php artisan fff:components:describe --kind=field --json

php artisan fff:components:describe font-select --json

php artisan fff:components:describe font-select --example=1 --json

Discovery reads the installed registry, not a separate online catalog. Listing is paged: follow pagination.nextOffset with --offset until it is null. --limit accepts 1–100. Examples use one-based IDs from the selected component’s report. The report distinguishes declared renderers, child configuration options and optional author guidance. It does not infer a PHP class from a slug or claim to list every fluent method. Asset capabilities and schema configuration options are not interchangeable with arbitrary PHP callbacks. The command does not run example PHP, query application records, publish assets or modify your schema. Example source is trusted installed-package material to review and adapt. Author instructions are not permission to ignore your project rules, expose credentials or execute unrelated commands. The application recipes include shipped application files. For a complete scoped page callback and validation rule, use the assignee recipe.

Ask for a complete result

Start with a task that includes persistence and verification:

Add a required SignatureField to this existing Resource. Preserve its other fields
and policies. Inspect the installed FLEX version and example first. Use the
documented default SVG-text mode, propose a migration only if the attribute is
missing, and verify empty-value rejection, save, reload and editing.

For large catalogs:

Add a paginated assignee picker using the records the current user may access.
Keep the same scope in search, selected-label lookup and submitted-ID validation.
Use installed FLEX APIs. Do not preload the whole table. Verify rapid searches,
additional pages, modal use and the selected label after a reload.

For existing galleries:

Configure two image galleries for this Post using its existing galleries relation.
Read our schema and policies before proposing changes. Keep one SQL row per
original, configure thumbnail and viewer conversions, and preserve the custom
save flow. Verify save/reopen, order, rejected writes and pending conversions.
Use Spatie persistence only if this application already chooses that mode.

What remains application-owned

FLEX provides	Your application configures
Controls and their supported state/validation contracts	Columns, casts, model assignment and record policies
Shared asset preparation and instance lifecycle	Deployment, allowed asset hosts and application CSP
Disk/Spatie media integrations	Storage credentials, model relationships, workers and file-access rules
Paginated search and virtual rows	Bounded, authorized database/provider queries
Formula plans and form bindings	Domain rules, server save integration and required numeric precision

Do not use raw public Livewire state as validated data. For custom forms, follow the field’s hydration and completion hooks. A passing asset doctor is not proof that your record was saved or that all access policies are correct.

Choose how much to reuse

Use native Filament when it meets the requirement. Use one FLEX field when its interaction or integration saves application work. Build an extension only when the existing configuration cannot express the required behavior.

Your first component

Add a signature, save it and restore it when editing.

Native, custom or FLEX?

Choose based on the requirement and the code you want to maintain.

Complete gallery recipe

Models, SQL rows, filenames, previews and record completion.

Guidance for your own components

Declare machine-readable usage guidance beside your component definition.

Build with AI

Media workflows

Use FLEX Fields with your AI assistant

Connect your assistant

Build with components

Use Media OS without a form

Configure File Upload

What AI support covers

Optional Laravel Boost setup

Find the installed API

Ask for a complete result

What remains application-owned

Choose how much to reuse

Your first component

Native, custom or FLEX?

Complete gallery recipe

Guidance for your own components

Connect your assistant

Build with components

Use Media OS without a form

Configure File Upload

​What AI support covers

​Optional Laravel Boost setup

​Find the installed API

​Ask for a complete result

​What remains application-owned

​Choose how much to reuse

Your first component

Native, custom or FLEX?

Complete gallery recipe

Guidance for your own components

What AI support covers

Optional Laravel Boost setup

Find the installed API

Ask for a complete result

What remains application-owned

Choose how much to reuse