Skip to main content
Start by asking the agent to activate media-studio-development and inspect the installed package versions. Include the integration boundary and constraints in the request. The skill is a maintained guide, not permission to alter production storage, run paid AI calls or publish your packages.

Build a native Filament picker

The expected boundary is Studio’s native Filament adapter. FLEX Fields should not be installed to satisfy this request. For the opposite requirement, explicitly ask for the existing FLEX FlexFileUpload::mediaStudio() integration and preserve its native field appearance/asset lifecycle.

Configure optional thumbnails

The agent should distinguish document thumbnails from browser preview and OCR, check Poppler/libvips capability, and avoid generating thumbnails in a list request. See document thumbnails for the actual implementation.

Configure AI without enabling unrelated systems

The skill separates search.content.ocr, intelligence, Meilisearch embeddings and assistant. Configuring one should not switch on the others or claim exactly-once billing.

Review the generated result

Require actual installed method signatures, durable reference persistence, server-side permission/tenant checks and the relevant negative cases. For frontend changes, verify strict TypeScript, mount/unmount lifecycle and the real interaction. For PHP fields, test saved state after deletion/replacement of media. Separate simulated provider behavior from a real cloud test, and report limits instead of claiming universal performance or complete AI understanding. For product runtime operations, use MCP with its own credentials and permissions. Boost development instructions do not grant access to that API.