Skip to content

forcedotcom/sf-skills / plugins/builder/experience-react/skills/experience-ui-bundle-deploy

experience-ui-bundle-deploy

Verified

MUST 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).

references/config-scaffold.md

View on GitHub
# org-setup.config.json — schema and scaffolding when it's missing

`org-setup.config.json` (at the project root) drives three steps: permission-set
assignment (step 4), role assignment (step 5), and self-registration (step 6).
Source of truth for the schema: reference `org-setup-config-schema.mjs`
(zod `.strict()` — unknown keys are rejected); consumption:
`loadPermsetConfig` / `resolveAssignment` (org-setup.mjs 464-478).

## Why a missing file is a trap for the permset step

When the file is absent, `loadPermsetConfig` returns
`{ defaultAssignee: 'skip', assignments: {} }` (org-setup.mjs 466), so **every**
permission set discovered under `permissionsets/` resolves to `skip` and is
silently not assigned. The deploy looks successful, but GraphQL introspection
(step 8) then returns an incomplete schema because the caller lacks FLS.

So: **permset folder present + config file absent = help the user create the
config (or gather equivalent inputs) rather than silently skipping.** Do not
fabricate assignments — confirm intent first (see below).

## Full schema

Every top-level key is optional; each object is strict (no extra keys).

```json
{
  "permsetAssignments": {
    "defaultAssignee": "currentUser | guestUser | skip",
    "assignments": {
      "<PermissionSetApiName>": { "assignee": "currentUser | guestUser | skip" }
    }
  },
  "role": { "assignee": "currentUser", "roleName": "<UserRole name>" },
  "selfRegistration": { "selfRegProfile": "<Profile API name>",
                        "accountName": "<display name>" },
  "socialLogin": { "communityMemberProfile": "<Profile name>",
                   "authProviderNames": ["<DeveloperName>", "..."],
                   "communityUserPermset": "<PermissionSet API name>" },
  "logoutUrl": "/<site-path>/ or https://<absolute-url>"
}
```

- **`assignee`** is a closed set: `currentUser`, `guestUser`, or `skip` — never a
  raw username. `defaultAssignee` applies to any discovered permset not named in
  `assignments`; it defaults to `skip` when the `permsetAssignments` block is
  present but omits it.
- **No `siteName` anywhere** — for `guestUser` the site is derived from the single
  `networks/<siteName>.network-meta.xml` the app ships. If the assignee is
  `guestUser` and the site can't be derived or the guest user can't be resolved,
  that permset is skipped and recorded, not fatal (see step 4).
- **`role.assignee`** must be `currentUser` (the only value the flow honors);
  `roleName` is a non-empty `UserRole` name.
- **`selfRegistration`** has no license field — the required license is derived
  from `selfRegProfile` (see `references/license-checks.md`).
- **`socialLogin`** drives step 6b. `communityMemberProfile` (required) is the
  profile added to `NetworkMemberGroup` so SSO-registered users can access the
  site. `authProviderNames` (required, non-empty) are the **DeveloperNames** of
  `AuthProvider` (OAuth) or `SamlSsoConfig` (SAML) records to link to the site's
  `AuthConfig`. `communityUserPermset` (optional) is assigned to SSO-created
  community users so `getCurrentUser()` works (needs `ApiEnabled`). Like
  `selfRegistration`, there is **no `siteName`** — the site is derived from the
  single `networks/<siteName>.network-meta.xml`. Full step detail:
  `references/social-login.md`.
- **`logoutUrl`** (optional) drives step 3b. A **site-relative path** (e.g.
  `/propertyrentalapp/`, recommended — domain-independent) or an absolute
  `http(s)` URL. Setup resolves a relative value to the absolute URL the platform
  requires (against the site's Experience Cloud origin) and writes it to the
  site's `<logoutUrl>` Network metadata after deploy, so Sign Out returns members
  to *this* site instead of the org default site. No `siteName` — the site is
  derived from the single `networks/<siteName>.network-meta.xml`. Full step
  detail: `references/logout-url.md`.

## Scaffolding flow (permset folder present, config missing)

1. **List the permission sets** under `<packageDir>/main/default/permissionsets/`
   (their file base names are the API names) so the choice is concrete.
2. **Ask the user, per permset, who to assign it to** — `currentUser`,
   `guestUser`, or `skip`. Default a whole-set answer to `currentUser` (not
   `skip`) since the folder exists on purpose; only use `guestUser` for permsets
   meant for the site's guest user. Also ask whether they want a `role`,
   `selfRegistration`, and/or `logoutUrl` block while you're writing the file (all
   optional). For `logoutUrl`, phrase it as "point Sign Out back to this site?" —
   if yes, default the value to the site-relative path `/<site-path>/` (step 3b
   resolves it to absolute post-deploy). Skipping it leaves logout on the org
   default site (see the `logoutUrl` note above).
3. **Offer two equivalent paths** — let the user pick:
   - **Write the file**: copy `assets/org-setup.config.template.json` to
     `org-setup.config.json` at the project root and fill in the answers. This is
     durable — re-runs and the reference `npm run setup` both read it.
   - **One-off inputs**: if they don't want a file, treat their answers as the
     config for this run only (assign each permset per the stated assignee via
     step 4's `sf org assign permset` command). Nothing persists.
4. **Validate before relying on it**: keys must match the strict schema exactly
   (e.g. it's `permsetAssignments`, not the singular `permsetAssignment`), and
   `assignee` values must be one of the three literals. Reject anything else and
   re-ask rather than writing an invalid file.

Prefer writing the file when the user is unsure — it makes the behavior
reproducible and matches what the reference tooling expects.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall