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/role-assignment.md

View on GitHub
# Role assignment

Detail for the **role** step. Source of truth: reference `org-setup.mjs`
`assignRoleToCurrentUser` (743-822).

Run this step **only** when a role is configured
(`role: { assignee: "currentUser", roleName: "<UserRole name>" }` in
`org-setup.config.json`). If absent, no-op cleanly. `assignee` is always
`currentUser` — it is the only value the flow honors. Assigning a role to the
current user is what makes Experience Cloud self-registration work correctly, so
this step normally runs before/with self-reg.

Validate `roleName` against the SOQL-name whitelist before querying.

## Sequence

1. **Resolve the role Id**:
   ```sql
   SELECT Id FROM UserRole WHERE Name = '<roleName>'
   ```
   Zero rows → hard error (`role "<roleName>" not found in org`).

2. **Resolve the current user**: `sf org display --target-org <org> --json` →
   `result.username`. If absent → hard error.

3. **Idempotency check**:
   ```sql
   SELECT Id, UserRoleId FROM User WHERE Username = '<username>'
   ```
   If `UserRoleId` is already set, **skip** — do not override an existing role
   assignment (lines 796-805).

4. **Assign**:
   ```bash
   sf data update record --sobject User \
     --where "Username='<username>'" \
     --values "UserRoleId='<roleId>'" \
     --target-org <org> --json
   ```
   Non-zero exit → hard error (`failed to assign role "<roleName>" to
   <username>`).
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