Describe the interaction, stored value and save behavior you need. Your assistant
can combine FLEX controls with native Filament fields in an existing Resource.
Managed JSON field groups are an optional storage approach.
Follow pagination.nextOffset when listing more than one page. Example IDs come
from the selected component’s report; an absent example is not permission to
invent one. The registry also contains supporting definitions, so its total is
not the marketing count of end-user controls.
The assistant then reads the component guide and installed PHP declarations for
the requested configuration, including inherited methods and closure signatures.
The component library links to the individual guides.
Does this cover every configuration?
The discovery command lists declared capabilities, examples and child-schema
options. It does not enumerate every fluent PHP method, callback or valid
combination. Author guidance is optional and may be absent. A missing renderer
is reported as unknown rather than inferred from a component ID.
An assistant must check the installed API and exercise the chosen workflow.
Instructions and examples reduce guessing; they do not certify every model’s
output or every component configuration.
Example request
For large record lists, specify the authorized search scope, pagination and
selected-label lookup. For media, first choose between an upload field
and a service without a form.
Verify the application’s result
Check the configured interaction, invalid values, record authorization, storage
format and save/reopen behavior. A successful asset doctor verifies published
files; it does not prove the application saved its record correctly.
Use the verification guide and working recipes
for application-level examples. Last modified on October 17, 2026
