Individual skill
experience-ui-bundle-2gp-deploy
MUST activate when the user wants to package, distribute, or install/upgrade/uninstall/promote a UI Bundle as a Salesforce second-generation (2GP) package (project may contain uiBundles/ or sfdx-project.json for packaging tasks; install/upgrade tasks may lack local bundle files). Handles making a bundle packageable, choosing managed/unlocked flavor, creating package/version with sf package, installing/upgrading in another org, and debugging failures. TRIGGER on packaging, 2GP, managed package, unlocked package, AppExchange, package version, sf package, sf package install, sf package upgrade, install a package, upgrade a package, cross-org distribution. DO NOT TRIGGER for plain source deploy to one org (use experience-ui-bundle-deploy) or scaffolding a new bundle (use experience-ui-bundle-project-generate). Apply piecemeal — do ONLY the part asked.
plugins/builder/experience-react/skills/experience-ui-bundle-2gp-deploy/SKILL.md
Source commit a8a18ce1e4ba12e69b4073eab98ce31bfbd8271e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,151
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- design Derived category
- testing Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesSKILL.mdcore · 22,135 bytesassets/CustomApplication.app-meta.xmlasset · 425 bytesassets/PermissionSet.permissionset-meta.xmlasset · 353 bytesscripts/find-bundle-package-dir.shruns · 2,026 bytes
Read excerpt
# Package an existing UI Bundle (2GP)
How to take a **UI Bundle that already exists in the current project**
(under `<packageDir>/uiBundles/<name>/`, where `<packageDir>` is the package
directory from `sfdx-project.json` — commonly `force-app/main/default`) and ship
it as a **second-generation package** (2GP), then install / upgrade / uninstall
it in another org.
**This is reference knowledge, not a runbook to execute top-to-bottom.** The
user already has a project and a built (or buildable) bundle. Read their intent
and apply only the matching part:
**Answer only what was asked.** Give the commands for the one part the user
needs plus the org each targets and any genuine caveat — nothing else. Do **not**