Agent skill · forcedotcom
experience-ui-bundle-file-upload-generate
MUST activate when the project contains a uiBundles/*/src/ directory and the task involves uploading, attaching, or dropping files. Use this skill when adding file upload functionality to a UI bundle app. Provides progress tracking and Salesforce ContentVersion integration. This feature provides programmatic APIs ONLY — build custom UI using the upload() API. ALWAYS use this instead of building file upload from scratch with FormData or XHR.
What it needs
About 6k tokens when loaded.
What this skill does
File Upload API (workflow) When the user wants file upload functionality in a React UI bundle, follow this workflow. This feature provides APIs only — you must build the UI components yourself using the provided APIs. CRITICAL: This is an API-only package The package exports programmatic APIs, not React components or hooks. You will: Use the upload() function to handle file uploads with progress tracking Build your own custom UI (file input, dropzone, progress bars, etc.) Track upload progress through the onProgress callback Do NOT: Expect pre-built components like <FileUpload /> — they are not exported Try to import React hooks like useFileUpload — they are not exported Look for dropzone components — they are not exported The source code contains reference components for demonstration, but they are not available as imports. Use them as examples to build your own UI. 1. Install the package Dependencies are automatically installed: @salesforce/ui-bundle (API client) @salesforce/platform-sdk (data SDK; the old @salesforce/sdk-data name is dead — see the experience-ui-bundle-salesforce-data-access skill) 2. Understand the three upload patterns Pattern A: Basic upload (no record linking) Upload files to Salesforce and get back contentBodyId for each file. No ContentVersion record is created. When to use: User wants to upload files first, then create/link them to a record later Building a multi-step form where the record doesn't exist yet Deferred record linking scenarios Pattern B: Upload with immediate record linking Upload files and immediately link them to an existing Salesforce record by creating ContentVersion records. When to use: Record already exists (Account, Opportunity, Case, etc.) User wants files immediately attached to the record Direct upload-and-attach scenarios Pattern C: Deferred record linking (record creation flow) Upload files without a record, then link them after the record is created. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/experience-ui-bundle-file-upload-generate--c529bb