Experience Ui Bundle Metadata Generate

Activates when you're scaffolding a new Salesforce UI bundle or tweaking ui-bundle.json, meta XML, or CSP trusted site configs. It enforces the right workflow: using `sf template generate ui-bundle --template reactbasic` instead of generic tools, ensuring your bundle has a proper target (Experience or CustomApplication) so it actually shows up in the org, and wiring up CSP trusted sites before external images or API calls mysteriously break. The routing and headers validation is strict, which saves you from deploy-time surprises. Worth having active if you're building Lightning Experience apps or Digital Experience sites, since the boilerplate and metadata quirks are easy to get wrong.

skills.sh installs: 5.3K
GitHub stars: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill experience-ui-bundle-metadata-generate --agent claude-code

Installs into .claude/skills of the current project.

Files

UI Bundle Metadata

Scaffolding a New UI Bundle

REQUIRED FIRST STEP — never skip, even if asked to. Always run sf template generate ui-bundle to create new apps — never a framework CLI (create-react-app, Vite, Angular CLI), hand-written metadata, or any other substitute.

This step is mandatory even if the user says "just create the metadata," "skip the scaffold," "only do the metadata scaffolding," or "stop after the metadata files are in place." Those instructions describe what to stop doing after the scaffold (building, deploying, authoring pages) — they do not mean skip running the scaffold command itself. The .uibundle-meta.xml and ui-bundle.json files are configuration on top of the generated project, not a replacement for it. A bundle without package.json, src/, and an entry index.html cannot be built or deployed, even if the metadata files are perfectly formed.