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 |
assets/network-selfreg-xml-recipe.md
View on GitHub# Network metadata edit recipe (two-phase)
Ported from reference `org-setup-xml.mjs` (`addProfileToMemberGroups` lines 125-147,
`enableSelfRegInXml` lines 158-182) and `org-setup.mjs`
(`ensureNetworkMemberProfile` 524-566, `enableSelfRegistration` 580-617).
**These two edits are NOT applied together.** The reference splits them across the
deploy so the profile is a recognised site member before self-registration is
switched on:
- **Edit A** runs in **Step 3, before the main `sf project deploy start`** — it
adds the profile to `networkMemberGroups` on the local source, so the profile
deploys as a site member alongside everything else. (org-setup.mjs 1434-1445:
"This must happen BEFORE the initial deploy so that the profile is a recognised
site member when subsequent steps … are deployed.")
- **Edit B** runs in **Step 6 (the self-reg step)** — it flips
`selfRegistration` to `true`, injects `<selfRegProfile>`, and is followed by a
**network-only redeploy** of just that one file.
## File to edit
`<packageDir>/main/default/networks/<siteName>.network-meta.xml`
`<siteName>` is the base name of the **single** `*.network-meta.xml` file under
`networks/`. If there is more than one such file, STOP — the site is ambiguous
and the reference implementation refuses to guess (see `deriveSiteName`,
`references/self-registration.md`).
`<selfRegProfile>` must contain no XML-special characters. Reject a name with
`< > & " '` as a config error rather than escaping it — profile names are
developer-authored config, not user input.
## Edit A — add the profile to member groups (Step 3, pre-main-deploy, idempotent)
Apply this to the local source **before** the Step 3 main deploy. Do NOT deploy
the file on its own — the main deploy ships it. Best-effort: if the
`<networkMemberGroups>` node is missing, surface a loud error but continue to
deploy (the self-reg step records the authoritative failure — org-setup.mjs
540-558).
Under the existing `<networkMemberGroups>` element, ensure the self-reg profile
is listed. **Skip this edit** if `<profile><selfRegProfile></profile>` is already
present (changed: false). Otherwise insert it immediately after the opening tag,
matching the file's existing member indentation:
```xml
<networkMemberGroups>
<profile><selfRegProfile></profile>
<!-- ...existing members unchanged... -->
</networkMemberGroups>
```
## Edit B — enable self-registration + set the profile (Step 6, idempotent)
Apply this during the self-reg step, then redeploy only this file (below).
**Skip this edit** if `<selfRegistration>` is already `true` OR a
`<selfRegProfile>` element already exists (changed: false — same skip semantics
as the reference). Otherwise apply BOTH targeted edits:
1. Flip the flag:
```xml
<selfRegistration>false</selfRegistration> <!-- becomes -->
<selfRegistration>true</selfRegistration>
```
2. Insert `<selfRegProfile>` immediately before `<selfRegistration>`, preserving
the leading whitespace/indent of that line:
```xml
<selfRegProfile><selfRegProfile></selfRegProfile>
<selfRegistration>true</selfRegistration>
```
A missing `<selfRegistration>` node is an error to surface, not to silently
no-op.
## Redeploy the edited file (Edit B only)
After Edit B, deploy only the one network file (not the whole project):
```bash
sf project deploy start --target-org <org> --source-dir <path-to>/<siteName>.network-meta.xml
```
Timeout 120s. If nothing changed (Edit B was skipped), no redeploy is needed.
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 |