Experience Ui Bundle Deploy

This handles the full deployment pipeline for Salesforce UI bundles, and the order matters more than you'd think. It walks through org auth, pre-deploy builds, metadata deployment, permission set assignment, optional data import, and GraphQL schema fetching with codegen. The critical insight here is that it enforces the right sequence: you have to deploy metadata before fetching the schema, assign permissions before introspection will return custom fields, and re-run codegen after every deploy that touches objects or permissions. It'll proactively discover and assign permission sets from your project after deployment, which saves you from the usual "why isn't this working" troubleshooting loop when users lack field-level security.

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-deploy --agent claude-code

Installs into .claude/skills of the current project.

Files

Deploying a UI Bundle App

Deploy order is load-bearing: a step's output is the next step's precondition (deploy before schema fetch; permissions before schema fetch; role/self-reg before the schema the guest user must see). This is the canonical setup sequence, ported from the reference org-setup.mjs. The org-setup.mjs line citations in references/ are port-provenance (why each rule exists) pointing at that external reference script — not files shipped with this skill — so you don't need to open them to run the steps.

Run each step in order. Every optional step is presence-driven: if its convention file is absent, no-op cleanly and move on — do not fabricate config. For the two destructive/expensive steps (self-registration, data import), ask the user before running.