forcedotcom/sf-skills / plugins/builder/experience-react/skills/experience-ui-bundle-deploy
experience-ui-bundle-deploy
VerifiedMUST activate when the project has a uiBundles/*/src/ directory and the task involves deploying to an org or post-deploy org setup. Deploys a UI bundle app and runs ordered setup: org auth, build, metadata deploy, permission-set and role assignment, Experience Cloud self-registration, social login / SSO / IDP linking (Auth Providers + SAML on a React site), site logout URL, seed-data import, and GraphQL schema fetch + codegen. Trigger signals: *.network-meta.xml, org-setup.config.json (socialLogin/logoutUrl), data-plan.json, sfdx-project.json, or mentions of deploy, org setup, social login/SSO, or logout URL on an Experience site. DO NOT TRIGGER when: creating a new UI bundle project (use experience-ui-bundle-project-generate); styling pages without deploying (use experience-ui-bundle-frontend-generate); adding a feature such as auth, search, or file upload without deploying (use the matching experience-ui-bundle-*-generate skill); configuring MFA permission sets (use experience-ui-bundle-mfa-configure).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.4 KB |
| assets/Communities.settings-meta.xml | config | 1001 B |
| assets/data-delete.apex | other | 1.6 KB |
| assets/data-import.apex | other | 3.0 KB |
| assets/network-selfreg-xml-recipe.md | markdown | 3.5 KB |
| assets/network-selfreg.apex | other | 2.1 KB |
| assets/org-setup.config.template.json | config | 662 B |
| assets/prepare-import-unique-fields.js | script | 1.7 KB |
| assets/social-login-auth-providers.apex | other | 6.7 KB |
| references/config-scaffold.md | markdown | 5.6 KB |
| references/data-import.md | markdown | 5.1 KB |
| references/dev-preview.md | markdown | 3.2 KB |
| references/graphql.md | markdown | 1.1 KB |
| references/license-checks.md | markdown | 2.8 KB |
| references/logout-url.md | markdown | 4.8 KB |
| references/role-assignment.md | markdown | 1.4 KB |
| references/self-registration.md | markdown | 4.0 KB |
| references/social-login.md | markdown | 10.9 KB |
| scripts/derive-site-name.shexecutable | script | 1.3 KB |
| scripts/find-data-plan.shexecutable | script | 1.3 KB |
| scripts/find-prep-script.shexecutable | script | 1.1 KB |
| scripts/get-source-root.shexecutable | script | 989 B |
| scripts/set-logout-url.mjsexecutable | script | 10.8 KB |
references/license-checks.md
View on GitHub# License pre-checks
Two license gates guard steps that fail with cryptic errors when the org lacks
the right UserLicense. Both are derived from the **self-reg profile** — there is
no separate license config, so the requirement can't drift from the profile the
flow actually assigns. Both only apply **when self-registration is configured**.
Source of truth: reference `org-setup.mjs` `checkDeployLicense` (956-992),
`readProfileUserLicense` (938-944), `checkSelfRegLicense` (895-926), and
`evaluateLicenseRows` (`org-setup-utils.mjs` ~224+).
## Gate 1 — deploy license (pre-deploy, HARD block)
Runs **before** `sf project deploy start` (lines 1478-1483). The profile isn't in
the org yet pre-deploy, so querying `Profile` would only report "profile
missing" — instead, read the required license NAME straight from the local
profile source:
`<packageDir>/main/default/profiles/<selfRegProfile>.profile-meta.xml` →
`<userLicense>...</userLicense>`.
- If the profile file or `<userLicense>` element is absent → nothing to gate on;
let deploy proceed (line 960).
- Otherwise query the org:
```sql
SELECT LicenseDefinitionKey, Name, Status, TotalLicenses, UsedLicenses
FROM UserLicense WHERE Name = '<licenseName-escaped>'
```
- Zero rows → **block the deploy** with a message NAMING the missing license
(`required license "<name>" is not present in the org — add it before
deploying`). Query/parse failure → block. Otherwise run the seat/status check.
This is a hard block (a `StepError`) because deploying without the license fails
anyway, but with an unhelpful error.
## Gate 2 — self-reg license (pre-selfReg, SOFT skip)
Runs **before** the self-reg step (lines 1598-1601). Query the license via the
profile:
```sql
SELECT UserLicense.LicenseDefinitionKey, UserLicense.Name, UserLicense.Status,
UserLicense.TotalLicenses, UserLicense.UsedLicenses
FROM Profile WHERE Name = '<selfRegProfile>'
```
A query failure, zero rows, inactive license, or no free seats is a **soft skip**:
warn with the specific reason and record the step skipped. Self-registration
being unavailable is not a setup failure.
## Seat / status math (`evaluateLicenseRows`)
Done client-side because SOQL can't compare two fields. The license is
**satisfied** only when it is **Active** and either `UsedLicenses < TotalLicenses`
or `TotalLicenses === -1` (the documented "unlimited" sentinel — treat it as
always having free seats). Report the specific reason (missing / inactive / no
seats) so the user knows exactly what to fix.
## SOQL-safety of the profile name
- In Gate 2 the profile name is **validate-and-fail**: a `'`, `\`, or control
char throws a config error rather than being escaped (developer config, not
user input).
- In Gate 1 the license NAME read from the profile XML is **escaped** for the
SOQL literal (`escapeSoqlString`).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |